#Approov

Approov Mobile Security

@approov.bsky.social

3 days ago

Epic Victory: Google Play's Walled Garden Opens Up & What It Means for Developers Epic Victory: Google Play's Walled Garden Opens Up & What It Means for Developers Episode Summary: In this episode of Upwardly Mobile, we dive deep into the landmark antitrust settlement between Epic Games and Google that is set to fundamentally reshape the Android app ecosystem globally. After years of legal battles sparked by Epic's "Project Liberty" and the removal of Fortnite from the Play Store, a jury found Google guilty of maintaining an illegal monopoly. We break down the newly announced March 2026 settlement, which significantly drops Play Store commission fees and introduces a game-changing "Registered App Stores" program. What does this mean for mobile developers, app revenue, and Android security? Tune in to find out! Brought to you by Approov: As Android opens its doors to third-party "Registered App Stores" and frictionless sideloading, ensuring your mobile app and APIs are protected from malicious clones and tampering is more critical than ever. Secure your mobile business and authenticate your apps natively with https://approov.com/. Key Topics Discussed: - The Origins of the Lawsuit: How Epic Games' Tim Sweeney bypassed Google's standard 30% fee by allowing direct purchases in Fortnite, leading to the game's removal and a massive antitrust lawsuit. - The Courtroom Battle: The revealing internal practices uncovered during the trial, including Google's "Project Hug" and millions of dollars spent to prevent developers from abandoning the Play Store. - The 2026 Settlement Details: How Google is dropping its standard Play Store commission to 20% for in-app purchases and 10% for recurring subscriptions. - Registered App Stores Program: A deep dive into Google's new framework that allows alternative Android app stores (like the Epic Games Store) to become "first-class citizens" on Android devices, removing the scary, "doom-laden" security pop-ups previously associated with sideloading. - Global Rollout Timeline: When these major fee changes and developer programs will go live, starting in the US, UK, and European Economic Area in June 2026, and expanding globally by September 2027. Source Materials & Further Reading: - TechCrunch: https://techcrunch.com/ - Wikipedia: https://en.wikipedia.org/w/index.php?title=Epic_Games_v._Google&oldid=1338953412 Targeted SEO Keywords: Epic Games vs Google, Google Play Store settlement, Android app ecosystem, Registered App Stores program, mobile app development, third-party app stores, sideloading Android apps, app store commission fees, Tim Sweeney, Fortnite Android return, mobile app security, API protection. 

📣 New Podcast! "Epic Victory: Google Play's Walled Garden Opens Up & What It Means for Developers" on @Spreaker #androiddev #approov #appstore #epicgames #fortnite #googleplay #mobilesecurity #sideloading #upwardlymobile

Approov Mobile Security

@approov.bsky.social

1 week ago

Unpacking the Spotify Exploits: Credential Stuffing, Fake Streams, and Mobile App Security Unpacking the Spotify Exploits: Credential Stuffing, Fake Streams, and Mobile App Security Episode Summary: In this episode of Upwardly Mobile, we dive deep into the digital exploitation landscape of one of the world's largest audio streaming platforms. We break down the massive credential stuffing attack that compromised 350,000 Spotify users, exposing the dangers of poor password hygiene and unsecured databases. We also explore the ongoing controversies surrounding Spotify, including lawsuits over artificial streaming, bot farms, and the platform's "Discovery Mode". Additionally, we highlight a growing trend where malicious actors are weaponizing Spotify's search features to promote pirated software, phishing schemes, and malware. Finally, we pivot to actionable solutions for developers, exploring how Zero Trust Runtime Protection and App Attestation can prevent automated mobile attacks. Brought to you by Approov: Don't let bots, scripts, or fake apps compromise your platform. Learn how to stop credential stuffing and secure your APIs at https://approov.com/. Sponsor Spotlight: Approov Mobile Security Are your mobile apps and APIs safe from automated credential stuffing, emulators, and Man-in-the-Middle (MitM) attacks? Approov ensures that only genuine mobile app instances running in safe environments can access your APIs, blocking scripts, modified apps, and bots in real-time. 👉 Secure your mobile platforms today at https://approov.com/. Source Materials & Further Reading: - https://www.itpro.com/ - https://www.noise11.com/ - https://dig.watch/ - https://approov.com/ Keywords: Credential stuffing, mobile app security, Spotify hack, artificial streaming, bot farms, zero trust runtime protection, API security, mobile malware, phishing schemes, app attestation, Approov. 

📣 New Podcast! "Unpacking the Spotify Exploits: Credential Stuffing, Fake Streams, and Mobile App Security" on @Spreaker #apisecurity #approov #appsec #credentialstuffing #cybersecurity #mobilesecurity #spotify #spotifyhack #upwardlymobile #zerotrust

Approov Mobile Security

@approov.bsky.social

2 weeks ago

Securing Mobile Healthcare | The Hidden Dangers in Mental Health Apps Episode Summary: In this episode of Upwardly Mobile, we dive deep into a shocking new cybersecurity report revealing that millions of users' highly sensitive medical data may be at risk. We discuss the recent discovery of 1,500 vulnerabilities across 10 incredibly popular mental health apps—which have been downloaded over 14 million times. From leaked therapy transcripts and mood logs to the high black-market value of these stolen health records, we unpack the unique risks threatening the digital healthcare space today. Finally, we explore actionable solutions for healthcare providers and developers to lock down their platforms, featuring insights on Runtime Application Self-Protection (RASP), dynamic certificate pinning, and end-to-end API security. Key Topics Discussed in This Episode: - The Mental Health App Crisis: How researchers at Oversecured uncovered 54 high-severity flaws in leading mental health applications, leaving sensitive data like Cognitive Behavioral Therapy (CBT) session notes and medication schedules exposed. - The Black Market for Health Data: Why cybercriminals are targeting therapy records, which can sell for upwards of $1,000 each—far more than stolen credit card numbers. - Common Developer Pitfalls: The dangers of outdated apps, plaintext configuration data, hardcoded Firebase URLs, and insecure encryption keys. - Securing Mobile Health: How technologies like Runtime Application Self-Protection (RASP) and dynamic certificate pinning can prevent Man-in-the-Middle (MitM) attacks, block bots, and ensure HIPAA and GDPR compliance. Sponsor: This episode is brought to you by https://www.google.com/url?sa=E&q=https%3A%2F%2Fapproov.com. Approov provides complete, end-to-end protection for mobile health apps and APIs. Their lightweight SDK and RASP technology can be deployed in just a single sprint to block bot attacks, prevent credential stuffing, and stop API abuse. Ensure your patients' health data is safe, even on jailbroken devices or insecure Wi-Fi networks. Learn how to protect your revenue and patient trust at https://www.google.com/url?sa=E&q=https%3A%2F%2Fapproov.com. Resources & Source Materials: - TechRadar Report: https://www.google.com/url?sa=E&q=https%3A%2F%2Fwww.techradar.com - Approov Mobile Health Security: https://www.google.com/url?sa=E&q=https%3A%2F%2Fapproov.com SEO Keywords: Mobile app security, mental health apps, healthcare data breach, API security, mobile health compliance, HIPAA compliance mobile apps, RASP technology, cybersecurity podcast, Oversecured vulnerabilities, patient data protection, Approov mobile security.       

📣 New Podcast! "Securing Mobile Healthcare | The Hidden Dangers in Mental Health Apps" on @Spreaker #apisecurity #appdevelopment #approov #cybersecurity #databreach #healthtech #hipaa #infosec #mentalhealthapps #mobilesecurity #upwardlymobile

Approov Mobile Security

@approov.bsky.social

2 weeks ago

The Triangle of Trust: Mastering Mobile App Attestation & Zero Trust API Security Welcome to another episode of Upwardly Mobile! In this episode, we take a deep dive into the evolution of runtime security for mobile API access. Traditional methods like API keys are easily stolen because they are static and stored directly inside the user's app. To combat this vulnerability, we explore the groundbreaking "Triangle of Trust" architecture developed by CriticalBlue, the company behind the Approov mobile security service. We unpack the technical details of US Patent 11,163,858 B2, titled "Client Software Attestation," which establishes a Zero Trust proof of software integrity for apps operating on the public internet. This episode breaks down how the patented system calculates a cryptographic hash fingerprint of an executing code image to detect tampering in real-time, ensuring that malicious actors cannot spoof access. We also discuss how Approov's platform-agnostic approach provides a significant competitive advantage over OS-native solutions like Google Play Integrity and Apple App Attest, especially in global markets featuring Huawei's HarmonyOS NEXT and non-GMS Android devices. Key Takeaways from this Episode: - The Triangle of Trust: A tripartite architecture separating the security check from the access itself, involving an Issuer (Approov Cloud Attestation Server), a Holder (the Mobile Client Device), and a Verifier (the Backend Server Device). - Dynamic Code Fingerprinting: How client applications calculate a cryptographic hash of their own executing code image to prove integrity, ensuring no sensitive "master keys" are ever stored on the device where they could be extracted. - Protection Against Advanced Threats: The system's ability to thwart "living-off-the-land" attacks (like memory hooking with Frida) and Man-in-the-Middle (MITM) attacks by verifying code dynamically in memory, rather than just checking the static OS state. - Superiority Over OS-Native Tools: Why a unified, cross-platform attestation approach is critical for the global market, bypassing the latency, platform restrictions, and hardware dependencies of Google Play Integrity and Apple App Attest. - A Defensible Security Moat: An analysis of why CriticalBlue's patent is highly defensible and has been cited over 60 times as prior art, acting as a major technical blocker for competitors in the cybersecurity industry. Sponsor: This episode is brought to you by Approov. Stop relying on static API keys and secure your mobile business with deterministic, zero-trust software integrity. With global reach across iOS, GMS Android, non-GMS Android, and HarmonyOS, Approov ensures your backend APIs are shielded from malicious bots and tampered apps. Visit https://approov.com/ to learn more and secure your mobile ecosystem today. Source Materials & Relevant Links: - US Patent 11,163,858 B2: Client Software Attestation by Richard Michael Taylor / Critical Blue Ltd. (Filed 2015, Granted Nov 2, 2021). - Whitepaper Excerpt: Attestation: The Triangle of Trust. - Approov Official Website: https://approov.com/ SEO Keywords: Mobile API security, Zero Trust architecture, App attestation, Approov, CriticalBlue, Cryptographic hash fingerprint, Google Play Integrity alternative, Apple App Attest alternative, Man-in-the-Middle protection, US Patent 11163858, Mobile app tampering, Cybersecurity podcast. 

📣 New Podcast! "The Triangle of Trust: Mastering Mobile App Attestation & Zero Trust API Security" on @Spreaker #apiprotection #appattestation #approov #criticalblue #cybersecurity #devsecops #mobilesecurity #upwardlymobilepodcast #zerotrust

Approov Mobile Security

@approov.bsky.social

1 month ago

The "Rootless" Revolution: Inside the Dopamine Jailbreak & The EBT Security Crisis The "Rootless" Revolution: Inside the Dopamine Jailbreak & The EBT Security Crisis 🎧 Episode Summary In this episode of Upwardly Mobile, we dive into two critical stories reshaping the mobile security landscape. First, we unpack the architecture of Dopamine, the modern "rootless" jailbreak that has cracked iOS 15 and iOS 16 without touching the system partition. We explore how it bypasses Apple’s Signed System Volume (SSV) and what this means for app developers trying to detect compromised devices. Then, we shift gears to a systemic failure in government fintech: why the "Lock Card" feature in EBT mobile apps is failing to stop fraud. We break down how attackers are bypassing mobile controls using legacy magstripe rails and bot attacks. 🚀 Key Topics Discussed - The Dopamine Architecture: Understanding the shift from "rootful" to "rootless" jailbreaking. - How it Works: The exploit chain, including PAC and PPL bypasses, and the creation of the fake root environment in /var/jb. - Detection Challenges: Why traditional jailbreak detection methods struggle against rootless environments and the reliance on finding tweak injection libraries like ElleKit. - The EBT Mobile Failure: Why locking your EBT card in the mobile app doesn't actually stop thieves at the register. - API Abuse: How botnets are hammering IVR and app APIs to time their theft perfectly. 🔗 Resources & Links Dopamine Jailbreak: - Official Project: https://github.com/opa334/Dopamine - Installation Guide: https://ios.cfw.guide/installing-dopamine/ - Technical Insight: https://ellekit.space/dopamine/ EBT & Mobile Fraud Analysis: - The Mechanics of Theft: https://www.propel.app/ebt-theft/how-are-ebt-benefits-being-stolen/ - Systemic Vulnerabilities: https://www.pa.gov/agencies/osig/what-we-do/bureau-of-fraud-prevention-and-prosecution/snap-skimming 🛡️ Sponsor This episode is brought to you by Approov. Is your mobile app running on a jailbroken device? Are bots scraping your API endpoints? Approov provides a comprehensive mobile security solution that ensures only genuine mobile app instances, running on safe mobile environments, can access your backend APIs. 👉 Learn more at: https://approov.com/ 🔍 SEO Keywords Dopamine Jailbreak, Rootless Jailbreak, iOS 15 Jailbreak, iOS 16 Security, Mobile App Security, EBT Fraud, Skimming, API Security, Sideloading, TrollStore, Magstripe Vulnerabilities, App Attestation.

📣 New Podcast! "The "Rootless" Revolution: Inside the Dopamine Jailbreak & The EBT Security Crisis" on @Spreaker #approov #appsec #cybersecurity #dopamine #fintechsecurity #infosec #jailbreak #mobilesecurity #upwardlymobile

Approov Mobile Security

@approov.bsky.social

1 month ago

