Anubis
Anubis is a name used in the provided content for multiple distinct malware families and operations. Most consistently, it refers to an Android banking trojan. In that role, Anubis is described as targeting financial applications, including 377 app variants across 93 countries, and stealing credentials through keylogging, screenshot capture, SMS interception for one-time passwords, and abuse of Android Accessibility Service. Reported Android capabilities include sending, receiving, and deleting SMS messages; stealing the device contact list; collecting the device ID; accessing contacts and location; recording audio; making calls; modifying external storage; and exfiltrating files encrypted by an onboard ransomware module. Infection vectors mentioned include malicious Android apps, including Google Play droppers named Currency Converter and BatterySaverMobi, fake system-update prompts that trick users into installing a payload APK, and broader malicious APK distribution. The dropper activity cited used motion-sensor-based anti-analysis, recovered command-and-control information from encoded Telegram and Twitter page requests, and was linked to the domain aserogeege.space and related infrastructure including IP 47.254.26.2. The content also notes infrastructure previously associated with the Anubis banking trojan at IP 185.141.62.123.
The content also uses Anubis to refer to a Python-based backdoor associated with FIN7/GrayAlpha. That Anubis backdoor is described as providing full system control via in-memory execution and using Base64-encoded communications with command-and-control infrastructure.
Separately, the content refers to an Anubis ransomware operation and ransomware-as-a-service program. This Anubis ransomware is described as using encryption and extortion tactics, targeting mid-sized organizations, and in one report supporting Windows, Linux, NAS, and ESXi x64/x32 environments, using ChaCha+ECIES, elevating privileges to NT AUTHORITY\SYSTEM, self-propagating encryption across a domain, and being managed through a web panel. Reported victimology in the content includes healthcare and critical infrastructure, with specific incidents involving Brockton Hospital/Signature Healthcare and a claimed theft of 170 GB of data from AkzoNobel. Because the provided material conflates these separate malware uses under the same name, attribution of any single capability to all "Anubis" references would be inaccurate.
Hunt this family in your stack
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
Groups observed using it
1 distinct threat actor attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.
In its most recent campaigns, FIN7 has been observed deploying the Python-based Anubis backdoor, which provides full system control via in-memory execution and communicates with its command-and-control infrastructure using Base64-encoded data.
Techniques & procedures
22 distinct techniques documented for this family, organized by ATT&CK tactic.
Initial Access
3 techniques
Initial Access
“This mechanism and similar techniques are the main implementation for the drive-by downloads typically associated with malvertising campaigns.”
Execution
2 techniques
Execution
Persistence
1 technique
Persistence
Privilege Escalation
1 technique
Privilege Escalation
Stealth
6 techniques
Stealth
In the Android manifest, we quickly notice: 1. Names are obfuscated. That’s frequent with malware... notice the first line creates a variable which is not used: this is junk code, to make reversing complicated.
That path is not in the DEX. This typically indicates the sample is packed, and the manifest references names of an unpacked DEX that we need to recover.
On May 1, 2020, a new version of Android BankBot (aka Anubis, Nautilus Bot) was spotted. The malware poses as an COVID-19 alert application.
We search in the APK and quickly spot a Pa.json among the assets. Unfortunately, it is not a DEX, nor a ZIP, but encrypted content. So, at some point the asset Pa.json is read, then decrypted, then loaded with DexClassLoader.
Credential Access
3 techniques
Credential Access
Discovery
1 technique
Discovery
Collection
4 techniques
Collection
Our data shows that the latest version of Anubis has been distributed to 93 different countries and targets the users of 377 variations of financial apps to farm account details. We can also see that, if Anubis successfully runs, an attacker would gain access to contact lists as well as location.
a copy of the Anubis banker Trojan ... intercepts and forwards the credentials for online financial transactions to criminals.
Command and Control
3 techniques
Command and Control
Exfiltration
1 technique
Exfiltration
SpyNote RAT can copy files from the device to the C2 server. ViceLeaker can copy arbitrary files from the device to the C2 server, can exfiltrate browsing history, can exfiltrate the SD card structure, and can exfiltrate pictures as the user takes them. TriangleDB has collected and exfiltrated files.
IOCs tracked for this family
31 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.
IPs, domains, and DNS infrastructure linked to this family.
File hashes (MD5, SHA-1, SHA-256) from samples and reports.
Other indicator types observed in public reporting.
Recent activity
40 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A ransomware operation notable for targeting healthcare and critical infrastructure more readily than peer groups.
Ransomware operation using encryption and extortion, observed disrupting healthcare providers.
Ransomware operated as a Ransomware-as-a-Service platform that encrypted systems at Brockton Hospital / Signature Healthcare, disrupting patient care, diverting ambulances, and preventing prescription fulfillment.
A banking trojan codebase from which Falcon variants spun out.
The version that knows your environment.
Match every observed IP, domain, and hash against your live telemetry.
Named campaigns wielding this family, with evidence pinned to each claim.
CVEs this family uses for access and lateral movement.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Every documented technique, ranked by evidence weight.
Reddit, Mastodon, and CTI community discussion around this family.