Malicious code in tokocrytodev (npm)
The npm package tokocrytodev contained malicious code that established a command-and-control polling loop, harvested SSH and cryptocurrency private keys, and exfiltrated them to a remote server while also stealing Ethereum wallet balances.
- Disclosed
- Last updated
- Blast radius
- Any system that installed and required the tokocrytodev package; systems with SSH keys, wallet keys, or Ethereum keystores accessible to the Node.js process.
- Ecosystems
- Attack vectors
- Affected entities
- tokocrytodevnpm package containing malicious code
The npm package tokocrytodev was found to contain malicious code that executed on require of index.js. The package established a polling loop that fetched commands from a remote C2 server at https://badai.run.place/cekapppiapi.php and executed them via child_process.exec, providing arbitrary remote code execution on the installer's host.\n\nThe malicious code included a stealKeysAsync() routine that searched for and exfiltrated private key material from multiple locations including ~/.ssh, /opt/wallet-keys, /etc/ssl/private, Ethereum keystores, and other sensitive directories. For each harvested Ethereum private key, the package constructed a web3 wallet and transferred the full balance (minus gas fees) to a hardcoded attacker address (0x742d35Cc6634C0532925a3b844Bc454e4438f44e).\n\nAll exfiltration payloads were encrypted using AES-256-ECB with a hardcoded key before being sent to the C2 server. Error handling was deliberately suppressed via uncaughtException and unhandledRejection handlers to minimize detection.\n\nThe malicious package was identified and credited to the OpenSSF's malicious-packages repository.
Indicators of compromise
- Packages
- tokocrytodev
- Domains
- badai.run.place
Remediation
- Immediately uninstall the tokocrytodev package from all systems
- Audit npm package.lock and yarn.lock files for any installations of tokocrytodev
- Rotate all SSH keys that may have been accessible to the Node.js process
- Rotate all cryptocurrency private keys and Ethereum wallet credentials
- Review Ethereum wallet transaction history for unauthorized transfers
- Scan systems for any persistence mechanisms or additional malicious artifacts left by the package
- Review process logs and network traffic for connections to badai.run.place
- Consider the compromise of any secrets or credentials that may have been exfiltrated
Sources
- GitHub Advisory GHSA-m482-gfg4-jcp7 · GitHub Advisory Database
Cite this entry
"Malicious code in tokocrytodev (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 10, 2026; last updated August 10, 2026. https://supplychainattack.org/incident/malicious-code-in-tokocrytodev-npm-18q0in
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in autbank-core (npm)
The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.
npmCompromised package - resolvedcritical
Malicious code in adxaa (npm)
The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.
npmCompromised package - resolvedcritical
Malicious code in upload-to-gcp (npm)
upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.
npmCompromised package - resolvedcritical
Malicious code in akamai-sensor (npm)
A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.
npmCompromised packageTyposquatting