Beyond the Hardware: Why Key Attestation Is Just a Receipt, Not a Security Strategy Beyond the Hardware: Why Key Attestation Is Just a Receipt, Not a Security Strategy In this episode of Upwardly Mobile, we dive deep into the often-misunderstood world of mobile app security to debunk the myth that hardware-backed key attestation is a "silver bullet." Drawing from expert analysis by Approov, Oasis, and community discussions, we explore why relying solely on Apple’s App Attest or Google’s Play Integrity can leave your APIs vulnerable to sophisticated attacks like device farming and runtime instrumentation. We explain why attestation is merely a "snapshot" in time and how to implement a true defense-in-depth strategy. Key Takeaways: - The Hardware Myth: Companies like Google and Apple promote hardware-backed key attestation (using TEEs or Secure Elements) as a primary security measure, but this approach has critical limitations when used in isolation. While it proves a cryptographic key is stored in secure hardware, it does not guarantee the integrity of the app calling that key or the user operating it. - The "Receipt" Analogy: Remote attestation is effectively just a receipt proving that a specific binary ran on specific hardware at a specific moment. It fails to prove that the state hasn't been rolled back, that the operator isn't malicious, or that the inputs haven't been manipulated since that snapshot was taken. - The Threat of Device Farms: Attackers can physically amass legitimate iPhones in "Device Farms" to generate valid App Attest tokens. These tokens are then sold via APIs to bots, allowing scripts to impersonate genuine devices and bypass standard hardware checks. - Runtime Manipulation: Tools like Frida and Magisk allow hackers to hook into API calls and forge attestation results or manipulate the application's behavior after the boot process. Without Runtime Application Self Protection (RASP), a validly attested device can still run a compromised app. - The Solution is Multi-Layered: Effective security requires moving verification off the device to the cloud and implementing dynamic checks. A robust strategy includes RASP, dynamic certificate pinning, and cloud-based mobile attestation that verifies the app's integrity continuously, not just at boot. Featured Resources & Source Material: - Article: https://approov.io/blog/limitations-of-hardware-backed-key-attestation-in-mobile-security – An analysis of why verification must always occur off-device. - Article: https://approov.io/blog/how-to-defeat-apple-devicecheck-and-appattest – A technical look at how hackers bypass iOS security using instrumentation and device farms. - Community Insight: https://dev.to/adityasingh_32/tee-attestation-isnt-trust-its-just-a-receipt-2m3k – A breakdown of why attestation does not equal trust. - Deep Dive: https://oasis.net/blog/tee-attestation-is-not-enough – Exploring the nuances of remote attestation within trust systems. - Definition: https://en.wikipedia.org/wiki/Trusted_execution_environment – Understanding the history and hardware behind TEEs. Sponsored By: This episode is brought to you by Approov. Approov Mobile Security provides a comprehensive solution that goes beyond simple attestation. By combining RASP, dynamic certificate pinning, and cloud-based verification, Approov ensures that only genuine, untampered instances of your app can access your APIs. - Website: https://approov.io/ - Talk to an Expert: https://approov.io/product/demo - Check Your Security: https://approov.io/product/assessment Keywords: Mobile Security, API Security, App Attestation, RASP, Device Farms, Man-in-the-Middle Attacks, Jailbreak Detection, Apple App Attest, Google Play Integrity, Approov, Cybersecurity, Trusted Execution Environment (TEE). 

📣 New Podcast! "Beyond the Hardware: Why Key Attestation Is Just a Receipt, Not a Security Strategy" on @Spreaker #androiddev #apisecurity #approov #appsec #iosdevelopment #mobilesecurity

Approov Mobile Security

@approov.bsky.social

1 month ago

SNAP | Why Mobile Apps Are Failing to Stop Food Stamp Fraud? Episode Summary In this episode of Upwardly Mobile, we investigate a growing financial crisis affecting the nation’s most vulnerable families. The USDA now estimates that up to $12 billion is stolen annually from the Supplemental Nutrition Assistance Program (SNAP). We explore how transnational criminal rings are using sophisticated technology—from physical skimmers to brute-force cyberattacks—to drain EBT cards in seconds. We also break down why the government’s latest solution—mobile apps that allow users to "lock" their cards—is failing to stop the theft. We analyze the technical vulnerabilities of the legacy magstripe system and explain why app-based controls are often bypassed by backend fraud and race conditions. This episode is sponsored by https://www.google.com/url?sa=E&q=https%3A%2F%2Fapproov.io%2F. Mobile apps are now the front door to critical services, but as we discuss in this episode, they are only as strong as the security frameworks behind them. Approov provides comprehensive mobile app protection, ensuring that the requests hitting your API are from genuine apps running on untampered devices. Key Topics & Takeaways: • The Scale of the Problem: Federal investigators estimate that SNAP fraud has hit all-time highs, potentially reaching $12 billion annually. Georgia alone reported nearly $23 million stolen in just the first quarter of 2025. • How the Fraud Works: Criminals are utilizing advanced skimming technology and "brute force" software that can guess a four-digit PIN in less than a second. The Secret Service notes that these are often transnational organized crime groups capable of working easily across borders. • The "Lock" Feature Failure: Many states, including Georgia, encouraged users to download apps like ConnectEBT to "lock" their cards. However, users like Sheria Robertson report having funds stolen mere minutes after unlocking the app to make a purchase. • The Technical Vulnerability: The core issue is that EBT cards still rely on legacy magnetic stripe technology rather than secure chips (EMV). Because the backend system relies on static track data and a PIN, the mobile app’s "lock" feature is often bypassed by race conditions or bot attacks on IVR systems. • Bot Attacks: Cybercriminals are using bots to hammer IVR systems to check balances and time their withdrawals the moment funds are deposited. Featured Stories & Data: • Victim Spotlight: Sheria Robertson, a single mother who lost her Thanksgiving food budget to thieves in Brooklyn, NY, despite being in Georgia and using the app's security features. • Investigator Insight: Mark Haskins from the USDA Food and Nutrition Service explains that criminals are "taking it to the next level" with cyber and brute force attacks. • State Data: Top states for reported fraud include Georgia, New York, and California. Relevant Links & Resources: • USDA SNAP Replacement of Stolen Benefits Dashboard • Report Fraud: USDA Office of Inspector General Hotline [(800) 424-9121] • Technical Deep Dive: https://www.google.com/url?sa=E&q=https%3A%2F%2Fbreached.company%2Febt-cyberattacks-multi-state-crisis-threatens-food-security-for-millions%2F • News Coverage: https://www.google.com/url?sa=E&q=https%3A%2F%2Fwww.wsbtv.com%2Fnews%2Flocal%2Fatlanta%2Fgeorgia-officials-say-state-snap-system-subject-cyberattack%2FCRX6VB4INZH2VJNVJ3DPWY3DBQ%2F • Propel App Resource: https://www.google.com/url?sa=E&q=https%3A%2F%2Fwww.propel.app%2Febt-theft%2Fhow-are-ebt-benefits-being-stolen%2F Keywords: SNAP fraud, EBT skimming, food stamp theft, mobile app security, Approov, ConnectEBT, cybercrime, magnetic stripe vulnerability, USDA, social safety net, financial fraud, IVR bot attacks.

📣 New Podcast! "SNAP | Why Mobile Apps Are Failing to Stop Food Stamp Fraud?" on @Spreaker #approov #cybersecurity #ebt #fintech #infosec #mobilesecurity #snapfraud #upwardlymobile

Approov Mobile Security

@approov.bsky.social

2 months ago

The Punkt MC03: Can You De-Google Without the Headache? In this episode, we explore the landscape of "privacy-first" smartphones, focusing on the newly unveiled Punkt MC03. We break down whether this Swiss-designed, German-made device can finally offer a viable alternative to the data-harvesting giants of the mobile world. We discuss the trade-offs of leaving the Google ecosystem, the unique "subscription-based" operating system model, and whether the return of the removable battery signals a shift in hardware trends. Key Topics & Timestamps: - The "De-Googled" Promise: The Punkt MC03 runs AphyOS, a custom version of Android that strips out Google Mobile Services to minimize background tracking and profiling. - AphyOS & The Subscription Model: Unlike standard Android phones, the MC03 relies on a subscription model (approx. $10/month after the first year) to fund security updates and infrastructure rather than selling user data to ad networks. - Security Architecture: The device splits the user experience into a secure "Vault" for vetted apps (like Proton and Signal) and a "Wild Web" environment for general Android apps, allowing users to isolate risky applications. - Hardware Highlights: The phone features a 6.67" OLED screen, IP68 rating, and a 5,200 mAh removable battery—a design choice driven by upcoming EU regulations regarding repairability. - Overcoming Past Failures: We discuss how the MC03 improves upon the "difficult-to-recommend" MC02 with a smoother onboarding process, an improved 64MP camera, and the option to install the Play Store for users who can't go fully cold-turkey. - The Competition: How the MC03 stacks up against other privacy-focused devices like the Murena Fairphone and other non-GMS ROMs like GrapheneOS. Sponsor: This episode is brought to you by Approov. Protect your mobile APIs from scripts, bots, and modified apps. Ensure that the requests you receive are from the genuine mobile app you released. - Visit https://approov.com/ to learn more about comprehensive mobile app security. Relevant Links & Source Materials: - ZDNET Review: https://www.zdnet.com/article/punkt-mc03-phone-ces-2026/ – Coverage of the US launch, pricing, and removable battery features. - Android Police Coverage: https://www.androidauthority.com/punkt-mc03-hands-on-ces-2026-3630101/ – An in-depth look at the onboarding improvements and specs. - Punkt Official Site: https://www.punkt.ch/products/mc03-premium-secure-smartphone – Direct specs and philosophy from the manufacturer. - Murena / /e/OS: https://thisgetthoughts.bearblog.dev/fairphone-5-murena-eos-review-part-2-the-os/ – Context on the competitor mentioned in the episode. Keywords: Punkt MC03, AphyOS, Non-GMS, De-Google, Mobile Privacy, Data Sovereignty, Removable Battery, Android Security, Fairphone, Murena, Apostrophy OS, Mobile Security.  Disclaimer: Information regarding pricing ($699 device / $10 monthly sub) and release dates (Spring 2026 for US) is based on reports from ZDNET and Android Police coverage of CES 2026.

📣 New Podcast! "The Punkt MC03: Can You De-Google Without the Headache?" on @Spreaker #android #approov #cybersecurity #degoogle #mobileprivacy #punktmc03 #righttorepair #technews #upwardlymobile

Approov Mobile Security

@approov.bsky.social

2 months ago

Unmasking "Wonderland" – The New Wave of Android Droppers & SMS Stealers In this episode of Upwardly Mobile, we dive deep into the evolving landscape of Android malware. We break down the emergence of Wonderland (formerly WretchedCat), a sophisticated SMS stealer targeting users in Uzbekistan through legitimate-looking "dropper" applications. We explore how threat actors, specifically the "TrickyWonders" group, are leveraging Telegram and malicious ad campaigns to bypass security checks and hijack devices. We also discuss the broader trend of Malware-as-a-Service (MaaS), including new threats like Cellik, Frogblight, and NexusRoute that are lowering the barrier to entry for cybercriminals globally. From real-time screen streaming to bypassing Google Play protections, we analyze the tactics defining modern mobile security threats. Key Topics Discussed: - The Rise of Droppers: How malware operators are shifting from "pure" Trojans to "droppers" (like MidnightDat and RoundRift) that appear harmless to evade detection before deploying payloads. - Wonderland's Capabilities: How this malware establishes bidirectional communication to intercept OTPs, steal contacts, and execute USSD requests. - The MaaS Economy: A look at the "Cellik" RAT, which offers one-click APK building to bundle malware inside legitimate apps, and "Frogblight," which targets users via fake court documents. - Government Impersonation: How "NexusRoute" is targeting users in India by mimicking government service portals to steal financial data and UPI PINs. - Defense Strategies: The importance of blocking unknown source installations and monitoring for suspicious SMS/USSD patterns. Sponsored By: This episode is brought to you by Approov. Stop mobile app abuse and API misuse. Ensure that the requests your API handles are from the genuine mobile app running on a safe mobile device. 👉 Visit our sponsor: https://approov.io/ Relevant Links & Source Materials: - The Hacker News: https://thehackernews.com/2025/12/android-malware-operations-merge.html - SC Media: https://www.scworld.com/brief/android-malware-wonderland-evolves-with-dropper-apps-targeting-uzbekistan - Cypro: https://www.cypro.se/2025/12/22/android-malware-operations-merge-droppers-sms-theft-and-rat-capabilities-at-scale/ Keywords: Android Malware, Wonderland, SMS Stealer, Dropper Apps, Mobile Security, Remote Access Trojan (RAT), TrickyWonders, Cybersecurity, One-Time Password (OTP) Theft, Malware-as-a-Service, Approov.     

📣 New Podcast! "Unmasking "Wonderland" – The New Wave of Android Droppers & SMS Stealers" on @Spreaker #androidmalware #approov #appsecurity #cybersecurity #infosec #mobilesecurity #technews #upwardlymobile #wonderlandmalware

Approov Mobile Security

@approov.bsky.social

2 months ago

