All Episodes

August 28, 2025 11 mins

Episode Title: Anatsa Unleashed: How a Sophisticated Android Banking Trojan Targets Over 830 Financial Apps Globally

In this episode of "Upwardly Mobile," we dive deep into the alarming evolution of Anatsa, a potent Android banking trojan that has significantly expanded its reach, now setting its sights on over 830 financial applications worldwide
. First identified in 2020, Anatsa (also known as Teabot or Troddler) grants its operators full control over infected devices, enabling them to perform fraudulent transactions and steal critical bank information, cryptocurrencies, and various other data on behalf of victims.
What You'll Learn in This Episode:
Anatsa's Expanded Targets: Discover how the Anatsa banking trojan has broadened its scope to include more than 150 new banking and cryptocurrency applications, extending its malicious campaigns to mobile users in new countries like Germany and South Korea
.
Deceptive Distribution Methods: Understand the cunning ways Anatsa spreads, primarily through decoy applications found on the official Google Play Store
. These seemingly harmless apps often masquerade as useful tools like PDF viewers, QR code scanners, or phone cleaners, accumulating over 50,000 downloads in some cases. Once installed, they silently fetch a malicious payload disguised as an update from Anatsa's command-and-control (C&C) server.
Advanced Evasion Techniques: Learn about Anatsa's sophisticated anti-analysis and anti-detection mechanisms, designed to evade security measures. These include decrypting strings at runtime using dynamically generated Data Encryption Standard (DES) keys, performing emulation and device model checks, and periodically altering package names and installation hashes
. The malware even hides its DEX payload within corrupted archives that bypass standard static analysis tools.
How Anatsa Compromises Devices: Find out how Anatsa requests and automatically enables critical accessibility permissions upon installation. This allows it to display overlays on top of legitimate applications, tamper with notifications, receive and read SMS messages, and ultimately present fake banking login pages to steal credentials
. The trojan also incorporates keylogging capabilities.
Industry Response: Hear about the efforts of cybersecurity firms like Zscaler, which identified and reported 77 nefarious applications distributing Anatsa and other malware families, collectively accounting for over 19 million downloads
. While Google has since removed these reported applications and states that Google Play Protect offers automatic protection, the continuous evolution of Anatsa highlights the ongoing threat.
Protect Yourself: Cybersecurity experts advise Android users to always verify the permissions that applications request and ensure they align with the intended functionality of the app
.
--------------------------------------------------------------------------------
Relevant Links to Source Materials:
• Source 1: SecurityWeek Article on Anatsa: "Anatsa Android Banking Trojan Now Targeting 830 Financial Apps"
• Source 2: Zscaler ThreatLabz Report: "Anatsa’s Latest Updates | ThreatLabz"
• Source 3: BSI Report on Anatsa: "BSI - Anatsa / Teabot"
--------------------------------------------------------------------------------
Sponsor: This episode of "Upwardly Mobile" is brought to you by Approov Mobile Security. Learn more about securing your mobile applications at approov.io.
--------------------------------------------------------------------------------
Keywords: Anatsa, Android banking trojan, mobile security, cybersecurity, financial apps, Google Play, malware, credential theft, keylogging, fraudulent transactions, Zscaler, threat intelligence, Android malware, cryptocurrency, mobile banking, data protection, Teabot, Troddler, anti-analysis, C&C server.


This content was created in partnership and with the help of Artificial Intelligence AI
Mark as Played
Transcript

Episode Transcript

Available transcripts are automatically generated. Complete accuracy is not guaranteed.
Speaker 1 (00:00):
Welcome to upwardly Mobile API and App Security. I'm your
host for today and i'm your expert.

Speaker 2 (00:05):
Great to be here.

Speaker 1 (00:06):
We're diving into well, the pretty intense world of mobile
app security today. The goal is really to cut through
some of the noise and give you our listeners some
key insights for defending mobile apps.

Speaker 2 (00:18):
Absolutely, because the threats, I mean, they just keep getting
more sophisticated, don't they, especially those targeting mobile devices. Yeah, developers,
security pros, everyone needs to stay ahead. It's a constant challenge.
Even the big platforms, you know, they're always playing catch
up to some extent, definitely.

