Which versions of easypanel-agent are malicious?

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

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

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

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

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

Malicious package

easypanel-agentnpm

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

MAL-2026-16072

Immediate action

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

npm uninstall easypanel-agent

What this malware does

The package's preinstall lifecycle script (preinstall.js) executes automatically on npm install and collects the installer's hostname, OS username, current working directory, and CI-related environment variable names. The collected data is base64-encoded and transmitted to a hardcoded out-of-band collector under lyomeri.com via both a DNS lookup (encoding data into a subdomain label under easypanel-agent.<data>.oob.lyomeri.com) and an HTTP GET request to the same host. The package's main entry, index.js, is an empty stub (module.exports = {}), so the install-time beacon is the sole functional behavior. The package name mimics the 'easypanel' product, consistent with a dependency-confusion or typosquat delivery vehicle. An in-source comment self-labeling the code as a 'benign canary' does not change that installer-controlled data leaves the machine without consent to an author-controlled endpoint.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

7eb103b6863369372ba8c07701264f8b0f6b57e3217e07912c8efbd9371c648f

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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