Which versions of easydsbots are malicious?

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

How do I remediate easydsbots if I installed it?

easydsbots 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 easydsbots — how do I know if it already compromised me?

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

Yes — easydsbots is associated with the IN-MAL-2026-018382 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 easydsbots 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 easydsbots (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 easydsbots across your stack and pipelines.

Malicious package

easydsbotsnpm

easydsbots is a confirmed malicious npm package (MAL-2026-14265) 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 easydsbots (npm)

MAL-2026-14265

Immediate action

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

npm uninstall easydsbots

What this malware does

package.json declares "postinstall": "sudo node install.js", escalating to root on npm install. install.js is heavily obfuscated (obfuscator.io: rotated 140-entry string array a0_0xdc68, hex-encoded property lookups, control-flow flattening, self-defending stubs) so the executed behavior is deliberately hidden from installers. index.js is similarly obfuscated (rotated 164-entry string array a0_0x53d8, runtime base64 decoding via Buffer[...](ertrf,...).toString()), declares js-virtualizer as a runtime dependency, and reads process.env.INVOCATION_ID into an isRunningAsService flag — an environment variable set only when a process is launched by systemd. The package also depends on node-linux, a library that registers /etc/init.d or systemd unit files. The combination — root-level lifecycle hook, opaque payload, systemd-context branch, and a daemon-installer dependency — is the shape of an obfuscated root-persistent daemon dropper executed at install time on the installer's host.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

6c3ee114e4ac67d2d02a9668c7ed0b38cbf62f9bc59e35b92c0ff9e713d3a688

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 easydsbots (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 easydsbots across your stack and pipelines.
If you installed it — respond
easydsbots 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 easydsbots 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 easydsbots 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. easydsbots 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-018382

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks easydsbots-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