Speaker 1 (00:36):
And speaking of those challenges, there's one specific threat in
the Android world that's been making a lot of noise lately.
We should probably unpack that.

Speaker 2 (00:44):
Ah, you mean a NASA exactly.

Speaker 1 (00:45):
An atsa ye also known as TeaBot or troggler sometimes.
And this isn't just like annoying adwear, no, not at all.
It's serious stuff. They can gain, apparently, full control over
an infected Android device.

Speaker 2 (00:58):
Full control. Yeah, we're talking for forming fraudulent transactions for
the victim, stealing banking details, grabbing crypto other user info.
It's been around since twenty twenty, constantly evolving.

Speaker 1 (01:10):
So what's the scale we're looking at here? Is it
just a few banks or.

Speaker 2 (01:13):
Well, that's what's quite striking. Z Scalers research suggests it's
targeting over eight hundred and thirty financial apps now globally,
and it's expanding. Germany South Korea are newer targets. Just
recently they added over one hundred and fifty new banking
and crypto apps to their lists. Okay, and that's on
top of the six hundred or so financial apps they

(01:34):
were already targeting across Europe and other places.

Speaker 1 (01:36):
The massive it really is.

Speaker 2 (01:38):
The insight here, I think, is how it signals this
shift towards like industrialized cybercrime. They're mapping out entire financial ecosystems.
It's not just opportunistic anymore.

Speaker 1 (01:48):
That scale is Yeah, it's alarming. But okay, if it's
that dangerous, how does it even get onto people's phones? Yeah,
especially if it's so widespread.

Speaker 2 (01:55):
Right, that's the clever or maybe insidious part. It mainly
uses decoy.

Speaker 1 (01:59):
Apps ekoya like fake games or something.

Speaker 2 (02:01):
Sometimes, but often they're disguised as utilities things you might
actually download. Think PDF viewers, QR code scanners maybe phone cleaners.

Speaker 1 (02:11):
Ah, the kind of thing people download all the time, exactly.

Speaker 2 (02:14):
And here's the kicker. They're found on the official Google.

Speaker 1 (02:18):
Play store, seriously, on the official store.

Speaker 2 (02:21):
Yep. Some of these individual decoys got over fifty thousand
downloads each, and z Scaler reported a broader group of
malicious apps, including these the NATSA ones racked up over
nineteen million installs combined.

Speaker 1 (02:34):
Nineteen million. That's huge. So how does the actual infection happen?
Then you install the cleaner app, and then what so?

Speaker 2 (02:40):
You install the decoy. It looks harmless, maybe it even
works a bit, but silently in the background, it phones
home to its command and control server, the CNC. Okay,
and then it pulls down the real malicious payload disguised
as like an app update. Ah, the old trojan horse
trick pretty much right there in your pocket.

Speaker 1 (02:57):
So it gets in disguise, but then it needs to
stay hidden, right. You mentioned it's sophisticated. What kind of
techniques are we talking about? How does it dodge security?

Speaker 2 (03:05):
Yeah, it employs some really advanced anti analysis and evasion stuff.
This really shows that cyber arms race we're in. Okay,
Like what well for one, it uses runtime decryption. It
keeps its malicious code strings hidden encrypted until the very
last moment when it's actually running. It uses a dees
key generated on the.

Speaker 1 (03:24):
Fly, so static analysis tools the ones looking at the
app code before it runs might miss the danger.

Speaker 2 (03:31):
Precisely they don't see the decrypted strings. Then there's anti
dynamic analysis. It checks if it's running in an emulator
or on certain device models that researchers often use. Basically,
it tries to detect if it's being watched in the
sandbox environment CLA and for evasion, it does things like
periodically changing its package name and installation hash makes it
harder to track across different infected devices. But one technique

(03:53):
z scaler highlighted is particularly neat in a malicious way.
It uses malformed.

Speaker 1 (03:59):
Archives formed archives what does that mean?

Speaker 2 (04:01):
It hides its core payload, the DAX file inside a
VIP archive that's deliberately broken invalid compression weird encryption flags.