2026 Mobile API and AI Security Predictions 2026 Mobile API and AI Security Predictions Episode Summary: In this episode of Upwardly Mobile, we audit the accuracy of Approov’s 2025 cybersecurity forecast. Of the seven trends predicted, four proved to be "absolutely correct." We break down these key hits: the dual-use of AI by attackers and defenders, the undeniable dominance of cross-platform development, the crackdown on open-source supply chain risks, and the heavy impact of new global breach reporting mandates. The 4 Mobile Security Trends That Defined the Year Key Topics — The 4 Correct Predictions: • 1. AI’s Double-Edged Sword: We discuss how 2025 wasn't just about AI hype—it was about operational impact. Attackers utilized LLMs to lower the bar for API abuse and generate scripts to bypass WAFs, while defenders leaned on AI for anomaly detection and scan interpretation to speed up code reviews. • 2. Cross-Platform is King: The prediction that cross-platform development would be "the way forward" held true. We analyze how Flutter and React Native maintained dominance in 2025, becoming the norm for enterprise and fintech apps, though Huawei’s HarmonyOS remained a regional outlier. • 3. The Open Source Crackdown: Scrutiny on open-source software (OSS) intensified as predicted. With attackers targeting ecosystems like npm and PyPI, and regulations like the EU CRA enforcing SBOMs, organizations were forced to verify their supply chains and adopt runtime protection to catch tampering. • 4. The Breach Reporting Crunch: Approov correctly forecasted that breach reporting would demand massive investment. With the EU NIS2 Directive and PCI DSS 4.0 coming into full effect, the focus shifted from simple disclosure to operational resilience—requiring companies to report incidents in hours, not days. Featured Resources & Links: • Approov Report: https://www.google.com/url?sa=E&q=https%3A%2F%2Fapproov.io%2Fblog%2Fapproov-predicted-7-mobile-cybersecurity-trends-for-2025-did-they-happen – The full retrospective on which predictions hit the mark and which were too optimistic (like the adoption of certificate pinning). • Expert Insights: https://www.google.com/url?sa=E&q=https%3A%2F%2Fwww.lastwatchdog.com%2Flw-roundtable-part-2-mandates-surge-guardrails-lag-intel-from-the-messy-middle%2F – Further reading on the friction between compliance mandates and security realities. Sponsor: This episode is brought to you by Approov. Don’t let your mobile app be the weak link. Approov provides comprehensive runtime security, ensuring that only your genuine app communicates with your API. • Visit: https://www.google.com/url?sa=E&q=https%3A%2F%2Fapproov.io • Solutions: https://www.google.com/url?sa=E&q=https%3A%2F%2Fapproov.io%2Fproduct%2Fruntime-secrets-protection and https://www.google.com/url?sa=E&q=https%3A%2F%2Fapproov.io%2Fproduct%2Fapi-security. Keywords: Mobile Security, Cybersecurity Predictions, AI Threats, Flutter, ReactNative, Open Source Security, SBOM, NIS2 Compliance, Supply Chain Attacks, Approov, API Security. 

📣 New Podcast! "2026 Mobile API and AI Security Predictions" on @Spreaker #ai #apisecurity #approov #compliance #cybersecurity2025 #mobileappsecurity #opensource #upwardlymobile

Approov Mobile Security

@approov.bsky.social

2 months ago

The 3.5 Billion WhatsApp Scraping Flaw: Is Your Mobile API Leaking? The 3.5 Billion WhatsApp Scraping Flaw: Is Your Mobile API Leaking? Episode Summary: In this episode, we break down a massive vulnerability discovered by researchers at the University of Vienna and SBA Research that allowed them to scrape data from roughly 3.5 billion WhatsApp accounts globally. We explore how a lack of rate limiting on the specific GetDeviceList API endpoint turned a benign contact discovery feature into a massive "enumeration oracle," allowing a single university server to query over 100 million numbers per hour. We discuss the types of data exposed—including active status, device types, public encryption keys, and millions of profile photos—and the implications for user privacy, particularly in regions where WhatsApp is banned like China and Iran. Finally, we cover Meta’s response to the disclosure and why industry experts are calling this a "masterclass in negligence" regarding API security. Key Topics Discussed: - The Vulnerability: How researchers used the GetDeviceList API to bypass safeguards and identify valid accounts across 245 countries. - The Scale: How a single server sustained 7,000 requests per second to verify 3.5 billion accounts without being blocked. - The Data: The exposure of profile images, "about" text, and public keys, and how this data correlates with previous Facebook leaks. - The Security Lesson: Why "does this number exist?" lookup APIs are inherently dangerous without strict behavioral monitoring and rate limiting. Sponsor: This episode is supported by Approov. When mobile app security is an afterthought, user privacy becomes collateral damage. Approov ensures that only genuine mobile app instances, running on safe mobile devices, can access your backend APIs. - Visit the Sponsor: https://approov.io/ Featured Sources & Further Reading: - BleepingComputer: https://www.bleepingcomputer.com/ – Detailing the mechanics of the GetDeviceList abuse and the global scope of the data scrape. - Malwarebytes: https://www.malwarebytes.com/ – Analysis of the privacy implications, including the exposure of users in restrictive regimes. - Privacy Guides: https://www.privacyguides.org/ – Discussing the patch and how alternative messengers handle contact discovery. Keywords: WhatsApp, API Security, Rate Limiting, Data Scraping, Mobile Security, Cybersecurity, Meta, Privacy, Enum, GetDeviceList, Infosec, Approov. 

📣 New Podcast! "The 3.5 Billion WhatsApp Scraping Flaw: Is Your Mobile API Leaking?" on @Spreaker #apisecurity #approov #cybersecurity #dataprivacy #mobileappsecurity #upwardlymobile #whatsapp

Approov Mobile Security

@approov.bsky.social

3 months ago

Apple's DMA Non-Compliance: An Open Letter Apple's DMA Non-Compliance: An Open Letter In this episode of *Upwardly Mobile*, we break down the seismic shift in the mobile app landscape following the European Commission’s decision to formally fine Apple €500 million for breaching the Digital Markets Act (DMA). We explore why regulators view Apple’s recent changes not as genuine adherence to the law, but as "malicious compliance"—a deliberate attempt to technically meet requirements while maintaining control and fees. We also discuss the December 2025 Open Letter sent by app developers to EU President Ursula von der Leyen, which argues that Apple’s new 20% commission on external transactions continues to violate the law and stifle fair competition. Finally, we contrast the situation in Europe with recent US court rulings involving Epic Games, where judges have ordered Apple to stop charging for services it doesn't provide, raising the question: Why are European developers getting a worse deal?. Key Topics Discussed: *   **The €500M Fine:** The European Commission found Apple in breach of "anti-steering" obligations, restricting developers from directing users to cheaper offers outside the App Store. *   **"Malicious Compliance":** An analysis of how Apple’s fee structures and "scare screens" are viewed by critics and regulators as structural impediments to the DMA’s goals. *   **The Meta Connection:** A look at the parallel €200M fine imposed on Meta regarding their "pay or consent" model. *   **The Developer Pushback:** Insights from the "CleanV2" Open Letter, where developers demand the removal of new commission fees that range up to 20%. *   **Transatlantic Tensions:** How the US Ninth Circuit Court of Appeals ruling regarding Epic Games highlights disparities in global enforcement. **Sponsor:** This episode is brought to you by **Approov**. Securing mobile apps is hard; Approov makes it easy. Ensure your APIs are only accessed by genuine instances of your mobile app and block scripts, bots, and modified apps. **Visit: [https://approov.io](https://approov.io)** **Resources & Source Materials:** *   **European Commission Press Release:** Details on the April 2025 fine regarding Apple’s anti-steering practices. *   **Kluwer Competition Law Blog:** "The DMA's Teeth: Meta and Apple Fined by the European Commission" by Alba Ribera Martínez. *   **Clean App Foundation Open Letter:** The December 2025 appeal to the European Commission regarding Apple's persistent non-compliance. *   **Analysis of US Rulings:** Context on the Epic Games vs. Apple court case and fee limitations. Digital Markets Act, DMA, Apple Fine, App Store Fees, Anti-Steering, Malicious Compliance, European Commission, Margrethe Vestager, Sideloading, Epic Games, Mobile App Security, Tech Policy, Antitrust.

📣 New Podcast! "Apple's DMA Non-Compliance: An Open Letter" on @Spreaker #antitrust #apple #approov #appstore #digitalmarketsact #dma #eu #mobiledev #upwardlymobile

Approov Mobile Security

@approov.bsky.social

3 months ago

Sanchar Saathi |The Mobile App Triggering India's Surveillance Firestorm Sanchar Saathi: The Mandatory Cyber Safety App Triggering India's Surveillance Firestorm In this critical episode of "Upwardly Mobile," we dive into the escalating controversy surrounding India's Sanchar Saathi app, a government-mandated digital tool that is fueling a nationwide debate over state surveillance and digital privacy. Designed as a citizen-centric safety tool to combat telecom fraud and track lost or stolen devices using their unique IMEI, the app has been lauded by the government for its success in blocking millions of fraudulent connections and stolen phones. However, a recent directive mandating its pre-installation on all new smartphones sold in India has drawn fierce criticism from privacy advocates, opposition politicians, and major tech firms. What You Will Learn in This Episode: The Core Conflict: Safety vs. Snooping - The Mandate: The Indian telecom ministry privately ordered all smartphone manufacturers to preload Sanchar Saathi on new devices within 90 days, requiring the app to be "visible, functional, and enabled" upon first setup. This directive could eventually roll out the app to more than 735 million existing phone users via software updates. - Government Defense: Officials state the app is strictly for cyber security and curbing the "serious endangerment" caused by IMEI tampering, promising adequate security for personal information. They also claim the app is optional and does not read private messages. - Surveillance Fears: Privacy experts and the political opposition argue the mandate is unconstitutional and creates a massive surveillance surface area. Opposition leaders have even compared the move to 'Pegasus'. Technical Deep Dive into Privacy Risks - The Sanchar Saathi app requests a range of "dangerous" or "high-risk" permissions. - The app has the capability to read call logs and all incoming SMS, technically allowing it to parse bank transaction alerts, 2FA codes, and map a user's social graph. - It accesses device identifiers, binding a user's identity to the hardware IMEI, which breaks standard rules for resettable identifiers and aids tracking. - If pre-installed as a system-level application (the proposed state), experts warn that permissions could be auto-granted without user consent, the app could run continuous background services, and it would be virtually impossible for 99% of users to uninstall. - The privacy policy is weak, lacking explicit mechanisms for data deletion, correction, or a clear opt-out feature. Industry Resistance - Tech giants were given 90 days to comply with the pre-installation mandate. - Apple has specifically resisted the mandate, citing concerns over privacy and system security, as iPhones require explicit user confirmation for permissions and prevent automatic background registration. - The mandate is technically easier to implement on Android devices, which make up over 95% of the Indian smartphone market. Keywords Sanchar Saathi, India digital privacy, state surveillance, government mandate, telecom fraud, cyber safety app, IMEI tracking, pre-installation controversy, Android security, iOS privacy, Apple resistance, call log permissions, data deletion rights, digital rights, Indian politics. Digital Autonomy and the Sanchar Saathi App - - Link 1: https://indianexpress.com/article/explained/explained-sci-tech/telecom-scindia-sanchar-saathi-optional-key-concerns-10397728/ - Link 2: https://www.ndtv.com/india-news/sanchar-saathi-communications-ministry-jyotiraditya-scindia-big-brother-or-cybersafety-boost-deep-dive-into-sanchar-saathi-app-9735477 - Link 3: https://indianexpress.com/article/technology/tech-news-technology/sanchar-saathi-app-preinstalled-android-ios-privacy-security-concerns-10397922/ - Link 4: https://www.bbc.com/news/articles/cedxyvx74p4o - Link 5: https://www.reuters.com/sustainability/boards-policy-regulation/what-is-indias-politically-contentious-sanchar-saathi-cyber-safety-app-2025-12-02/ Sponsor This episode is brought to you by https://approov.io/podcast, helping developers secure their mobile APIs and prevent reverse engineering and unauthorized data access. - Sponsor Website: approov.io

📣 New Podcast! "Sanchar Saathi |The Mobile App Triggering India's Surveillance Firestorm" on @Spreaker #android #apple #approov #bigbrother #cybersafety #digitalprivacy #indiatech #samsung #sancharsaathi #statesurveillance #telecomfraud #upwardlymobile #xiaomi

Approov Mobile Security

@approov.bsky.social

3 months ago

