Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

eth-react-redirectionnpm

Malicious code in eth-react-redirection (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10127
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall eth-react-redirection

What this malware does

Package published as a React navigation library but ships code from an unrelated logger fork with an injected remote-execute payload. lib/levels.js contains a top-level IIFE that performs an HTTP GET to http://mongos-hooks-api.vercel.app/defy/v3 and, on a 404 response, passes a token field from the response body to new Function.constructor('require', res.token)(require), running arbitrary attacker-supplied JavaScript with the package's require binding. lib/const.js stores a base64-encoded secondary URL under the misleading name DEV_API_KEY that decodes to https://jsonkeeper.com/b/4NAKK, an anonymous JSON-paste host usable as a backup payload source. index.js additionally spawns a detached Node child process (process.execPath on lib/caller.js) with stdio ignored and unref()'d on every require. The package.json name and description advertise a React navigation library, while index.js is a chai assertions plugin and lib/ is a fork of pino/flowlimit — a masquerade shape. The remote-execution path fires on module load, so any consumer that requires this package triggers execution of code fetched over plain HTTP from an attacker-controlled endpoint.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

581bd6ff87fb89c83d76fffd9fac9aab57039cd200f8d9f8991ce3a997511644

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eth-react-redirection (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 eth-react-redirection across your stack and pipelines.

  2. If you installed it — respond

    eth-react-redirection 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.

  3. Did it already run?

    If eth-react-redirection 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.

  4. How O3 protects you

    O3 blocks eth-react-redirection 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. eth-react-redirection 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-009615

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks eth-react-redirection-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

eth-react-redirection (npm) malicious package — MAL-2026-10127 | O3 Security