LiveActive security incident?Get immediate response
MITRE ATT&CK® Malware

S0478: EventBot

EventBot is an Android banking trojan and information stealer that abuses Android’s accessibility service to steal data from various applications.[1] EventBot was designed to target over 200 different banking and financial applications, the majority of which are European bank and cryptocurrency exchange applications.[1]

MobileS0478MalwareObject v1.0Modified
Discuss defensive coverageBack to ATT&CK
Glexia's Take · Automated analysis

Security context for executives and security teams

Automation confidenceMedium

S0478: EventBot describes [EventBot](https://attack.mitre.org/software/S0478) is an Android banking trojan and information stealer that abuses Android’s accessibility service to steal data from various applications.(Citation: Cybereason EventBot) [EventBot](https://attack.mitre.org/software/S0478) was designed to target over 200 different banking and financial applications, the majority of which are European bank and cryptocurrency exchange applications.(Citation: Cybereason EventBot)

Executive priority

S0478: EventBot is an official MITRE ATT&CK software. Glexia treats it as defensive behavior context for prioritizing monitoring, control validation, and response planning without using the object by itself as an attribution claim.

Technical view

Security teams should validate S0478: EventBot by reviewing the official ATT&CK relationships, mapped tactics (the mapped ATT&CK tactic context), supported platforms (Android), and available local telemetry before making detection or mitigation decisions.

Likely telemetry

  • Official ATT&CK relationships and object metadata

Detection direction

  • Validate whether S0478: EventBot appears in your detection coverage and tabletop scenarios.
  • Use the object to align executive risk language with SOC, incident response, and detection engineering work.
  • Do not treat ATT&CK relationship context as attribution without corroborating evidence.

Mitigation priorities

  • Map the object to existing controls and identify missing telemetry or response ownership.
  • Prioritize mitigations that reduce exposure on the listed platforms and tactics.
  • Review adjacent ATT&CK relationships before changing policy, detections, or reporting language.
Additional notes and limits

Baseline Glexia take generated from the official MITRE ATT&CK STIX object, source hash, tactics, platforms, and detection fields. It is safe to replace with a richer model-generated take for the same source hash later.

This baseline take is source-grounded and schema-validated, but it does not include environment-specific telemetry, incident evidence, or threat-intelligence corroboration.

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Official MITRE ATT&CK definition

EventBot

EventBot is an Android banking trojan and information stealer that abuses Android’s accessibility service to steal data from various applications.[1] EventBot was designed to target over 200 different banking and financial applications, the majority of which are European bank and cryptocurrency exchange applications.[1]

View the same entry on attack.mitre.org (MITRE-hosted reference; in-page links above use the Glexia ATT&CK library.)

Glexia analysis

How security teams should use this page

Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.

ATT&CK relationship table

Techniques used

This mirrors the MITRE pattern of making group, software, campaign, and technique relationships scannable. Relationship notes come from mirrored ATT&CK relationship text when available.

14 rows
DomainIDNameRelationship / procedure
MobileT1521.001Symmetric CryptographySub-technique

EventBot has encrypted base64-encoded payload data using RC4 and Curve25519.[1]

MobileT1437.001Web ProtocolsSub-technique

EventBot communicates with the C2 using HTTP requests.[1]

MobileT1407Download New Code at Runtime

EventBot can download new libraries when instructed to.[1]

MobileT1636.004SMS MessagesSub-technique

EventBot can intercept SMS messages.[1]

MobileT1655.001Match Legitimate Name or LocationSub-technique

EventBot has used icons from popular applications.[1]

MobileT1417.002GUI Input CaptureSub-technique

EventBot can display popups over running applications.[1]

MobileT1422System Network Configuration Discovery

EventBot can gather device network information.[1]

MobileT1418Software Discovery

EventBot can collect a list of installed applications.[1]

MobileT1426System Information Discovery

EventBot can collect system information such as OS version, device vendor, and the type of screen lock that is active on the device.[1]

MobileT1513Screen Capture

EventBot can abuse Android’s accessibility service to capture data from installed applications.[1]

MobileT1406Obfuscated Files or Information

EventBot dynamically loads its malicious functionality at runtime from an RC4-encrypted TTF file. EventBot also utilizes ProGuard to obfuscate the generated APK file.[1]

MobileT1417.001KeyloggingSub-technique

EventBot can abuse Android’s accessibility service to record the screen PIN.[1]

MobileT1422.001Internet Connection DiscoverySub-technique

EventBot can gather device network information.[1]

MobileT1624.001Broadcast ReceiversSub-technique

EventBot registers for the `BOOT_COMPLETED` intent to auto-start after the device boots.[1]

Relationship explorer

All related ATT&CK context

uses · TechniqueT1521.001: Symmetric CryptographyMobileuses · TechniqueT1437.001: Web ProtocolsMobileuses · TechniqueT1407: Download New Code at RuntimeMobileuses · TechniqueT1636.004: SMS MessagesMobileuses · TechniqueT1655.001: Match Legitimate Name or LocationMobileuses · TechniqueT1417.002: GUI Input CaptureMobileuses · TechniqueT1422: System Network Configuration DiscoveryMobileuses · TechniqueT1418: Software DiscoveryMobileuses · TechniqueT1426: System Information DiscoveryMobileuses · TechniqueT1513: Screen CaptureMobileuses · TechniqueT1406: Obfuscated Files or InformationMobileuses · TechniqueT1417.001: KeyloggingMobileuses · TechniqueT1422.001: Internet Connection DiscoveryMobileuses · TechniqueT1624.001: Broadcast ReceiversMobile
Change history

Object version and sync metadata

The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates.

ATT&CK release
19.2
Object version
1.0
Created
Modified
Raw hash
c4bf0452940e0c3e...
Imported snapshots across ATT&CK releases(2)
ReleaseBundle importedObject versionModifiedStatusRaw hash
19.21.0Current bundlec4bf0452940e…
19.11.0Older bundlec4bf0452940e…
Raw source

Mirrored ATT&CK source object

The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.

Open mirrored raw JSONOpen MITRE-hosted copy
Source references

External references and citations

MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.

  1. [1]
    Cybereason EventBot

    D. Frank, L. Rochberger, Y. Rimmer, A. Dahan. (2020, April 30). EventBot: A New Mobile Banking Trojan is Born. Retrieved June 26, 2020.

    Open source URL
  2. [2]
    mitre-attackS0478
    Open source URL
Source and licensing

Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.

Official MITRE ATT&CK siteOfficial STIX data repositoryMITRE ATT&CK terms of use