Supply Chain Security Unpacked: Combating Dependency Confusion & Poisoned Pipelines Supply Chain Security Unpacked: Combating Dependency Confusion, Poisoned Pipelines Episode Notes: The software supply chain, the "backbone of modern software development," is under unprecedented assault, with attacks aimed at libraries and development tools soaring by an astounding 633% year-over-year. This episode explores the evolution of supply chain threats, examining everything from software vulnerabilities and malicious maintainers to hidden risks lurking in hardware and commercial binaries, and details the cutting-edge defenses developers are deploying to fight back. The Evolving Threat Landscape: Implicit Trust Exploited Modern attacks exploit the implicit trust developers place in package managers and public repositories. Key threats discussed include: - Dependency Confusion: First identified by Alex Birsan, this attack exploits package managers that prioritize packages found in public repositories (especially those with a higher version number) over identically named private packages. Attackers use reconnaissance to pinpoint internal package names (often by examining manifest files like package.json), publish a malicious package with the same name and a higher version to a public repository, and wait for the target application's build process to pull and execute the malicious code. Vectors for this attack include exploiting namespaces, DNS Spoofing, and manipulating CI/CD security settings. - Widespread Malware and Stolen Secrets: The npm ecosystem was recently hit by the self-replicating "Shai-Hulud" worm, which compromised over 500 packages and harvested sensitive credentials, including GitHub Personal Access Tokens (PATs) and API keys for cloud services like AWS, GCP, and Microsoft Azure. Stolen credentials remain a reliable attack vector, leading to incidents where attackers published malicious code on behalf of trusted entities (e.g., Nx, rspack). - Poisoned Pipelines and Malicious Maintainers: Highly sophisticated attackers are compromising build and distribution systems directly, bypassing code reviews. This includes notorious attacks like SolarWinds and compromises targeting GitHub Actions pipelines (e.g., Ultralytics and reviewdog/actions-setup). Furthermore, the XZ Utils backdoor highlighted the risk of malicious maintainers who build trust over years before inserting sophisticated backdoors into critical open-source projects. - Code Rot and Vulnerable Open Source: A survey of popular open-source packages found them rife with vulnerabilities, with an average of 68 vulnerabilities across 30 packages scanned, including many critical and high-severity flaws. Even actively maintained, high-traffic packages like Torchvision contained dozens of vulnerabilities, despite frequent updates. Defense and Verification: Making Trust Explicit To counter these escalating threats, the industry is focusing on making trust assumptions explicit and verifiable: - Supply-chain Levels for Software Artifacts (SLSA): SLSA is a security standard that helps consumers verify the process by which an artifact was created using a signed provenance file. Achieving Level 3 compliance involves stringent build platform hardening to prevent the forgery of provenance files. - Trusted Publishing and Attestations: Platforms like PyPI have implemented Trusted Publishing, which removes the need for developers to manage long-lived API tokens by utilizing short-lived OIDC tokens issued by the build platform. Building on this, digital attestations (driven by PEP 740) cryptographically bind published packages to their build provenance using Sigstore. - CI/CD Security Tools: Tools like Zizmor perform static analysis for GitHub Actions to flag subtle vulnerabilities like template injection or dangerous triggers. Capslock is an experimental tool used for Go language packages that statically identifies capabilities (like network access or file system operations), allowing developers to verify what code can actually do, regardless of where it came from. - Preventing Confusion: Developers can mitigate Dependency Confusion through strict naming conventions, proactively reserving namespaces (or "namesquatting" on platforms like PyPI), utilizing private package repositories with stringent access controls (RBAC/MFA), and enforcing package whitelisting and version locking using files like package-lock.json. - Verifying Commercial Binaries: Risks also lurk in closed-source commercial software ("black-box" binaries). The compromise of Justice AV Solutions (JAVS) demonstrated how malware (RustDoor) can be implanted in a backdoored installer; sophisticated tools like differential analysis are necessary to detect signs of tampering and unvetted files (such as the typosquatted ffmepg.exe). Organizations must adopt a "Don't Trust, but Verify" approach to all software received from suppliers. - The Future of Vulnerability Management: The cybersecurity community is moving beyond sole reliance on CVEs, especially following the NVD backlog experienced in 2024. Comprehensive security now requires visibility into threats like malware, tampering, secret leaks, and lack of hardening, rather than just known vulnerabilities. NIST SP 800-204D outlines crucial strategies for integrating SSC security measures—including generating provenance data—into DevSecOps CI/CD pipelines. Relevant Links and Resources: - Learn more about Dependency Confusion Prevention and DevSecOps Orchestration: https://approov.com/ - NIST SP 800-204D: Strategies for the Integration of Software Supply Chain Security in DevSecOps CI/CD Pipelines: https://doi.org/10.6028/NIST.SP.800-204D Keywords: Software Supply Chain Security, Dependency Confusion, Hardware Trojan, SLSA Framework, CI/CD Pipeline Security, DevSecOps, Trusted Publishing, PyPI, npm, Zizmor, Build Provenance, Side-Channel Attacks, Malware, Cryptojacking, NVD Backlog, Digital Attestations, Zero Trust. 

📣 New Podcast! "Supply Chain Security Unpacked: Combating Dependency Confusion & Poisoned Pipelines" on @Spreaker #approov #appsec #ci_cd #cybersecurity #dependencyconfusion #devsecops #nist #slsa #softwareintegrity #supplychainsecurity #threatintelligence

Approov Mobile Security

@approov.bsky.social

3 months ago

Black Friday's Hidden Threat: Stopping AI-Powered Fraud and Mobile Commerce Exploits Black Friday's Hidden Threat: Stopping AI-Powered Fraud and Mobile Commerce Exploits The biggest shopping days of the year—Black Friday and Cyber Monday—have also become the prime hunting grounds for cybercriminals, with global financial losses from attacks predicted to hit $10 billion in 2024. In this episode, we dive deep into the rising statistics shaping financial cybersecurity during the holiday shopping season, focusing on how sophisticated, AI-driven scams and mobile app vulnerabilities are creating a perfect storm for retailers and consumers alike. Episode Highlights: The State of Financial Cybercrime Cybercriminal activity spikes by 70% during Black Friday compared to regular shopping days. Statistics show that cyberattacks during this period were projected to rise by 20% in 2024, following a 15% increase in 2023. Key Threats and Data: - The Rise of Fake Shops: Scammers are evolving at an unprecedented pace, using AI to generate persuasive copy and fully functional storefront templates that mimic legitimate communication flawlessly. A recent analysis found a 250% jump in fake Black Friday shops leading up to the sales weekend. - Targeting E-commerce: E-commerce platforms experience a 65% surge in phishing attacks. Phishing scams remain the most common threat, accounting for 42% of attacks on financial transactions during the 2023 holiday shopping period. - Prevalent Fraud Types: Financial institutions report detecting 30% more fraudulent transactions during Cyber Monday. Card-not-present fraud was the leading method used by cybercriminals in 2023, accounting for over 75% of online fraud cases. Credential stuffing incidents surged by 80% during Cyber Monday in 2023, affecting over 40 million accounts globally. - The Cost: Financial fraud cases during holiday shopping periods account for nearly $8.5 billion annually. Small and medium-sized businesses (SMBs) are highly vulnerable, reporting an average loss of $120,000 per cyberattack. The Mobile Frontline: While many focus on suspicious websites, the true cybersecurity frontline for e-commerce is increasingly within mobile apps. Attacks on mobile apps used for shopping increased by 50% in 2023, often involving malicious app clones. Attackers exploit vulnerabilities like Man-in-the-middle (MitM) attacks intercepting API traffic and extracting API keys reverse-engineered from app binaries. Standard defenses like TLS encryption and certificate pinning offer necessary but incomplete protection. Industry Response: Financial institutions are bolstering security by integrating biometric authentication into 50% of mobile banking apps, adopting real-time transaction monitoring (reducing fraud by 40%), and using tokenization technology in 65% of online transactions. Furthermore, Zero Trust architecture is gaining traction, with 55% of organizations adopting it to secure financial systems. Sponsor Spotlight This episode is brought to you by Approov, the mobile security platform addressing vulnerabilities where they start: the mobile API. Approov provides a pragmatic defense-in-depth approach by ensuring that only genuine, unmodified apps connect to your backend. Approov neutralizes Black Friday exploits by using dynamic attestation to verify app integrity, and protects against API key theft by delivering short-lived, attested tokens at runtime, preventing API keys from residing within the app binary. Protect your mobile commerce from sophisticated fraud. Learn more about Approov's Mobile API Protection: - https://approov.io/podcast Relevant Source Links For more information and detailed statistics referenced in this summary: - Financial Cybersecurity Statistics for Black Friday and Cyber Monday 2025 (via CoinLaw): [Link to CoinLaw Article] - Online scams skyrocket before Black Friday – NordVPN warns what shoppers should watch out for (via TechRadar): [Link to TechRadar Article] - https://cybermagazine.com/articles/darktrace-reports-692-surge-in-black-friday-cyber-scams  Keywords & Hashtags (SEO Optimized) Keywords: Black Friday, Cyber Monday, cybersecurity statistics, financial fraud, e-commerce security, mobile commerce, API protection, card-not-present fraud, phishing scams, ransomware, credential stuffing, AI-powered scams, fake shops, Approov, NordVPN, retail cybercrime, tokenization, Zero Trust. 

📣 New Podcast! "Black Friday's Hidden Threat: Stopping AI-Powered Fraud and Mobile Commerce Exploits" on @Spreaker #aiscams #apisecurity #approov #blackfridayfraud #cybermonday #cybersecurity #digitalpayment #ecommercesecurity #mobilesecurity #upwardlymobile

Approov Mobile Security

@approov.bsky.social

3 months ago

X Joins App Fairness Coalition to Combat Monopolies In this pivotal episode of https://approov.io/podcast, we dive into the significance of https://x.com (formerly known as Twitter) joining the https://appfairness.org/(CAF). This move signals growing momentum in the global effort to reform the mobile app ecosystem, currently dominated by Apple and Google, whose practices are alleged to harm consumers and developers alike. We examine X's commitment to dismantling monopolistic practices and fostering a digital future where competition thrives and innovation is rewarded. Furthermore, we discuss the context of this fight, including the recent U.S. Department of Justice (DOJ) antitrust complaint filed against Apple. CAF asserts that Apple’s alleged illegal conduct—including abusing App Store guidelines to increase prices and choke off competition—must be addressed, urging Congress to pass legislation like the Open App Markets Act. Tune in to understand how companies are pushing back against the "shackles on developers" to create a level playing field for the more than 80 members of this independent nonprofit organization. Discussion Points - Dismantling Monopolies: X’s Head of Global Government Affairs stated that joining CAF is a testament to their commitment to dismantling monopolistic practices and building a mobile ecosystem that truly serves its users and fosters growth. - The Problem with Gatekeepers: The current mobile app ecosystem is dominated by Apple and Google, who use their power to harm developers and users through excessive costs and restrictions on innovation. Global Policy Counsel for CAF noted that businesses on platforms like X are harmed by these anticompetitive app store practices. - The Antitrust Fight: The DOJ, along with 16 attorneys general, filed an antitrust complaint against Apple, accusing the company of illegally monopolizing smartphone markets. CAF supports this strong stand against Apple’s "stranglehold over the mobile app ecosystem". - The Path Forward: CAF advocates for legislation, like the Open App Markets Act, to create a free and open mobile app marketplace and put an end to the anticompetitive practices of all mobile app gatekeepers. - About CAF: The Coalition for App Fairness is an independent nonprofit organization focused on protecting consumer choice, fostering competition, and creating a level playing field for app and game developers globally. https://approov.comSponsored Segment:  The increasing regulatory and commercial pressures are weakening app store monopolies. As the mobile ecosystem decentralizes, the need for robust, independent security is crucial. Our sponsor, Approov, provides strong, app-centric security solutions that operate independently of basic app store protections. Approov helps mobile app developers reduce security dependencies on app stores by delivering runtime protection and attestation for mobile apps and their APIs, shielding against tampering and unauthorized access. Approov’s approach decentralizes security, ensuring developers are not limited by the basic security checks provided by Apple, Google, or any third-party app store (especially relevant as regulations like the EU DMA take effect). Key security features include: - https://approov.io/mobile-app-security/rasp/dynamic-cert-pinning/: Secures connections against man-in-the-middle attacks and allows instant over-the-air (OTA) updates without requiring republishing through app stores. - https://approov.io/mobile-app-security/rasp/runtime-secrets/: API keys and secrets are removed from the app and delivered only to verified app instances, protecting against reverse engineering and credential scraping attempts. - https://approov.io/mobile-app-security/rasp/: Provides real-time shielding against threats like OS manipulation or hostile frameworks, regardless of how or where the app is distributed, including alternative app stores. This ability to deliver critical updates and security policies directly from Approov’s cloud platform ensures the quickest possible response to threats, bypassing store-mediated app updates. Keywords  X, Twitter, Coalition for App Fairness (CAF), Mobile App Ecosystem, App Store Monopolies, Antitrust, Apple Antitrust, Google Play Store, Developer Freedom, App Competition, Open App Markets Act, Approov, App Security, API Protection, Runtime Protection, App Attestation, EU DMA.        Relevant Links - X Joins CAF Announcement: [Link to source (though the specific URL is not provided in the excerpts, we reference the content that would link to this news)] - CAF Mission & Membership: appfairness.org - DOJ Antitrust Complaint Context: [Link to source (though the specific URL is not provided in the excerpts, we reference the content)] - Sponsor Approov: Secure your mobile apps independently of app stores at approov.com - Approov Security Details: - How Approov Works: [Link to source] - Approov vs. Mobile App Hardening: [Link to source] - Approov's Role in a Post-DMA Landscape: [Link to source and]

📣 New Podcast! "X Joins App Fairness Coalition to Combat Monopolies" on @Spreaker #antitrust #appfairness #approov #appsecurity #appstorereform #developerfreedom #mobilemonopolies #openappmarketsact #upwardlymobile #x

Approov Mobile Security

@approov.bsky.social

4 months ago

