Which versions of easypanel-core are malicious?

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

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

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

If easypanel-core was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is easypanel-core part of a known attack campaign?

Yes — easypanel-core is associated with the IN-MAL-2026-019455 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-core across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for easypanel-core (version 1.0.0).

Malicious package

easypanel-corenpm

Advisory published Sep 4, 2026Updated Sep 4, 2026

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

MAL-2026-15897

Immediate action

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

npm uninstall easypanel-core

What this malware does

easypanel-core ships an inert module.exports = {} main and places all functionality in a preinstall lifecycle script. On npm install, preinstall.js collects os.hostname(), os.userInfo().username, process.cwd(), and the names of CI-related environment variables, base64url-encodes them, and transmits the data to *.daco3v4q6f49egu1ds1gwjnsjb88s5kcp.oob.lyomeri.com via both a DNS subdomain lookup and an HTTP GET to /npm/<encoded>. The package name mimics the easypanel project and the description advertises a 'client library', while the shipped library exports nothing and provides no functionality — the install-time beacon is the sole behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4cb013a465c19126feba2006a81f33d65cc64b269e3da8ffe4e8284c7defa3cc

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for easypanel-core (version 1.0.0).
If you installed it — respond
easypanel-core 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-core was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. easypanel-core 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-019455

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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