Which versions of easypanel-hosting are malicious?

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

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

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

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

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

Malicious package

easypanel-hostingnpm

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

MAL-2026-16075

Immediate action

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

npm uninstall easypanel-hosting

What this malware does

[email protected] ships a stub index.js (module.exports = {}) and an npm preinstall lifecycle script that collects the installer's hostname, username, current working directory, and CI-related environment variable names, base64url-encodes them, and sends them off-host via a DNS lookup and an HTTP request to a hardcoded out-of-band subdomain under lyomeri.com (e.g. easypanel-hosting.<token>.oob.lyomeri.com, with the encoded payload placed in the DNS label and in the HTTP path /npm/<encoded>). The exfiltration fires automatically on npm install before any user code runs. The empty main module and package name resembling a hosting-adjacent product are consistent with a dependency-confusion or reconnaissance probe; regardless of framing, installer identity metadata leaves the machine unconditionally to an author-controlled OOB collector.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

db6a378b33bb2f33088ed90db4ac48e81368e30d5ef38578dca3b4345e9cb06b

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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