The Edge Advantage: Why Cloudflare and Approov Outpace Zscaler in API Security? Remote Attestation vs. RASP: Securing Mobile APIs at the Edge (Zscaler vs. Approov/Cloudflare) On this episode of Upwardly Mobile, we dive deep into the most critical architectural debate in mobile API security today: Does security enforcement belong on the client device (RASP) or off-device at the network edge (Remote Attestation)? We break down the philosophical and technical differences between the integrated Zscaler ZSDK approach, which bundles Runtime Application Self-Protection (RASP), and the specialized, edge-native partnership between Approov and Cloudflare. Discover why security experts argue that because the attacker ultimately controls the client environment, remote attestation is superior for defense against sophisticated, targeted attacks. Episode Highlights & Key Concepts The Philosophical Divide: RASP vs. Remote Attestation The core of the debate centers on where security decision logic is insulated. - RASP (Runtime Application Self-Protection): This approach implements security logic within the application code to detect threats locally during runtime, often used for real-time overlay fraud, app tampering, and emulator abuse detection. - The Risk: Any locally enforced logic provides a target for advanced adversaries. Attackers can potentially reverse-engineer RASP checks and bypass local controls to execute API requests from a tampered application instance. - Remote Attestation (Approov/Cloudflare): This specialized approach verifies that only a genuine, untampered app can access APIs, protecting backend systems from unauthorized or rogue applications. - Superior Resilience: Approov’s architecture minimizes local enforcement, ensuring attestation decisions are made entirely in the cloud service. This insulates the enforcement logic on the backend, offering superior resilience against sophisticated, targeted attacks. - Zero Feedback Loop: A key security advantage is that the attacker receives no feedback from the client on why the token validation failed at the edge, significantly raising the cost and complexity of a successful attack bypass. Architectural and Operational Advantages The comparison between the integrated Zscaler Zero Trust Exchange (ZTNA/SSE) model and the Approov/Cloudflare Edge-First (WAAP) model highlights major differences in deployment, performance, and operational cost. - Enforcement Location and TCO: The Approov/Cloudflare model focuses enforcement entirely at the Cloudflare edge using serverless functions (Workers or API Shield). This is described as a zero-operations deployment model that removes the need for customer-managed infrastructure components like Zscaler’s required App Connectors. The serverless model accelerates time-to-value and minimizes maintenance overhead. - API Key Protection: Approov provides a critical security layer by leveraging attestation guarantees to securely deliver secrets, such as API keys, just-in-time to the application only when the environment is verified as genuine and unmodified. This capability directly mitigates the risks associated with reverse engineering hard-coded keys. - Performance and Scale: The Cloudflare/Approov integration leverages Cloudflare’s global, high-performance network. Comparative tests show Cloudflare is significantly faster than Zscaler in various Zero Trust scenarios, a crucial factor for a smooth user experience and ensuring users don't bypass security controls. Furthermore, Approov offers a commercial attestation fabric built for scale, guaranteeing no quotas or throttling on attestation traffic for high-volume apps. - API Governance: Cloudflare API Shield enhances protection with rigorous positive security via OpenAPI schema validation at the edge. This preemptively guards against modern API security risks like Broken Object Level Authorization (BOLA) by ensuring that only traffic conforming to the documented API structure is accepted. Secure Your Mobile APIs with the Industry's Leading Attestation Solution This episode is proudly brought to you by Approov, the definitive solution for continuous and deterministic mobile app attestation. Approov ensures that only genuine, untampered instances of your mobile application can access your backend APIs, protecting against bot attacks, API abuse, and sophisticated tampering. Learn how to deploy mobile API security today: 🔗 https://approov.io/  Keywords: Mobile API Security, Remote Attestation, RASP, Approov, Cloudflare, Zscaler, API Integrity, Mobile App Protection, Zero Trust Architecture, Edge Security, API Abuse Prevention, Serverless Security, JWT Attestation, Mobile Bot Mitigation, Cloudflare Workers, App Attestation. 

📣 New Podcast! "The Edge Advantage: Why Cloudflare and Approov Outpace Zscaler in API Security?" on @Spreaker #apiprotection #appintegrity #approov #cloudflare #cybersecurity #edgesecurity #mobileappdev #mobilesecurity #rasp #remoteattestation #zerotrust #zscaler #zsdk

Approov Mobile Security

@approov.bsky.social

4 months ago

App Store Revolution: Google Play Opens to Third-Party Payments (The Epic Games Aftermath) Upwardly Mobile: Episode Notes Episode Title: App Store Revolution: Google Play Opens to Third-Party Payments (The Epic Games Aftermath) Summary: In this episode of Upwardly Mobile, we break down the monumental shift in the Android ecosystem following the Supreme Court’s refusal to hear Google's final appeal. Google has finally opened its Google Play app store to third-party payment options for U.S. developers, settling a multi-year legal battle initiated by Epic Games. We discuss what this means for developers seeking to maximize revenue, the new freedom to direct users to cheaper external payment options, and the resulting challenges in maintaining app integrity and security now that developers are operating outside Google Play Billing exclusivity. Plus, we explore crucial security solutions, like Approov, that can help developers protect their apps when relying less on Google Mobile Services (GMS) for integrity checks. Key Takeaways - Policy Shift: Following years of legal challenges, Google is now required to allow U.S. app developers to use alternative payment methods and link users directly to external payment sources. This means developers can process payments outside of Google’s ecosystem and inform users about alternative pricing. - End of Exclusivity: Previously, Google generally mandated the use of Google Play Billing and collected a commission on nearly every in-app purchase. Now, developers can provide direct links to external checkout pages and offer options like PayPal or their own payment systems. - Timeline and Scope: This change became effective immediately as of October 29, 2025. However, the new rules currently apply only in the U.S. and the District Court order is set to expire on November 1, 2027. - Security Challenges: While developers gain freedom and potential revenue maximization by avoiding Play Store commissions, distributing and processing payments externally requires implementing their own robust security, update, and analytics systems, as Play services like integrity verification may not be available. - App Attestation Alternative: For developers building non-GMS Android apps or those seeking customizable security outside of Google’s structure, Approov provides a solution. Approov is a runtime application self-protection (RASP) tool that offers app attestation—verifying the integrity and authenticity of an app and the device it runs on—without relying on Google PlayIntegrity or SafetyNet. Sponsored by Approov Protect your app and APIs regardless of your payment processing choices. Approov offers comprehensive runtime application self-protection (RASP) and serves as a reliable, GMS-independent alternative to Google PlayIntegrity for robust app attestation and real-time threat detection. Learn more or start a free trial today: https://notebooklm.google.com/notebook/approov.io Relevant Links & Resources - Google Opens App Store to Third-Party Payment Systems (PaymentsJournal): https://www.paymentsjournal.com/google-opens-app-store-to-third-party-payment-systems/ - Google Play now allows Android apps to use other billing systems in the US (9to5Google): https://9to5google.com/2025/10/30/google-play-now-allows-android-apps-to-use-other-billing-systems-in-the-us/ - How Organizations Can Chart the Course to Agentic Commerce (Must Read): [Relevant link to PaymentsJournal content on commerce] (October 31, 2025) Keywords Google Play, third-party payments, Epic Games, app store, commission, app security, app attestation, Approov, U.S. court ruling, Google Play Billing, non-GMS apps, developer revenue, digital payments, emerging payments, API security.            

📣 New Podcast! "App Store Revolution: Google Play Opens to Third-Party Payments (The Epic Games Aftermath)" on @Spreaker #approov #appsecurity #appstore #developerfreedom #digitalbanking #emergingpayments #epicgames #fintech #googleplay #mobilepayments #thirdpartypayments

Approov Mobile Security

@approov.bsky.social

4 months ago

NPM Nightmare: & Cloudflare AI That Secured End Users From 2 Billion Weekly Malicious Downloads The Billion-Download Backdoor: Defending Client-Side Supply Chains Against Crypto-Draining NPM Attacks -------------------------------------------------------------------------------- Episode Notes In early September 2025, the open-source software ecosystem faced a massive supply chain attack when attackers compromised trusted maintainer accounts on npm using targeted phishing emails. This security breach led to the injection of malicious code into 18 widely used npm packages—such as chalk, debug, and ansi-styles—which together account for more than 2 billion downloads per week. This episode dives into the mechanics of the attack, the threat posed by the complex malware deployed, and the role of advanced AI-powered defenses in preventing client-side disaster. Key Takeaways The Threat Landscape The attackers' primary goal was crypto-stealing or wallet draining. The compromised packages contained obfuscated JavaScript, which, when included in end-user applications (including web projects and mobile apps built with frameworks like React Native or Ionic), was activated at the browser level. This malware would intercept network traffic and API requests, ultimately swapping legitimate cryptocurrency addresses (including Bitcoin, Ethereum, and Solana) with the attackers' wallets. The attack leveraged the human factor, as maintainers were tricked by phishing emails urging them to update two-factor authentication credentials via a fake domain, npmjs[.]help. The Evolution of Malware: Shai-Hulud Beyond crypto-hijacking, researchers detected a complex self-replicating worm dubbed Shai-Hulud. This advanced payload targets development and CI/CD environments: • Autonomous Propagation: Shai-Hulud uses existing trust relationships to automatically infect additional NPM packages and projects. • Credential Theft: Using stolen GitHub access tokens, the worm lists and clones private repositories to attacker-controlled accounts. • Secret Harvesting: It downloads and utilizes the secret-scanning tool TruffleHog to harvest secrets, keys, and high-entropy strings from the compromised environment. • Malicious Workflows: Shai-Hulud establishes persistence by injecting malicious GitHub Actions workflows into repositories, enabling automated secret exfiltration. Automated Defense with AI Security Cloudflare’s client-side security offering, Page Shield, proved critical in mitigating this threat. Page Shield assesses 3.5 billion scripts per day (40,000 scripts per second) using machine learning (ML) based malicious script detection. • Page Shield utilizes a message-passing graph convolutional network (MPGCN). This graph-based model learns hacker patterns purely from the structure (e.g., function calling) and syntax of the code, making it resilient against advanced techniques like code obfuscation used in the npm compromise. • Cloudflare verified that Page Shield would have successfully detected all 18 compromised npm packages as malicious, despite the attack being novel and not present in the initial training data. • While patches were released quickly (in 2 hours or less), Page Shield was already equipped to detect and block this threat, helping users "dodge the proverbial bullet". Security Recommendations To protect against fast-moving supply chain attacks, organizations must maintain vigilance and implement automated defenses: 1. Audit Dependencies: Review your dependency tree, checking for versions published around early–mid September 2025. Developers should pin dependencies to known-good versions. 2. Rotate Credentials: Immediately revoke and reissue any exposed CI/CD tokens, cloud credentials, or service keys that might have been used in the build pipeline. 3. Enforce MFA: Tighten access policies and enforce multi-factor authentication (MFA) on all developer and CI/CD access points. 4. Proactive Monitoring: Monitor build logs and environments for signs of suspicious scanning activity, such as the use of TruffleHog. -------------------------------------------------------------------------------- 🔗 Relevant Links and Resources • Cloudflare: https://blog.cloudflare.com/how-cloudflares-client-side-security-made-the-npm-supply-chain-attack-a-non/     ◦ Cloudflare Page Shield Script detection • Trend Micro Research: What We Know About the NPM Supply Chain Attack • Kaspersky Blog: Popular npm packages compromised 🛡️ Sponsor This episode of Upwardly Mobile is brought to you by our friends at https://approov.io/mobile-app-security/rasp/. -------------------------------------------------------------------------------- Keywords: NPM supply chain attack, Cloudflare Page Shield, Shai-Hulud worm, Cryptohijacker, crypto-stealing malware, client-side security, JavaScript obfuscation, open-source security, dependency audit, CI/CD security, phishing attack, MPGCN, machine learning security, developer accounts compromise, npm packages, software security.          

📣 New Podcast! "NPM Nightmare: & Cloudflare AI That Secured End Users From 2 Billion Weekly Malicious Downloads" on @Spreaker #aiinsecurity #approov #clientsidesecurity #cloudflarepageshield #cryptostealing #cybersecurity #devsecops #javascriptsecurity #npmsecurity #shaihulud #supplychainattack

Approov Mobile Security

@approov.bsky.social

4 months ago

The Unseen Storm: Securing APIs and Protecting Against Key Exposure The Unseen Storm: Securing APIs and Protecting Against Key Exposure This week on Upwardly Mobile, we delve into the hidden dangers lurking within seemingly simple applications and the advanced solutions required to close the modern mobile security trust gap. We analyze a case study involving a basic weather application to illustrate how common development mistakes—like exposing sensitive API keys and neglecting input validation—create catastrophic security vulnerabilities, potentially leading to data breaches, financial loss, and system compromise. The Problem: Client-Side Secrets and Architectural Flaws The proliferation of web applications consuming public APIs has vastly expanded the attack surface. Developers often treat the client environment as trusted, leading to critical architectural failures. We discuss how exposed API keys embedded in client-side JavaScript are considered "low-hanging fruit" for attackers. Key Takeaways from the Security Analysis: - Reconnaissance and Exploitation: Attackers can use tools like curl and grep with regular expressions to scan target URLs for hardcoded API key patterns. Once obtained, keys can be used for unauthorized calls, potentially exceeding quotas and incurring costs. - Interception: Tools like Burp Suite enable attackers to intercept and modify API traffic, revealing the exact structure of API calls, including the API key and parameters. - Injection Attacks: Poor input sanitization on server-side search functionalities is a primary attack vector. We examine verified command snippets used to test for command injection (e.g., appending cat /etc/passwd) and NoSQL Injection (e.g., using MongoDB operator syntax). - Lateral Movement: An exposed API key is often just the beginning. If the key has excessive permissions, it can allow an attacker to enumerate IAM policies, check for sensitive S3 buckets, and even create persistent administrative users, leading to a full cloud account takeover. Defensive Fundamentals for Developers: To combat these threats, security must be shifted left—integrated into the earliest stages of development. We review critical defensive measures: - Environment Variable Security: API keys must never be exposed to the client; they should reside in secure server-side environment variables. The client should request data from your secure server endpoint, which then internally fetches the data from the third-party API using the hidden key. - Rate Limiting: To protect backend APIs from abuse and "Denial-of-Wage" attacks (attacks that incur cost), rate limiting middleware (like express-rate-limit) is essential. This blocks automated scripts by limiting each IP to a set number of requests within a time window. - Cloud Hardening: Security extends to infrastructure. Developers must audit cloud resources, checking S3 bucket policies for leaks and ensuring EC2 security groups only allow necessary web traffic (ports 80 and 443). Closing the Mobile API Security Trust Gap with Positive Authentication While these fundamentals are crucial, mobile app security introduces unique challenges, creating a concerning "trust gap". Traditional security measures like TLS, mutual TLS, embedded API keys, and signature-based approaches are often insufficient, as they are vulnerable to reverse engineering, MitM attacks, and spoofing. We discuss Approov, a solution designed for the mobile world that uses a positive trust model to authenticate the app instance itself, rather than just the user or the connection. - App Attestation: https://approov.io/ uses a challenge-response cryptographic protocol to dynamically measure the integrity of the runtime app image. - Tokens (JWT): Only genuine, untampered apps are granted a short-lived JSON Web Token (JWT). Requests without a valid token are immediately rejected by the backend API. - Protection against Reverse Engineering: Because the system does not rely on static secrets embedded in the app, traditional reverse engineering techniques are ineffective. Approov also provides a runtime secrets protection capability, allowing developers to remove third-party API keys from the app package entirely, substituting them only just in time for the API call after the app has passed attestation. - Benefits: This positive authentication model blocks sophisticated bots, automated scraping systems, and repackaged apps, ensuring that only registered, authentic versions of your application can access your valuable digital assets. Links & Resources Source Material Reference: - Excerpts from "https://undercodetesting.com/the-unseen-storm-how-a-simple-weather-app-exposes-critical-api-security-flaws/" - Excerpts from "https://approov.io/addressing-the-security-trust-gap-in-a-mobile-world" Sponsor: - Learn how Approov protects your revenue and business data by deploying Mobile Security: https://www.approov.io/ Keywords API security, mobile security, API key protection, reverse engineering, input validation, client-side vulnerabilities, app attestation, JWT, zero-trust architectures, rate limiting, cloud security, Denial-of-Wage, Man-in-the-Middle (MitM), Burp Suite, Approov. 