Speaker 1 (04:09):
So security tools see a broken file and just ignore it.

Speaker 2 (04:13):
Often, yes, standard tools expect properly formed ZPs, but Android
itself is often more forgiving and can still extract and
run the dx file from this corrupt archive.

Speaker 1 (04:24):
That's wow, a built in invisibility cloak.

Speaker 2 (04:28):
Sort of yeah, against many standard tools. Plus the DX
payload itself is often hidden inside something like a Jason
file dropped dynamically at runtime loaded and then immediately deleted,
makes finding it later really tough.

Speaker 1 (04:41):
And you mentioned a key lagger too.

Speaker 2 (04:43):
Uh huh. Recent versions have integrated a new key lagger
variant right into the core payload, so it's constantly adding
new tricks. It forces security to move beyond just looking
for known signatures. You need behavioral analysis.

Speaker 1 (04:55):
As some serious stealth. Okay, so let's say it gets
past all that it's on your phone. Hit and what
happens next for the user? What's the immediate impact?

Speaker 2 (05:03):
Right? So, once it's in and running, it goes for control.
Its first big move is usually requesting accessibility permissions.

Speaker 1 (05:09):
A those permissions, they always seem.

Speaker 2 (05:12):
So powerful they are, and many users, you know, might
just click allow without really thinking. If you grant ANZA
those permissions, it can then automatically enable all the other
permissions listed in its.

Speaker 1 (05:24):
Manifest file without asking again.

Speaker 2 (05:26):
Without asking again, And we're talking critical permissions here, things
like system alert window.

Speaker 1 (05:31):
What does that led it to display?

Speaker 2 (05:33):
Overlays on top of other apps. So imagine opening your
real banking app and ANASA instantly puts a perfectly crafted
fake login screen right over it.

Speaker 1 (05:43):
Oh that's bad, very bad.

Speaker 2 (05:46):
Extremely And it also grabs permissions like reads and MS,
receives useful screen intent.

Speaker 1 (05:51):
So it can read my texts like two factor authentication
codes exactly.

Speaker 2 (05:54):
It can intercept those crucial codes, mess with your notifications.
It basically gets the keys to the care kingdom to
impersonate you digitally.

Speaker 1 (06:02):
Okay, so it has control. It can see my screen,
read my text. How does it actually get the money
or credentials out?

Speaker 2 (06:08):
It uses those overlay capabilities we mention. It downloads fake
login pages from its CNC server. But here's the crucial bit.
It tailors them. It checks which financial apps you actually
have installed on your device and downloads fake pages specifically
designed to mimic those apps, so.

Speaker 1 (06:26):
It looks exactly like my bank's log in.

Speaker 2 (06:28):
It tries to. Yes, makes the scam much more convincing
than a generic fishing page. Z Scaler even found evidence
of this in action, like an incomplete fake page for
the Robinhood app that just showed a scheduled maintenance message.

Speaker 1 (06:41):
So they're actively developing and testing these.

Speaker 2 (06:43):
Fakes, constantly refining them, and all that communication back to
the CNC fetching the pages, sending the stolen data. It's
typically encrypted with a simple single byte XO or key,
not super strong encryption, but enough to obscure it casually.

Speaker 1 (06:58):
It's clear ANATZA is a major player, but finding it
in the Google Play Store does this point to a
bigger problem? Is this kind of thing common?

Speaker 2 (07:07):
Unfortunately, it does seem to reflect a broader pattern. C
Scaler's report gives us context here. They found and reported
seventy seven dodgy apps distributing a NAZA and other malware families, seventy.

Speaker 1 (07:17):
Seven apps with nineteen million in stalls collectively. You said,
that's right now.

Speaker 2 (07:22):
The good news is Google did remove the reported apps,
and Google stated that Google play Protect already had protections
against these particular versions. Play Protect is on by default
if you have Google.

Speaker 1 (07:32):
Play services, so there are defenses.

Speaker 2 (07:34):
There are absolutely active defenses are running, but clearly stuff
still slips through. It's not foolproof. These attackers are very motivated, and.

