Skip to content

InvestNot yet confirmed elsewhere1 publisher2 min readPublished

Georgia Tech found malware could move money unassisted in 35 of 159 banking apps it tested

The Georgia Tech corpus says the handset belongs to the attacker while Regulation E says the loss belongs to the bank, which makes every extra authentication factor pushed to that same phone a purchase with no yield.

The Investor · Invest desk

How we use AISend a correction

Illustration accompanying Georgia Tech found malware could move money unassisted in 35 of 159 banking apps it tested
Generated illustration

What happened

  • Georgia Tech researchers ran 9,850 malware samples pulled from VirusTotal on Android phones and found banking the largest of seven target categories, with 159 apps hit by 3,579 samples.
  • In 35 of those 159 apps, all of them banks' own software rather than counterfeits, the malware could initiate a money transfer with no action at all from the customer.
  • Of the 9,850 samples, 9,102 blocked the user from revoking the malware's permissions and 9,024 blocked uninstallation, putting removal beyond ordinary customer means.
  • In 98 of the 159 banking apps, the malware hid or deleted the notifications a bank sends when it spots something wrong on the phone or in the account.
  • Zimperium research released this week counts more banking apps under active targeting in the United States than in any other country.

Why it matters

  • constraint If a compromised handset exposes every factor delivered to it, the cheapest upgrade on most fraud roadmaps, one more code or approval sent to that phone, stops adding measurable protection.
  • cost Regulation E routes most of what the malware takes onto the bank's own books, so the paying party is the one with no control over the handset or the accessibility setting the attack rides.
  • decision The bank's cheapest support script, telling the customer to delete the app, is no longer available, which pushes remediation into channels the bank neither owns nor prices.
  • exposure ThreatFabric's rising count of small and midsize U.S. banks and credit unions on target lists means the same Regulation E liability now reaches institutions that were previously below the attackers' economic threshold.

The split inside that 159 is where the underwriting sits. The samples were built to harvest credentials from 147 of the apps [9], and stolen credentials still have to be spent somewhere, which leaves the bank's server-side scoring one more look at the transaction; for 112 apps that second look is the entire defense [22]. In the other 35 the transfer starts on the customer's own handset inside the customer's own session, 22% of the tested set [21], and there is no login anomaly to catch because nothing anomalous happened at login.

Android's accessibility service, built so software can read the screen and tap on a user's behalf for people with disabilities, is what makes most of this work [11], and the same access covers the channels banks use to check their work: SMS passcodes, email, push notifications and in-app approvals are all readable and editable once the device is taken over [3]. Eward Driehuis of ThreatFabric puts it as an engineering constraint rather than a warning, saying multifactor authentication becomes "less efficient or even fully compromised if additional factors are available from the same device" [2]. Read that as a budget line. A dollar spent adding a fourth on-device factor is a dollar not spent on an off-device factor or on server-side behavioural scoring, and on this evidence only the second pair is still standing.

The most useful number here is one nobody has. Singapore, Malaysia, India and Hong Kong already require protections inside the banking app [17], and Driehuis says ThreatFabric's intelligence "does not show a significant decrease in mobile malware activity" in those regions [4]. This is probably too harsh a reading of one vendor's telemetry, and ThreatFabric sells fraud-detection software [19], so its account of its own data is not disinterested. But four mandates with no measurable decline is the nearest thing to a controlled test anyone has run on app hardening, and it suggests hardening is a compliance cost that does not price as a control.

The evidence has dated edges. The sample window closed in December 2022 [5], so anything Android has tightened since is invisible in these percentages. Zimperium's count of the U.S. leading the world in banking apps under active targeting arrives without an absolute number attached [1]. And the 54% of customers who now bank primarily by app, per Morning Consult [15], is a mobile-first population that includes iPhones, while the corpus is Android.

Which leaves 35 of 159. Nothing in the source material argues with it.

What to watch

  • A refreshed run of the Georgia Tech corpus against current Android builds, which would show whether accessibility abuse still yields unassisted transfers.
  • Whether U.S. regulators copy the in-app protection mandates already live in Singapore, Malaysia, India and Hong Kong.
  • The first Regulation E dispute in which a bank argues an unanswered fraud alert as evidence of customer consent.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence72
Adoption68
Hype gap+12
Incentives66
Confidence60
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Research released this week by mobile security vendor Zimperium counts more banking apps under active targeting in the U.S. than in any other country.

  2. [2]

    Eward Driehuis, vice president of fraud engineering at ThreatFabric, said most such malware is "actually taking over the device" and that malware makes multifactor authentication "less efficient or even fully compromised if additional factors are available from the same device."

    ReportedSupportedSource: Eward Driehuis, ThreatFabric, to American Banker2 sources— create a free account to open themView cited source
  3. [3]

    Malware on a compromised phone can see and manipulate text messages carrying one-time passcodes, emails, push notifications and in-app transaction approvals.

Sources

1 independent publisher whose own reporting we read for this story.

  1. americanbanker.com

    1 article · August 27, 2026

    U.S. bank apps are now top target for malware: Study

Share your take

Let Clarity write the post for you.

Signed-in readers get a short post drafted on this story in the register they choose — narrative, analytical, or a direct position — editable to the last word before it goes anywhere. The share buttons at the top of this story work without an account.

Topics and entities

Follow any of these and your For You feed starts watching them — no settings page required.

Topics

  • Commercial threat intelligenceFollow
  • In-app security mandatesFollow
  • Limits of device-bound MFAFollow
  • Android platform securityFollow
  • Mobile Banking MalwareFollow
  • Regulation E fraud liabilityFollow
Loading related stories