📣 New Podcast! "The Unseen Storm: Securing APIs and Protecting Against Key Exposure" on @Spreaker #apikeys #apisecurity #appauthentication #approov #cybersecurity #devsecops #infosec #mobilesecurity #websecurity #zerotrust

Approov Mobile Security

@approov.bsky.social

4 months ago

UK Competition and Markets Authority (CMA) designate Apple and Google with Strategic Market Status UK CMA Declares Apple & Google Have Strategic Market Status (SMS): The Future of Mobile Competition and Security In this pivotal episode of "Upwardly Mobile," we break down the monumental decision by the UK Competition and Markets Authority (CMA) to officially designate Apple and Google with Strategic Market Status (SMS) in their respective mobile platforms. This move is set to reshape digital markets across the UK and has massive implications for app developers, businesses, and mobile security worldwide. Key Takeaways from the CMA's Decision (Published 22 October 2025): The CMA launched its investigations in January 2025 under the Digital Markets, Competition and Consumers Act 2024 (DMCCA), aiming to address the "unprecedented market power" held by a few large digital firms. - SMS Designation Confirmed: Following consultation with over 150 stakeholders, the CMA confirmed that both Apple and Google meet the legal tests for having Substantial and Entrenched Market Power (SEMP) and a Position of Strategic Significance (POSS) in their mobile platforms. - Scope of Mobile Platforms: The designation applies to the holistic Mobile Platform provided by each company, grouping together highly interconnected digital activities: - Apple: Smartphone Operating System (iOS), Tablet Operating System (iPadOS), Native App Distribution (App Store), and Mobile Browser and Browser Engine (Safari and WebKit). - Google: Mobile Operating System (Android), Native App Distribution (Play Store), and Mobile Browser and Browser Engine (Chrome and Blink). - Market Dominance: CMA findings confirmed that almost all UK mobile device holders use either Apple or Google's platform. Users are unlikely to switch between them, reinforcing their dominance. Furthermore, to reach both user bases, businesses must distribute their content through both platforms, effectively making them "must-have" channels. - Market Entrenchment: The CMA concluded that competitive constraints are currently limited. Despite the rapid deployment of technologies like Artificial Intelligence (AI), these developments are deemed unlikely to eliminate Apple or Google’s market power over the five-year designation period. - Economic Impact: The designation acknowledges the crucial role of these platforms, noting that the UK app economy generates an estimated 1.5% of the UK’s GDP and supports about 400,000 jobs, encompassing sectors like FinTech and mobile gaming. What Happens Next? The SMS designation itself is not a finding of wrongdoing and does not introduce immediate new requirements. However, it acts as the gateway for the CMA to introduce targeted and proportionate interventions, such as Conduct Requirements or Pro-Competition Interventions, designed to ensure open choices, fair dealing, and trust and transparency within these vital digital activities. This action mirrors regulatory efforts globally, including the EU’s Digital Markets Act (DMA) and legal actions in the US and Japan. 🎧 Sponsored by Approov We are entering a "pivotal era for mobile technology" where regulatory interventions like the CMA’s SMS designation and the EU's DMA are weakening the centralized control over app distribution held by Apple and Google. This shift "opens the floodgates for alternative app stores, sideloading, and direct-to-consumer models". As mobile security risks move beyond platform constraints, secure your applications and APIs with a truly cross-platform, developer-centric solution. Visit approov.io for more information on how to implement modern app and API protection. 🔗 Useful Links & Resources - https://assets.publishing.service.gov.uk/media/68f8c09325d7d8af156dc294/Final_decision_report.pdf (22 October 2025): [www.gov.uk/cma] - https://assets.publishing.service.gov.uk/media/68f8bf4780cf98c6e8ed8f83/Final_decision_report.pdf (22 October 2025): [www.gov.uk/cma] - https://www.gov.uk/government/news/cma-confirms-apple-and-google-have-strategic-market-status-in-mobile-platforms: [www.gov.uk/cma] 💡 Keywords CMA, Strategic Market Status (SMS), Digital Markets Competition and Consumers Act 2024 (DMCCA), Apple Mobile Platform, Google Mobile Platform, mobile platform, app distribution, mobile browser, mobile security, iOS, Android, App Store, Play Store, WebKit, Blink, API protection, sideloading, app economy, tech regulation. 

📣 New Podcast! "UK Competition and Markets Authority (CMA) designate Apple and Google with Strategic Market Status" on @Spreaker #apiprotection #appdistribution #appeconomy #apple #approov #cma #digitalmarkets #dmcc #google #mobilecompetition #sms #strategicmarketstatus

Approov Mobile Security

@approov.bsky.social

5 months ago

Cloudflare Connect 2025 is underway! We’re here at Booth #9 at the ARIA, Las Vegas. Stop by to chat about API protection done right 🔐

📅 Or book a meeting: meetings.hubspot.com/ted-miracco/...

#CloudflareConnect #LasVegas #APISecurity #Approov #ZeroTrust

Approov Mobile Security

@approov.bsky.social

5 months ago

Next Generation Attestation to Secure Mobile Apps Against Threats from AI Mobile is officially the digital default. In this episode of Upwardly Mobile, we explore the staggering statistics showing mobile devices dominating global internet usage and discuss the critical security challenges that arise from this mobile-first environment. We then delve into the cutting-edge solution offered by our sponsor, Approov, and their latest platform update, https://www.businesswire.com/news/home/20251007833296/en/Approov-Launches-Next-Generation-Attestation-to-Secure-Mobile-Apps-Against-Threats-from-AI-and-Meet-New-EU-Regulations, including AI-driven attacks and new regulatory pressures. The Mobile Tipping Point: 64% and Rising The mobile landscape is at an inflection point. As of 2025, over 64% of all website traffic comes from mobile devices. This dominance is driven by the fact that nearly 96.3% of internet users access the internet using a mobile phone. • This shift is not just a trend; it is the new normal. • Mobile traffic reached 64.1% in Q2 2025, marking eight consecutive quarters of growth. • Developing regions are leading the surge, with Africa having the highest proportion of mobile internet traffic at 69.13%, and Asia seeing 72.3% of all web traffic coming from smartphones. • The most common activities performed on smartphones include playing a game (68%), listening to music (67%), and using social media (63%). The Security Gap in a Mobile-First World The widespread adoption of mobile creates significant security vulnerabilities. Automated threats make it easier for bad actors to clone legitimate apps, steal data, and commit fraud, which can cause irreparable damage to a brand's reputation and financially devastate users. Furthermore, new security gaps are emerging due to regulations like the EU’s Digital Markets Act (DMA), which mandates support for third-party app stores, increasing the risk of fraudulent apps. Approov 3.5: Protecting the Critical Connection Approov, the leader in mobile API security, addresses these threats by acting as a digital gatekeeper. Approov protects the critical connection between a mobile app and a company's backend servers (APIs). It ensures that only genuine, untampered apps running in a secure environment can access sensitive services, blocking automated bots, modified apps, and cloned apps before they can compromise data. The latest platform update, Approov 3.5, delivers next-generation attestation: • Ready for the DMA and Open App Stores: Approov’s cloud-based verification ensures only genuine app instances—regardless of their distribution source—can access a company’s APIs. • Hardware-Backed Security (Android): Cryptographic keys are stored in a secure, isolated “vault” on the device’s hardware, making cloning an app’s identity virtually impossible. • Defense Against AI-Powered Attacks: The platform provides real-time threat analytics, allowing security teams to dynamically issue over-the-air (OTA) updates to block emerging AI threats without requiring an app update. • Immutable App Signature: This feature creates a unique fingerprint upon installation, continuously verifying the app’s integrity against tampering or repackaging with malware. • Memory Dump Detection: A new defense actively blocks attackers attempting to scrape sensitive information, such as AI secrets or user credentials, directly from the device’s memory. Approov has proven that robust security can be achieved without compromising user experience, offering fast and responsive cross-platform security checks for iOS, Android, and HarmonyOS. By verifying API requests, Approov reduces API attacks by over 95%. -------------------------------------------------------------------------------- Keywords Mobile traffic, API security, Approov 3.5, mobile app security, Digital Markets Act (DMA), hardware-backed security, 64% web traffic, AI-powered attacks, mobile-first, app cloning, fraud prevention, mobile API. Sponsor Link For more information on securing your mobile application and APIs, please visit our sponsor: https://approov.io/.

📣 New Podcast! "Next Generation Attestation to Secure Mobile Apps Against Threats from AI" on @Spreaker #apisecurity #approov #approov35 #cybersecurity #digitalmarketsact #dma #fraudprevention #mobilefirst #mobilesecurity #webtraffic

Approov Mobile Security

@approov.bsky.social

5 months ago

Big Tech's Gamble: Lawsuits Challenge Apple, Google, and Meta Over Social Casino Apps In this episode of Upwardly Mobile, we dive into the significant legal challenges facing major technology companies—Apple, Google (Alphabet), and Meta Platforms—as they are forced to defend themselves against class action lawsuits alleging that they promoted and profited from illegal social casino gambling apps. A recent ruling by U.S. District Judge Edward Davila in San Jose, California, denied the companies' requests to dismiss the lawsuits. The plaintiffs, numbering in the dozens, contend that the companies' platforms—Apple’s App Store, Google’s Play Store, and Meta’s Facebook—promoted an “authentic Vegas-style experience of slot machine gambling” through an allegedly illegal racketeering conspiracy. Key Takeaways from the Litigation: - The Liability Claim: The core claim is that the defendants "willingly assist, promote and profit from" allegedly illegal gambling. This is achieved by: - Offering users access to the apps through their stores. - Taking a substantial percentage of consumer purchases (estimated at 30% commission, totaling over $2 billion) on in-app transactions for items like Game Coins and Sweeps Coins. - Processing these allegedly illicit transactions using proprietary payment systems. - Using targeted advertising to "shepherd the most vulnerable customers" to the casino apps. - The Section 230 Defense Rejected: Apple, Google, and Meta argued that Section 230 of the federal Communications Decency Act protected them from liability because this law shields online platforms from lawsuits over third-party content. Judge Davila rejected this argument, finding that the companies did not act as "publishers" when processing payments. The judge emphasized that the "crux of plaintiffs’ theory is that defendants improperly processed payments for social casino apps". - "Neutral Tools" Argument Undercut: The court called it irrelevant that the companies provided "neutral tools" (like payment processing) to support the apps. - Damages Sought: The lawsuits seek unspecified compensatory and triple damages, among other remedies. - Appeals and Case History: Judge Davila allowed the defendants to immediately appeal his decision to the 9th U.S. Circuit Court of Appeals, acknowledging the importance of the Section 230 issues. The litigation against the Silicon Valley-based companies began in 2021. - Additional Suits: Separately, a new lawsuit was filed against Apple and Google by lead Plaintiff Bargo (not naming the social casino operators), alleging the distribution of "patently illegal gambling software" in New Jersey and New York. This complaint includes legal claims under NJ and NY gambling loss recovery statutes, consumer protection laws, and RICO laws. Sponsor Message: This episode of Upwardly Mobile is brought to you by our sponsor. Learn how to secure your mobile app business today. Visit https://approov.io/. Relevant Source Materials & Case Information: - Article Reference (Legal Analysis): Excerpts from "Apple and Google Hit with New Social Casino Gambling Lawsuit," National Law Review (October 02, 2025). (Article written by James G. Gatto of Sheppard, Mullin, Richter & Hampton LLP). - Article Reference (News): "Apple, Google, Meta must face lawsuits over gambling apps," Honolulu Star-Advertiser (Oct. 1, 2025). - Article Reference (Judicial Denial): "Judicial Denial for Tech Giants in Casino App Lawsuits" (Sept 30). - Amicus Brief Reference: In re: Casino-Style Games Litigation (Nos. 22-16914, 22-16916, 22-16888, 22-16889, 22-16921, 22-16923) U.S. Court of Appeals for the Ninth Circuit. - District Court Case Reference (Northern District of California): In re Apple Inc App Store Simulated Casino-Style Games Litigation, No. 21-md-02985; In re Google Play Store Simulated Casino-Style Games Litigation, No. 21-md-03001; and In re Facebook Simulated Casino-Style Games Litigation, No. 21-02777. - Sponsor Link: https://approov.io/ Keywords for SEO Optimization: Social Casino Lawsuit, Apple, Google, Meta, Section 230, Gambling Apps, App Store, Play Store, Communications Decency Act, Platform Liability, Edward Davila, Consumer Protection, Racketeering, Illegal Gambling, Tech Litigation, In-App Purchases, RICO.

📣 New Podcast! "Big Tech's Gamble: Lawsuits Challenge Apple, Google, and Meta Over Social Casino Apps" on @Spreaker #approov #appstore #bigtechliability #gamblinglaw #googleplay #section230 #socialcasino #upwardlymobile

Approov Mobile Security

@approov.bsky.social

5 months ago

