SARA Node.js Android Ransomware Code Leaked on Forum
The source code for SARA, a Node.js-based Android ransomware tool, has been distributed on underground hacking forums. Discover how this lightweight malware exploits legacy Android permission models and learn critical containment procedures to safeguard enterprise mobile assets.

Key Takeaways
- SARA is a lightweight Node.js-based Android ransomware that uses system alert window overlays to lock device screens.
- The source code has been leaked on the Breached forum, lowering the barrier to entry for amateur threat actors.
- By targeting legacy SDK versions, the malware can bypass newer Android permission models and gain silent approval upon installation.
Underground forums are seeing a rise in the democratization of mobile threats, highlighted by the public distribution of a simple Node.js-based Android ransomware program known as SARA. The source code, published by a threat actor using the alias AdellXnet on the Breached forum, lowers the entry barrier for low-skilled adversaries looking to deploy functional mobile locker campaigns. This public availability allows malicious actors to easily compile and modify the code, increasing the risk of widespread opportunistic attacks targeting personal and corporate mobile devices alike.
While traditional Android ransomware has relied heavily on native Java or Kotlin development, the emergence of lightweight JavaScript and Node.js-based variants signals a shift toward cross-platform frameworks. By using runtimes like Node.js for Mobile or packaging tools such as Apache Cordova, threat actors can bypass traditional signature-based detection mechanisms that struggle to inspect packaged JavaScript bundles. Security teams must adapt to this evolution by analyzing the specific behaviors and permissions used by these hybrid applications.
Deep Technical Analysis of SARA
SARA functions as an Android locker program written in Node.js, designed to hijack the device UI and force users into paying a ransom. The underlying code uses a simple yet effective architecture that combines a background service with a persistent system alert window. In typical configurations, the malware utilizes an embedded JavaScript runtime to execute system-level commands through a terminal wrapper or an embedded WebView framework.
A notable vector for running SARA on target devices involves terminal environments such as Termux. Attackers frequently trick users into executing the scripts manually under the guise of security testing or running automated bot platforms. Alternatively, they package the code into a standard APK using cross-platform compilation frameworks, making the threat indistinguishable from legitimate mobile applications at a glance. Organizations can proactively manage these risks by implementing comprehensive vulnerability assessments across their entire mobile fleet.
The Step-by-Step Attack Chain
The execution cycle of this ransomware progresses through three distinct phases, beginning with targeted social engineering and culminating in device lockdown and encryption.
SARA Ransomware Step-by-Step Execution Chain
- 1Initial Access
Lures via forums, Telegram, or fake app clones (e.g., tiktok.apk, onlyfans.apk).
- 2Privilege Abuse
Exploits legacy targetSdkVersion <= 22 to bypass runtime prompts and silently gain permissions.
- 3Impact & UI Lock
Launches com.termuxhackers.id.MyService and draws over device UI using SYSTEM_ALERT_WINDOW.
Phase 1: Initial Access. Adversaries distribute SARA through localized download links on community channels, Telegram groups, and direct file-sharing sites. The files are disguised as high-demand utilities, visual modification tools, or cracked premium applications. Because the source code is public, any threat actor can easily customize the application name, icon, and embedded configuration to match popular regional services.
Phase 2: Execution and Privilege Abuse. Once installed, SARA exploits a well-known vulnerability in older Android permission architectures. By setting the target SDK version in the app's build files to version 22 or lower, the application requests all declared manifest permissions upon installation. On many legacy or unpatched Android devices, the operating system silently approves these permissions, including the critical system alert overlay permission, without prompting the user during runtime.
Phase 3: Impact and Locking Mechanics. Upon launch, a background service registered in the manifest (typically named com.termuxhackers.id.MyService) is triggered. This service creates a persistent system alert window that draws over every other application on the screen. The overlay intercepts touch inputs, rendering the home button, back button, and settings menu completely unresponsive. Simultaneously, advanced variants can utilize standard Node.js cryptographic libraries to encrypt user directories, changing file extensions and displaying a ransom note that demands cryptocurrency payments.
Threat Actor Tactics and MITRE ATT&CK Mapping
Analyzing the behavioral indicators of SARA allows security operations teams to establish proactive threat hunting rules. The ransomware depends on several standard tactics to maintain persistence and bypass operating system protections.
SARA Ransomware MITRE ATT&CK Mapping
Event Triggered Execution (T1624): The malware automatically boots up with the device by listening to the system boot completion broadcast receiver. This ensures that even if the user restarts the phone, the lock screen overlay launches immediately upon startup.
Obfuscated Files or Information (T1406): Because the core logic is written in JavaScript, attackers frequently run the code through tools like JS-Obfuscator before compiling the APK, stripping variable names and inserting dead code to evade static analysis engines.
Lock Screen Dismissal Bypass (T1470): By misusing the SYSTEM_ALERT_WINDOW privilege, the malware prevents the user from accessing system settings to manually uninstall the app.
File Encryption (T1630): The payload executes recursive directory traversal across the shared storage environment, encrypting media files and databases using lightweight JavaScript cryptographic algorithms.
Enterprise Mobile Risks and Incident Prevention
Mobile devices are often the weakest link in corporate perimeter defenses. Compromised mobile endpoints can act as springboards for lateral movement, credential theft, and unauthorized access to corporate networks. If an employee installs SARA on a work-configured device, sensitive company data stored locally on the shared storage partition could be permanently lost or exfiltrated.
To reduce this exposure, security teams must regularly monitor their organization's exposed assets. Using tools to evaluate rogue assets is highly beneficial. For example, if your corporate domain has been targeted by credential-harvesting campaigns that distribute these malicious packages, checking your status via a Dark Web Scanner can provide immediate visibility into leaked employee credentials or active threats.
Furthermore, organizations should implement automated attack surface management to identify unmanaged mobile assets and shadow applications. Ensuring that employees only install applications from verified, enterprise-approved app stores is the single most effective administrative control against this threat.
Detection, Containment, and Remediation Protocols
Organizations can deploy specific detection rules within their endpoint management tools to flag suspicious APK packages before they run. A standard YARA rule can be utilized to scan local storage or application deployment pipelines for SARA-related signatures.
Verified Indicators of Compromise (IoCs)
- hash6dc068db642247295e96437d8aca60a0SARA Android Ransomware MD5 File Hashhash6dc068db642247295e96437d8aca60a0SARA Android Ransomware MD5 File Hash
- hash00dc92f14326c7b0e87e877bfd12a7dfSARA Android Ransomware MD5 File Hashhash00dc92f14326c7b0e87e877bfd12a7dfSARA Android Ransomware MD5 File Hash
- hash6b9157e059da44f13843e682ac3bcba7SARA Android Ransomware MD5 File Hashhash6b9157e059da44f13843e682ac3bcba7SARA Android Ransomware MD5 File Hash
- domainiloveanimals.shopStealit / Node.js Campaign Command & Control (C2)domainiloveanimals.shopStealit / Node.js Campaign Command & Control (C2)
- domaingithub.com/termuxhackers-id/SARASARA Distribution GitHub Repositorydomaingithub.com/termuxhackers-id/SARASARA Distribution GitHub Repository
- domaingithub.com/R1punk/SARASARA Distribution GitHub Repositorydomaingithub.com/R1punk/SARASARA Distribution GitHub Repository
rule Detect_SARA_Ransomware {
meta:
description = "Detects Simple Android Ransomware Attack artifacts"
author = "FemtoSec Threat Intelligence"
strings:
$pkg_name = "com.termuxhackers.id"
$service = "MyService"
$lock_msg = "Your device has been locked" nocase
condition:
any of them
}If an administrator suspects that a device has been infected, they can validate the presence of the malware by decompiling the suspect APK using standard security tools. Reviewing the Android Manifest file will reveal the presence of the system alert window permission alongside a legacy target SDK version.
In the event of an active compromise where the screen is locked, containment must be executed immediately. Security personnel should disconnect the device from all cellular and wireless networks to prevent any background exfiltration or key exchange with the attacker's server.
If Android Debug Bridge (ADB) debugging was previously enabled on the device, administrators can connect the phone to a secure workstation and run terminal commands to force-uninstall the malicious package. The terminal command adb shell pm uninstall com.termuxhackers.id will remove the application and restore access to the interface. Alternatively, booting the device into Safe Mode disables all third-party overlays, allowing users to navigate to the system settings and manually uninstall the fraudulent application.
Android Ransomware Containment & Remediation Checklist
- Network IsolationImmediately disconnect cellular and Wi-Fi connections to block C2 exfiltration.
- ADB RemediationRun 'adb shell pm uninstall com.termuxhackers.id' to forcibly uninstall the package.
- Safe Mode BootBoot into Safe Mode, bypassing overlays, and uninstall the fraudulent app manually through Android Settings.
- Deploy YARA RulesConfigure local scanners to flag malicious package artifacts matching SARA signatures.
How to Defend Against Similar Threats
- Implement Mobile Device Management policies to block side-loading of unauthorized APK files.
- Restrict the installation of legacy apps targeting Android SDK version 22 or lower unless verified.
- Utilize mobile endpoint detection and response tools to scan for known SARA package indicators.
Threat Intel FAQ
What is SARA Android ransomware and how does it work?
How can enterprise security teams detect and prevent SARA ransomware?
Could a similar threat affect your organization?
If your team may be exposed to a similar threat, FemtoSec can help validate blast radius, prioritize remediation, and connect the issue to a practical security program.
Related Threats

The Delhi Heart and Lung Institute has fallen victim to a major breach by the Krybit ransomware syndicate. The threat actors claim to have exfiltrated 22 GB of sensitive hospital, patient, employee, and corporate data, threatening public release within a short four-day window.

November 5, 2026
SHIBA Ransomware Claims German HVAC Provider
SHIBA ransomware has claimed a data breach targeting German building services provider TEMA Haus- und Wärmetechnik. Learn about the threat group's double-extortion tactics, initial access vectors, PowerShell execution patterns, and actionable defense strategies for critical enterprise infrastructure.

October 23, 2026
Kazu Ransomware Targets Insurance Sector in 366 GB Breach
Kazu ransomware operators have listed South African insurer Rand Mutual Assurance on their dark web leak portal, claiming 366 GB of exfiltrated corporate records. This intelligence brief examines Kazu's attack tradecraft, LockBit lineage, operational impact, and concrete detection rules.