Which versions of entropyeasybots are malicious?

The following npm versions of entropyeasybots are flagged malicious: 2.0.2. Treat any of these as compromised.

How do I remediate entropyeasybots if I installed it?

entropyeasybots establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

If entropyeasybots 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 entropyeasybots part of a known attack campaign?

Yes — entropyeasybots is associated with the IN-MAL-2026-011343 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 entropyeasybots 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 entropyeasybots (version 2.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging entropyeasybots across your stack and pipelines.

Malicious package

entropyeasybotsnpm

entropyeasybots is a confirmed malicious npm package (MAL-2026-11539) that opens a backdoor for remote access (malicious version 2.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in entropyeasybots (npm)

MAL-2026-11539

Immediate action

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

npm uninstall entropyeasybots

What this malware does

index.js decodes a base64-obfuscated IP (85.137.253.124) and connects a spawned /bin/sh subprocess's stdio to a TCP socket at 85.137.253.124:1111, granting remote shell access on the installer's host. package.json declares postinstall: sudo node install.js, and install.js uses node-linux's Service API to register a systemd unit named CustomBot that runs index.js with maxRestarts:10, providing root-level persistence of the backdoor across reboots. The C2 IP is stored as a base64 string and reconstructed at runtime to hide the destination.

Malicious versions

1 flagged

2.0.2

Indicators of compromise (SHA-256)

82e7d0cd2ef4870fdc4484c815737ade78e04bdac4843df02f5cf876cfa3dbaa

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for entropyeasybots (version 2.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging entropyeasybots across your stack and pipelines.
If you installed it — respond
entropyeasybots establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If entropyeasybots 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 entropyeasybots 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. entropyeasybots on npm has been identified as a malicious package (version 2.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011343

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database