How Misconfigured Firebase Servers Exposed User Credentials and Private Data? In this critical episode of Upwardly Mobile, we delve into the alarming cybersecurity incident involving massive data exposure stemming from misconfigured Firebase servers. Cybersecurity researchers uncovered a breach that exposed the sensitive information and plaintext passwords of over 1.8 million users. This wasn't the result of sophisticated hacking, but rather "basic negligence" and developers failing to implement standard security settings. We discuss why Firebase, Google's popular backend-as-a-service (BaaS) for mobile apps , has become a liability risk when developers neglect configuration best practices. What was exposed and the devastating scope of the leak: The scope of this data leak is massive, involving publicly accessible Firebase real-time databases used by more than 900 mobile applications, predominantly Android-based . These affected apps spanned categories including health, fitness, education, and finance. The highly sensitive user data exposed included: • Plaintext passwords (unencrypted) • Usernames, email addresses, and phone numbers • Billing information • High-privilege API tokens, AWS root access tokens, and private chat logs • Millions of user ID photos . The Failure of Security as an Afterthought: Experts warn that storing plaintext passwords on open cloud databases in 2025 is "reckless" . The breach occurred because developers failed to secure their Firebase instances, often by extending insecure "test-mode" configurations or inadvertently leaving production environments vulnerable. Responsibility for this preventable disaster lies with both the developers and Firebase itself, for allowing insecure default settings.We also explore the technical mechanism behind these breaches: Automated scanning tools (like OpenFirebase) are actively exploiting this vulnerability by parsing Android Package Kit (APK) files to extract Firebase project IDs, API keys, and subsequently probing service URLs for unauthenticated access. This incident serves as a strong wake-up call for the tech industry, emphasizing the critical need for mandatory security training and treating security as a core function of software development—not an afterthought. -------------------------------------------------------------------------------- 🛡️ Sponsor: Approov Protect your mobile APIs and prevent automated attacks that exploit hardcoded secrets and misconfigurations. Secure your apps from the client-side up. Learn more and protect your platform at https://approov.io/podcast -------------------------------------------------------------------------------- Source Materials & Links • Article 1: "Massive data leak exposes passwords of 1.8 million users through misconfigured Firebase servers," ZENDATA (May 25, 2025). • Article 2: "Numerous Applications Using Google's Firebase Platform Leaking Highly Sensitive Data," Cyber Security News (September 25, 2025). -------------------------------------------------------------------------------- Keywords: Data Leak, Firebase Security, Plaintext Passwords, Cybersecurity, Mobile App Security, Google Firebase, Cloud Misconfiguration, Data Breach, Developer Negligence, API Security, Android Security, BaaS, App Development.

📣 New Podcast! "How Misconfigured Firebase Servers Exposed User Credentials and Private Data?" on @Spreaker #apiprotection #approov #cloudsecurity #databreach #firebasefail #mobilesecurity #plaintextpasswords #upwardlymobile #zendata

Approov Mobile Security

@approov.bsky.social

5 months ago

Google's Legal Gauntlet: Antitrust Battles and the Future of the App Ecosystem Google's Legal Gauntlet: Antitrust Battles and the Future of the App Ecosystem  This week on Upwardly Mobile, we dissect the flurry of major legal decisions facing Google in September 2025, from its desperate plea to the Supreme Court to halt the Epic Games injunction to the final ruling in the federal search monopoly case. We explore the massive shifts coming to the Android app ecosystem and Google's mandated business practice changes. Episode Notes September 2025: A Critical Month for Google's Antitrust Defense Google is challenging two massive antitrust rulings simultaneously, initiating what the sources describe as its "last hope" to maintain control over core business functions. Part 1: The Epic Games Showdown at the Supreme Court Google has asked the U.S. Supreme Court to intervene and pause the injunction it received following a major legal loss to Epic Games in October 2024. The company is seeking a decision on the stay by October 17, just days before the injunction is scheduled to take effect around October 20 or 22. The injunction, upheld by the Ninth Circuit Court of Appeals, requires Google to make several fundamental changes to the Google Play Store and the Android app ecosystem: - Open the Play Store: Google must allow users to download and use third-party app stores for a period of three years. - External Billing: Google is no longer allowed to force developers to use its billing system; developers must be allowed to include external links in apps, enabling users to bypass Google’s billing system. - End Pre-Install Deals: Google can no longer make deals around pre-installing the Play Store on phones. Google argues that this "unprecedented antitrust injunction" will "[create] enormous security and safety risks" by allowing the proliferation of stores that stock "malicious, deceptive or pirated content". Furthermore, Google claims the injunction burdens developers with constantly monitoring numerous stores and makes it substantially easier for developers to avoid compensating Google for services. Epic Games strongly disagrees, stating that Google continues to rely on "flawed security claims" rejected by the jury and the Ninth Circuit. Epic maintains that the injunction should go into effect so consumers and developers can benefit from competition, choices, and lower prices. Part 2: The Search Monopoly Ruling In a separate, long-running federal monopoly case, U.S. District Judge Amit Mehta ruled on remedies following his earlier decision that Google had acted illegally to maintain a monopoly in internet search. Key aspects of Judge Mehta's September 2025 ruling include: - No Divestiture of Chrome/Android: The judge denied the Department of Justice's proposal to force Google to sell its Chrome browser or divest the Android operating system, ruling that the government had "overreached". - End Exclusive Deals: Google is no longer permitted to strike exclusive deals around the distribution of search, Google Assistant, Gemini, or Chrome. For example, Google cannot require device makers to pre-load its apps in order to gain access to the Play Store. - Data Sharing: Google must share some of its search data with competitors going forward to narrow the "scale gap" created by exclusive distribution agreements. (Google is not required to share data related to its ads). Google called the decision "largely a win" but expressed concerns about the requirements to share Search data and the new limits imposed on how Google distributes its services. 🛡️ https://approov.io As discussions around third-party app stores and sideloading intensify due to the Epic v. Google injunction, the need for robust mobile app security is paramount. Approov provides essential security solutions for developers navigating these new challenges. Approov offers mobile app attestation solutions that allow developers to safely distribute mobile apps through third-party app stores by significantly mitigating the primary risks associated with sideloading, such as malware, app tampering, and fraudulent API use. Approov verifies both the integrity of the app and the device environment, ensuring that only genuine, unmodified app instances—regardless of installation source—can communicate with backend APIs. Approov's system works across Android, iOS, and HarmonyOS. Learn how Approov secures your APIs and mobile apps against evolving threats related to sideloading and third-party distribution: [approov.io] Relevant Links (Source Material) - Epic Games Lawsuit: Coverage regarding Google’s request for a Supreme Court stay and the opening of the Play Store (as reported by Engadget, Thurrott.com, The Verge, and Reuters). - DOJ Monopoly Case: Reporting on Judge Amit Mehta’s final ruling, which denied the divestiture of Chrome but mandated changes to Google’s search distribution and data sharing practices (as reported by Engadget). - Security Solutions: Information on mobile app attestation and security best practices for apps distributed through third-party channels. Keywords: Google Supreme Court, Epic Games, Antitrust, Google Play Store, Android Ecosystem, Third-Party App Stores, App Store Security, Chrome Monopoly, Judge Amit Mehta, DOJ Lawsuit, App Distribution, Mobile App Attestation, Approov, Digital Marketplace, Competition Law. 

📣 New Podcast! "Google's Legal Gauntlet: Antitrust Battles and the Future of the App Ecosystem" on @Spreaker #androidecosystem #antitrustlaw #approov #epicvgoogle #googleantitrust #googleplay #mobileapps #supremecourt

Approov Mobile Security

@approov.bsky.social

5 months ago

How Secure Are eSIMs? Exploring Myths and the Reality of Digital SIM Cards Episode Notes Description: In this episode of Upwardly Mobile, we dive into one of the most pressing cybersecurity threats facing mobile carriers and their subscribers: eSIM swap fraud. While digital SIMs offer superior security against physical theft, they remain vulnerable to sophisticated credential-based attacks and social engineering that target the carrier's systems. We explain how this critical fraud operates and reveal the advanced, cloud-based technologies—App Attestation and Device Binding—that mobile operators are now deploying to verify user identity and device integrity in real time, effectively blocking fraudsters before a swap can be completed. The eSIM Swap Threat eSIM swapping is a form of identity fraud where an attacker convinces a mobile carrier to transfer a victim's phone number to a new eSIM under the attacker's control, often by impersonating the legitimate user remotely. • Attack Method: Attackers often gather personal details from public sources or breaches, then contact the carrier, claiming they need to transfer their number to a new device. Since no physical access is needed, the fraud relies entirely on weaknesses in the carrier’s authentication process. • The Impact: Once a swap is successful, the criminal gains full control over the victim's phone number. They can intercept calls, texts, and, critically, one-time security codes (OTPs) sent via SMS, allowing them to bypass two-factor authentication (2FA) for online banking, cryptocurrency exchanges, and other sensitive accounts, leading to massive financial loss. https://approov.io/blog/why-hackers-love-phones-keep-your-eye-on-the-device To counter these remote, identity-based attacks, carriers are adopting a multi-layered verification approach focused on establishing the trustworthiness of the application and the hardware initiating the swap request. 1. App Attestation This technology focuses on verifying the integrity and legitimacy of the carrier's mobile application. • Verification: App Attestation confirms that the carrier's app being used is the genuine, untampered version downloaded directly from an official app store. • Prevention: It detects if the app has been modified with malicious code or is running in a compromised environment, such as an emulator. If an attacker attempts to use a fake or compromised version of the carrier’s app to initiate a fraudulent eSIM swap request, https://approov.io/mobile-app-security/rasp/app-attestation/ detects and blocks that request. 2. Device Binding Device Binding provides a cryptographic link between a user's account and the unique hardware characteristics of their trusted device. • Secure Link: When a user first logs in, a secure link is created between the app and the device's hardware IDs. • Suspicion Flagging: If a request for an eSIM swap is later initiated from a different, unverified device, the system flags the activity as suspicious, regardless of whether the attacker has stolen credentials. The system can then require additional verification steps or outright deny the unauthorized transfer. This combined approach shifts the security decision-making from the potentially compromised user device to a secure cloud service, making it extremely difficult for attackers to bypass checks through client-side tampering or reverse-engineering. Comprehensive Security Layers for Mobile Carriers Beyond app and device verification, mobile carriers are advised to strengthen defenses through systemic controls: • Stricter Authentication: Implementing secure authentication processes for eSIM transfers, including demanding extra layers like verbal confirmation or a photo ID. • Device Fingerprinting: Binding eSIM profiles to unique device hardware IDs to prevent unauthorized cloning or reuse across multiple devices. • Advanced Analytics: Leveraging AI-Driven Fraud Detection and machine learning to monitor network activity for anomalies, such as unusual call volumes or multiple simultaneous activations, which might signal digital SIM Box fraud schemes. • User Protection Features: Offering tools like Verizon's "SIM Protection," which allows customers to lock lines on their account, prohibiting any transaction requiring a new SIM/eSIM transfer until manually unlocked (with a possible 15-minute delay when unlocking). Protect Yourself: User Best Practices Users must also adopt strong security habits to minimize risk: • Prioritize App-Based 2FA: Always use authenticators like Google Authenticator or Authy over SMS-based two-factor authentication (2FA) for critical accounts, as SMS codes can be intercepted post-swap. • Secure Your Carrier Account: Set a strong password and add an account PIN or passcode with your carrier to prevent unauthorized changes. • Stay Vigilant: Immediately contact your carrier if you notice unexpected loss of cellular service, unusual account alerts, or unauthorized charges, which are common signs of a successful eSIM hack. -------------------------------------------------------------------------------- Sponsor This episode is brought to you by Approov, pioneers in Mobile App and Device Security. Learn how Approov’s App Attestation and Device Binding solutions safeguard your mobile transactions and prevent sophisticated fraud. Visit: https://notebooklm.google.com/approov.io

📣 New Podcast! "How Secure Are eSIMs? Exploring Myths and the Reality of Digital SIM Cards" on @Spreaker #appattestation #approov #devicebinding #deviceverification #esim #fraud #mobilecarrier #sim #simbox #simboxfraud #swap #swapping

Approov Mobile Security

@approov.bsky.social

6 months ago

