Guardsquare

20/10/2026

The EU’s Cyber Resilience Act (CRA) is fundamentally changing how mobile apps are secured, shifting the liability of cybersecurity directly to developers and app publishers.
And while reporting obligations have already come into effect, organizations still have until 11 December 2027 to fully comply with all the CRA’s requirements.

So what are those requirements? And what steps should you start putting into place today to ensure compliance?

Read the full breakdown and ensure your mobile app is ready:

How can mobile application developers comply with the Cyber Resilience Act, which comes into effect on 11 December 2027? Explore scope, deadlines, and more

14/10/2026

Next for : runtime attacks.

One example of a runtime attack is Near Field Communication (NFC) signal relay fraud. NFC is often used by contactless payment and mobile identity apps as a form of additional verification.

These require users to physically tap their credit card against their phone’s NFC chip to authenticate it. Typically, an overlay screen tricks a user into thinking they’ve been logged out and need to re-verify their identity. When the user taps their card, a background app captures the NFC signals and sends them to an attacker’s device.

This blog dives into NFC relay attacks and several other real-world examples of mobile app attacks, and how strong mobile app security can mitigate the impact of these attacks.

Read more here: https://hubs.la/Q04B2Rzz0

13/10/2026

A widening outbreak of data leaks in Japan have already exposed millions of customer and employee records. The source of these incidents all trace back to API attacks using stolen mobile application credentials.

While the speed, scope, and scalability of these incidents are quite notable, the actual attack methodologies are nothing new. Existing mobile application defenses (when applied correctly) can address each point of opportunity in the attack cycle.

This includes:
- Continuous testing throughout the development process to help developers identify and fix potential security issues (like hardcoded secrets) as they build the application.
- Polymorphic protections that combine sophisticated code hardening (layers of obfuscation and encryption techniques to defend against static analysis) with runtime checks (to prevent dynamic analysis and tampering when the app is running).
- Mobile API security in the form of dedicated app attestation capabilities, to ensure that only a legitimate app on a trusted device can access backend services (while blocking malicious clones, bots, scripts, and agents).

Read our latest blog to learn how accelerated mobile API attacks (and others like them) can be prevented with a modern, defense-in-depth approach to mobile application security:

Mobile API attacks lead to widespread data leaks across Japan, highlighting the need for comprehensive mobile app security. Learn how they started.

07/10/2026

The next attack we’re featuring for : Malware.

Commonly distributed via phishing campaigns, malware has long been a problem for mobile application developers. By taking advantage of certain OS features like accessibility services, malware allows threat actors to gain control of a user device and collect their data.

Combatting malware requires a complete mobile app security strategy.

Read more about how real-time threat monitoring can help teams understand a malware attack and how multi-layered protections mitigate the risks of malware here: https://hubs.la/Q04zjpb60

06/10/2026

Did you know more than 33% of scanned mobile app builds have certificate verification issues? Or that lingering debug flags are frequently left in production builds?

Code reviewers aren't to blame. Many concerning mobile app security risks pass code review because they don't look dangerous in context.

Check out our latest blog to learn the real threat to mobile security and how automated security testing addresses the blind spots.

Read more:

Learn how mobile application security testing (MAST) catches vulnerabilities that code review can miss, from hardcoded secrets to debug flags.

05/10/2026

Welcome to the mobile-first fraud era. New research shows that 90% of all scams take place via a mobile phone, with investment scams the most costly (an average case value of $6,600). Banking fraud via mobile in particular has seen a 35% increase over the last 12 months.

AI and LLMs have made social engineering attacks (like mobile phishing) easier and more effective. When combined with a mobile malware payload, a single errant click can trigger a chain reaction that leads to lost credentials, account takeovers, and many assorted flavors of financial fraud.

Mobile banking and FinTech apps need best-of-breed protections against the latest AI-accelerated fraud campaigns. This means polymorphic code hardening and runtime checks that uniquely change shape with each app build to reset the clock on persistent attacks.

There’s a scammer in your pocket

02/10/2026

AI helped drive a 300% increase in bot traffic last year. But that surge is symptomatic of a more prescient security trend.

Akamai’s latest State of the Internet report finds that AI is also responsible for elevating APIs as the dominant attack surface for modern enterprises. Threat researchers recorded a 113% increase in daily API attacks while some 87% of surveyed organizations experienced an API-related security incident in 2025 (up from 76% in 2022).

Mobile APIs can be directly attacked by bots, emulators, agents, or modified apps. This common gap in mobile app security allows backend systems to receive malicious requests that mimic legitimate traffic. Closing this gap requires verification at the API boundary to confirm that all API calls come from legitimate mobile apps running in trusted environments.

Akamai report warns of increase in bot traffic, API threats, chatbot leaks and other AI-related threats

01/10/2026

🚨It’s Cybersecurity Awareness Month!🚨

This month, we’re highlighting real world mobile app attacks and the defenses you can implement against them.

The first attack we’re discussing is fitting for the month of October: mobile synthetic identity fraud aka “Frankenstein" fraud.

Attackers collect real personal information like social security numbers, bank account information, and credit score profiles to attempt to bypass verification checks and execute an authentic financial transaction.

For financial organizations, mitigating “Frankenstein fraud" begins with a strong, multi-layered mobile application security strategy. A combination of real-time threat monitoring, runtime checks, and app attestation can help you identify these synthetic identities before they cause damage.

Read more about how these attacks are executed and the strategies you can employ against them here: https://hubs.la/Q04yKGnN0

29/09/2026

A friend's relative took a call from his "bank." He walked through a basic "security check," installed what he thought was an app update, and hung up.

Twenty minutes later, his account was completely drained.

No phishing link. No stolen card. His bank's fraud engine never saw any of it, because the fraud never left his phone.

This is the part of the fraud landscape most detection stacks still aren't built for. Malware families like TsarBot, CopyBara, and Hook don't steal a password and log in from somewhere else anymore. They take over the device itself: fake lock screens, screen recording, accessibility abuse, and in some cases, transactions executed directly from the victim's real session.

Fraud didn't get smarter. It got closer.

We broke down how these three malware families operate and what it actually takes to defend against them:

Learn how on-device fraud and mobile malware bypass traditional fraud detection and how financial apps can protect users from device-based attacks.

25/09/2026

You may have forgotten about the “smart toaster” app you downloaded six years ago, but attackers haven’t. As the Internet of Things (IoT) market continues to expand and companion apps proliferate in app stores, a new study from researchers at UMass Amherst raises security concerns about abandoned IoT apps.

Analysis of more than 60,000 Android apps found security risks in over 70% of the dataset, with 30 of the top 1,000 most-installed apps sending data to broken external endpoints. Even after vendors discontinue support, apps frequently remain operational on users’ mobile devices, interfacing with devices and collecting user data without receiving security updates. This leaves known and newly discovered vulnerabilities unmitigated and increases the risks of remote exploitation, unauthorized device access, and prolonged data misuse.

The growing "IoT abandonware" problem isn’t just a risk for users and smart device manufacturers. It also introduces a threat vector for mobile apps installed on user devices.