Which versions of easypanel-deploy are malicious?

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

How do I remediate easypanel-deploy if I installed it?

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

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

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

Malicious package

easypanel-deploynpm

easypanel-deploy is a confirmed malicious npm package (MAL-2026-16074) 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 easypanel-deploy (npm)

MAL-2026-16074

Immediate action

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

npm uninstall easypanel-deploy

What this malware does

The package's preinstall lifecycle script runs automatically on npm install and collects installer-side identifiers — os.hostname(), os.userInfo().username, the current working directory, and CI-related environment variable names — base64url-encodes them, and sends them to a hardcoded third-party out-of-band collector under oob.lyomeri.com via both a DNS lookup (easypanel-deploy.<chunk>daco3v4q6f49egu1ds1gwjnsjb88s5kcp.oob.lyomeri.com) and an HTTP GET request to the same host. The behavior fires without user consent on install, exfiltrates host reconnaissance data to an attacker-controlled endpoint, and is consistent with a dependency-confusion / beacon package. An in-source comment labeling this as a 'benign canary' does not change the observable behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

0ac486399ab6c99cf83bfcf80e487c414fd29430e27f0d929ff7034ed333c7e8

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks easypanel-deploy-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