Apple's Leap in iOS Security: Unpacking Memory Integrity Enforcement (MIE) In this episode, we're diving deep into Apple's groundbreaking Memory Integrity Enforcement (MIE), an unprecedented effort poised to redefine the landscape of mobile security, and we'll also explore the broader spectrum of threats targeting the iOS ecosystem. Apple's Memory Integrity Enforcement (MIE) is the culmination of a half-decade of intensive design and engineering, combining the unique strengths of Apple silicon hardware with advanced operating system security. Apple believes MIE represents the most significant upgrade to memory safety in the history of consumer operating systems. This comprehensive, always-on protection is designed to provide industry-first memory safety across Apple devices, all without compromising device performance. The Driving Force: Combating Mercenary Spyware While the iPhone has never experienced a successful, widespread malware attack, Apple's focus for MIE is primarily on the mercenary spyware and surveillance industry. These highly sophisticated threats, often associated with state actors, utilize exploit chains that can cost millions of dollars to target a small number of specific individuals. A common denominator in these advanced attacks, whether targeting iOS, Windows, or Android, is their reliance on memory safety vulnerabilities. MIE aims to disrupt these highly effective exploitation techniques that have been prevalent for the last 25 years. How MIE Works: A Three-Pronged Defense MIE is built on a robust foundation of hardware and software innovations: 1. Secure Memory Allocators: Apple's efforts in memory safety include developing with safe languages like Swift and deploying mitigations at scale. Key to MIE are its secure memory allocators, such as kalloc_type (introduced in iOS 15 for the kernel) and xzone malloc (for user-level in iOS 17), alongside WebKit's libpas. These allocators use type information to organize memory, thwarting attackers' goals of creating overlapping interpretations of memory to exploit use-after-free and out-of-bounds bugs. 2. Enhanced Memory Tagging Extension (EMTE): Building on Arm's 2019 Memory Tagging Extension (MTE) specification, Apple conducted deep evaluations and collaborated with Arm to address weaknesses, leading to the Enhanced Memory Tagging Extension (EMTE) specification in 2022. MIE rigorously implements EMTE in strictly synchronous, always-on mode, a crucial factor for real-time defensive measures in adversarial contexts. EMTE prevents common memory corruption types:     ◦ Buffer Overflows: The allocator tags neighboring allocations with different secrets. If memory access spills over into an adjacent allocation with a different tag, the hardware blocks it, and the operating system can terminate the process.     ◦ Use-After-Free Vulnerabilities: Memory is retagged when reused. If a request uses an older, invalid tag for retagged memory, the hardware blocks it. EMTE also specifies that accessing non-tagged memory from a tagged region requires knowing that region’s tag, making it harder for attackers to bypass EMTE. 3. Tag Confidentiality Enforcement: This critical component protects the implementation of Apple's secure allocators and the confidentiality of EMTE tags, even against side-channel and speculative-execution attacks. Apple's silicon implementation prevents tag values from influencing speculative execution, a vulnerability seen in other MTE implementations. Furthermore, MIE addresses Spectre variant 1 (V1), a speculative-execution vulnerability, with a mitigation designed for virtually zero CPU cost, making it impractical for attackers to leak tag values and guide attacks. Impact and Availability Memory Integrity Enforcement is built right into Apple hardware and software in all iPhone 17 and iPhone Air models, offering unparalleled, always-on memory safety protection for key attack surfaces, including the kernel and over 70 userland processes. Importantly, MIE was designed to deliver groundbreaking security with minimal performance impact, remaining completely invisible to users. Apple is also making EMTE available to all developers in Xcode as part of the new Enhanced Security feature. Extensive evaluations by Apple's offensive research team have confirmed that MIE dramatically reduces the exploitation strategies available to attackers, making it extremely difficult to rebuild exploit chains. Beyond MIE: Other Threats to iOS Devices While MIE targets memory corruption, the iOS ecosystem faces a range of other threats: • Application-Level Threats: These include various forms of malware, such as TouchID malware, Yispecter, and AceDeceiver, which exploit design flaws or trick users. More widespread are leaky applications (greyware), representing 61% of iOS apps, which legally collect and silently forward unnecessary personal data like location, contacts, and photos to third parties. • Network-Level Threats: iOS devices are as exposed to network-related threats as any other operating system. These include Man-In-The-Middle (MITM) attacks, where communications are intercepted or altered via unprotected WiFi hotspots or spoofing. Phishing and Smishing are the most detected network threats on mobile devices, trapping users through malicious links in emails or SMS. Rogue cell towers can also trick devices into connecting, allowing interception of calls, SMS, and data. • Device-Level Threats: OS vulnerability exploits occur when cybercriminals leverage public security holes in outdated iOS versions (e.g., Pegasus spyware). Jailbroken devices bypass iOS security checks, making them more vulnerable to malicious applications. Finally, unmanaged or malicious profiles can be configured to send all transiting data to external servers, crushing data privacy. Organizations like Pradeo offer solutions such as Mobile Threat Defense (MTD) and Mobile Application Security Testing to provide full protection for mobile fleets and applications, safeguarding data and ensuring compliance with data privacy regulations. -------------------------------------------------------------------------------- Relevant Links to Source Materials: • For deeper insights into Apple's Memory Integrity Enforcement, refer to the "Memory Integrity Enforcement: A complete vision for memory safety in Apple devices" research by Apple Security Engineering and Architecture (SEAR). • To understand broader iOS threats, consult the "iOS SECURITY REPORT: THREATS TARGETING APPLE MOBILE DEVICES" white paper by Pradeo. Sponsored by: Enhance your mobile API security with Approov. Visit them at https://www.google.com/url?sa=E&q=https%3A%2F%2Fapproov.io. -------------------------------------------------------------------------------- Keywords: Apple security, Memory Integrity Enforcement (MIE), iOS security, memory safety, mercenary spyware, EMTE, secure allocators, buffer overflows, use-after-free, speculative execution, cyber threats, mobile security, iPhone security, hardware security, software security, enterprise mobility, mobile malware, leaky applications, Man-In-The-Middle, phishing, jailbreaking, OS vulnerabilities, Pradeo Security, API security, mobile API protection, device integrity.

📣 New Podcast! "Apple's Leap in iOS Security: Unpacking Memory Integrity Enforcement (MIE)" on @Spreaker #apisecurity #applesecurity #approov #cybersecurity #devicesecurity #emte #ios #iphone #memorysafety #mie #mobilesecurity #pradeo

Approov Mobile Security

@approov.bsky.social

6 months ago

What the App Store Freedom Act Means for Developers and Consumers? The App Store Freedom Act Episode Description: In this episode of Upwardly Mobile, we unpack the App Store Freedom Act, a landmark bipartisan bill aiming to reform the highly concentrated mobile app marketplace dominated by tech giants like Apple and Google. Introduced by Representative Kat Cammack (R-FL) and co-sponsored by Representative Lori Trahan (D-MA), this legislation addresses significant concerns about anti-competitive practices, consumer choice, and developer freedom. The https://appfairness.org/, an independent nonprofit advocating for consumer choice and a level playing field for app developers, applauds the bill's bipartisan support, seeing it as a crucial step to dismantle "mobile walled gardens". We explore the bill's key provisions, which include allowing users to choose third-party app stores, install apps outside of official stores, and delete pre-installed applications. The Act also seeks to remove limitations on communication between developers and users, cap commissions on payments outside default systems, and mandate data sharing for app developers. However, the App Store Freedom Act isn't without its critics. We delve into the concerns raised by the American Action Forum, particularly regarding potential overlaps with existing antitrust law and recent rulings like Apple v. Epic Games. A major point of contention is the security implications: opening up app stores could lead to a significant influx of fraudulent apps, data theft, and unverified third-party providers, potentially compromising the "walled garden" security benefits that currently protect users. We also discuss how while the bill might expedite FTC enforcement, it could bypass crucial antitrust requirements, potentially overlooking pro-consumer behaviors by app store providers. Join us as we explore the multifaceted debate surrounding this pivotal piece of tech legislation. Key Discussion Points: • The Problem: Anti-competitive practices and lack of consumer freedom in mobile app stores controlled by Apple and Google. • The Bill's Purpose: To foster competition, enhance consumer choice, and create a level playing field for app developers globally. • Core Provisions of the App Store Freedom Act (H.R.3209):     ◦ Interoperability: Users can choose default third-party app stores, install apps from outside sources, and hide/delete pre-installed apps.     ◦ Open App Development: Requires covered companies to provide developers with access to interfaces, hardware, and software features on equivalent terms.     ◦ Prohibitions: Bans requirements for specific in-app payment systems, prevents punitive actions against developers using alternative pricing or payment methods, and protects legitimate business communications between developers and users.     ◦ Nonpublic Business Information: Prohibits covered companies from using developer data to compete against those apps. • Enforcement: Violations are treated as unfair or deceptive acts by the Federal Trade Commission (FTC), with potential civil penalties up to $1,000,000 per violation. State attorneys general can also bring civil actions. • Overlap with Existing Law & Apple v. Epic Games: Discussion on whether new legislation is fully necessary given previous court rulings that addressed similar anti-steering practices. • Security Concerns: Analysis of how opening the "walled garden" could impact user safety, potentially leading to fraudulent apps, stolen data, and unverified third-party providers. • Balancing Act: The trade-offs between promoting competition and maintaining user security and convenience. Relevant Source Materials for this Summary: • "CAF Applauds Bipartisan Support for App Store Freedom Act - Coalition for App Fairness" • "Evaluating the App Store Freedom Act - AAF" • "Text - H.R.3209 - 119th Congress (2025-2026): App Store Freedom Act | Congress.gov | Library of Congress" Sponsor: This episode of Upwardly Mobile is brought to you by Approov.io. Secure your APIs and mobile apps against fraud and abuse. Visit approov.io to learn more. Keywords: App Store Freedom Act, digital markets, app store regulation, Apple, Google, anti-competitive practices, consumer choice, app developers, mobile apps, Open App Markets Act, Apple v. Epic Games, FTC, security concerns, H.R.3209, mobile walled gardens, competition policy, tech legislation, digital monopoly, software development, consumer protection, privacy.   --------------------------------------------------------------------------------

📣 New Podcast! "What the App Store Freedom Act Means for Developers and Consumers?" on @Spreaker #apple #appregulation #approov #appstorefreedomact #competitionlaw #digitalmarkets #digitalrights #epicgames #ftc #google #mobileapps #openappmarketsact #spotify #walledgardens

Approov Mobile Security

@approov.bsky.social

6 months ago

Apple's iOS Obfuscation Dilemma: App Store Rejection & Developer Security Challenges Apple's iOS Obfuscation Dilemma: App Store Rejection & Developer Security Challenges In this vital episode of "Upwardly Mobile," we dive deep into the complexities of mobile app security within the healthcare sector, particularly concerning the HIPAA Security Rule and the challenges of iOS code obfuscation and App Store review. As telemedicine and mobile access to ePHI (Electronic Protected Health Information) become ubiquitous, understanding and implementing robust security measures is no longer optional—it's imperative. What You'll Learn in This Episode: - The Evolving Threat Landscape for Healthcare Apps: Discover how the rapid adoption of mobile healthcare apps by both patients and practitioners has created new, data-rich attack surfaces for hackers. This includes apps used for consultations, prescription refills, appointment scheduling, accessing test results, and even those associated with medical devices. - Limitations of Traditional Security: We explore why traditional security approaches and even robust TLS (Transport Layer Security) are often insufficient for protecting mobile healthcare apps and their APIs, particularly due to the unique exposure of mobile app code and device environments. Xcode's native build settings like symbol stripping and dead code stripping are primarily for optimization and offer no meaningful protection against determined reverse-engineering efforts. - Proposed Improvements to the HIPAA Security Rule: Learn about Approov's specific recommendations to strengthen the updated HIPAA Security Rule (initially proposed in June 2024), focusing on mobile apps accessing ePHI. Key proposed changes include mandating: - App Attestation: A proven technique to ensure only genuine, unmodified apps can access APIs. - Runtime Device Attestation: Continuous scanning and real-time reporting of device environments to block requests from compromised devices. - Dynamic Certificate Pinning: Essential for protecting communication channels from Man-in-the-Middle (MitM) attacks, even when traffic is encrypted. - API Secret Protection: Explicit guidelines to ensure API keys are never stored in mobile app code and are delivered only as needed to verified apps. - Runtime Zero Trust Protection of Identity Exploits: Additional controls like app and device attestation to provide an extra layer of zero-trust security against credential stuffing and identity abuse. - Breach Readiness and Service Continuity: Extending incident response plans to cover third-party breaches and explicitly managing API keys and certificates during a breach. - The Role of https://mas.owasp.org/MASVS/: Understand how the OWASP Mobile Application Security Verification Standard (MASVS) serves as the industry standard for mobile app security, offering guidelines for developers and testers. We specifically highlight MASVS-RESILIENCE for hardening apps against reverse engineering and tampering. - The iOS Obfuscation Dilemma: Unpack the conflict faced by developers in regulated industries like fintech and healthcare: the critical need to protect proprietary algorithms and sensitive logic through code obfuscation versus the risk of rejection by Apple's App Store. Apple's guidelines are ambiguously enforced, often flagging aggressive obfuscation as an attempt to "trick the review process". - Third-Party Obfuscation Solutions: Since Xcode provides no built-in true obfuscation features, we discuss the imperative for advanced third-party solutions. Learn about techniques like symbol renaming, string encryption, control flow obfuscation, and dummy code insertion. We also touch upon leading commercial tools like Guardsquare's iXGuard, Zimperium's Mobile Application Protection Suite (MAPS), and Appdome, as well as LLVM-based obfuscators. - Obfuscation as a Compliance Control: Discover why code obfuscation and Runtime Application Self-Protection (RASP) are fundamental technical safeguards for HIPAA compliance and meeting the requirements of PCI DSS, even if not explicitly named in the regulations. - Strategic Recommendations for Implementation: Get insights on implementing a risk-based tiered approach to app protection, integrating obfuscation into your CI/CD pipeline, and transparently communicating your security posture to the App Store review team to mitigate rejection risks. Tune in to gain a comprehensive understanding of securing your mobile health applications in today's complex digital environment! Relevant Links & Resources: - Sponsor: Learn more about app and API security solutions from Approov: https://approov.io/ - Approov Blog: Injecting Mobile App Security into The HIPAA Healthcare Security Rule: https://approov.io/blog/injecting-mobile-app-security-into-the-hipaa-healthcare-security-rule - OWASP Mobile Application Security (MAS) Project: https://owasp.org/www-project-mobile-app-security/ - OWASP Mobile Application Security Verification Standard (MASVS): https://mas.owasp.org/MASVS/03-Using_the_MASVS/ Keywords: Mobile App Security, Healthcare, HIPAA, ePHI, API Security, Code Obfuscation, iOS Security, App Store Review, App Attestation, Runtime Application Self-Protection (RASP), PCI DSS, OWASP MASVS, Man-in-the-Middle (MitM) Attacks, API Keys, Zero Trust, Telemedicine, Virtual Healthcare, Mobile Health, Cybersecurity, Enterprise Security, Data Protection, Compliance, InfoSec, Privacy, Digital Health. 

📣 New Podcast! "Apple's iOS Obfuscation Dilemma: App Store Rejection & Developer Security Challenges" on @Spreaker #appdome #approov #appsecurity #codeobfuscation #dataprotection #guardsquare #healthcareit #iosdevelopment #mobilesecurity #owaspmasvs #rasp #securesoftware #zerotrust #zimperium