Which versions of tokocrytodev are malicious?

The following npm versions of tokocrytodev are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate tokocrytodev if I installed it?

tokocrytodev is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed tokocrytodev — how do I know if it already compromised me?

If tokocrytodev was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is tokocrytodev part of a known attack campaign?

Yes — tokocrytodev is associated with the IN-MAL-2026-017206 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find tokocrytodev across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tokocrytodev (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tokocrytodev across your stack and pipelines.

Malicious package

tokocrytodevnpm

tokocrytodev is a confirmed malicious npm package (MAL-2026-13687) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tokocrytodev (npm)

MAL-2026-13687

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall tokocrytodev

What this malware does

On require of index.js, top-level code starts a polling loop that GETs commands from https://badai.run.place/cekapppiapi.php?uid=<host-id>, executes them via child_process.exec, and POSTs AES-256-ECB-encrypted stdout/stderr to /fallback.php, giving the remote operator arbitrary RCE on the installer host. A stealKeysAsync() routine shell-executes find over /root/.ssh, /home/*/.ssh, /opt/wallet-keys, /etc/ssl/private, $HOME/.ethereum/keystore, /var/lib/ethereum/keystore, and /mnt/crypto/wallets for *.pem, .key, UTC--, and keystore files containing PRIVATE KEY material, and exfiltrates the contents encrypted to the same C2. For each harvested 64-hex private key (and the ETH_PRIVATE_KEY env var), the package builds a web3 wallet against mainnet.infura.io and sends the full balance minus gas to the hardcoded attacker address 0x742d35Cc6634C0532925a3b844Bc454e4438f44e. Exfil payloads are AES-256-ECB encrypted with a hardcoded key and posted as text/plain; uncaughtException and unhandledRejection handlers silently swallow errors to reduce noise.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

09fa98b6fd8313abbfeb250d10c12db28975f7bb12742f56dd5f1a3e1959d6d1

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tokocrytodev (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tokocrytodev across your stack and pipelines.
If you installed it — respond
tokocrytodev is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If tokocrytodev was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks tokocrytodev before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. tokocrytodev on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017206

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tokocrytodev-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database