Speaker 1 (07:44):
It's not just a NASA hiding in these stores, is it?
Are there other trends we should know about definitely.

Speaker 2 (07:50):
Threat Labs, which is z Scaler's research arm, keeps an
eye on this. Their observation show it's a dynamic landscape,
meaning meaning what's popular changes. Adware is still huge, like
two thirds of the malicious apps they reported were adware.
Joker malware is also significant and about a quarter okay,
and they've seen a rise lately in adwear, Jober, another

(08:10):
one called Harley, and banking trojans like Anatza. Meanwhile, some
other families like Facetealer and Coper seem to be declining
a bit.

Speaker 1 (08:18):
So it's this constant cat and mouse game exactly.

Speaker 2 (08:22):
Threat actors shift tactics, security researchers, adapt, platforms update. It's ongoing.
For developers, it means you can't just secure against yesterday's threats.
You have to watch the trends.

Speaker 1 (08:34):
So let's bring it back to the listener. Whether you're
developing apps for iOS, Android, Harmony OS, or you're just
using these devices daily, what can you actually do.

Speaker 2 (08:43):
Well for Android users specifically given Annatsa's methods. The advice
sounds basic, but it's critical, which is, verify app permissions
meticulously before you tap allow, Ask yourself, does this app
really need this permission to do its job right, Like does.

Speaker 1 (09:00):
A QR code scanner genuinely need accessibility services exactly?

Speaker 2 (09:04):
That should be a massive red flag. If the permissions
don't align with the app's purpose, just deny it, or,
better yet, uninstall the app. It really forces you to
reconsider all those permission pop ups, doesn't it.

Speaker 1 (09:15):
It really does? Okay, Well, what if the worst happens?
What if you suspect a device is compromised by something
like an.

Speaker 2 (09:20):
Not to day disinfection can be tricky. First step is
obviously trying to remove the malicious app.

Speaker 1 (09:25):
But you said ANSA might try to stop that.

Speaker 2 (09:28):
It might. Yes, some malware actively resists uninstallation. If you
can remove it, great, But if you can't, or if
you want to be absolutely.

Speaker 1 (09:34):
Sure it's gone, factory reset.

Speaker 2 (09:36):
A factory reset might be the necessary, though drastic step
for complete certainty wipes everything, including the malware. And for
the tech folks listening, z scaler uses specific detection names
Android dot banker dot ETSA and agentfive dot AE, Android
osagent dot BOI, useful for threat intel feeds and SoCs.

Speaker 1 (09:57):
Good to know. So wrapping this up then, and NASA
is clearly a potent evolving threat use a sophisticated tricks
exploits user trust. It really highlights the need for constant vigilance,
doesn't it, both in how we use apps and how
we build them.

Speaker 2 (10:11):
It really does. And this whole situation, this ongoing back
and forth, it shows that relying solely on the built
in protections from Apple, Google, Huawei, while they're essential, they're
just not always enough on their own real mobile app security,
especially if you're developer building for these platforms or using
cross platform tools like Flutter or React Native. It needs
multiple layers. It needs developers implementing proactive security measures, It

(10:34):
needs continuous awareness from everyone involved, and it needs users
to be educated and cautious. It really makes you wonder, though,
in a world where our phones are so central, especially
to our finances, where should the responsibility ultimately lie the
app stores, the developers, us, the users. Is just telling
everyone to be vigilant a truly sustainable long term strategy

(10:57):
or do we need a more fundamental rethink about how
trust and security are baked into the mobile ecosystem from
the ground up.

Speaker 1 (11:03):
That is definitely something to think about. A great point
to end on. Thanks for joining us to this discussion.
This podcast was made with human sources and assisted with
AI
Advertise With Us

Popular Podcasts

Stuff You Should Know
The Joe Rogan Experience

The Joe Rogan Experience

The official podcast of comedian Joe Rogan.

24/7 News: The Latest

24/7 News: The Latest

The latest news in 4 minutes updated every hour, every day.

Music, radio and podcasts, all free. Listen online or download the iHeart App.

Connect

© 2025 iHeartMedia, Inc.