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

8i7pp4npm

Advisory published Updated

8i7pp4 is a confirmed malicious npm package (MAL-2026-17952) that steals credentials and exfiltrates sensitive data (malicious version 0.0.0-stage). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 8i7pp4 (npm)

MAL-2026-17952
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall 8i7pp4

What this malware does

Package 8i7pp4 version 0.0.0-stage contains only two files and no detected behaviors of concern. There are no lifecycle scripts fetching or executing remote content, no reads of installer secrets (environment variables, SSH/AWS/npm credentials, browser or wallet stores), no outbound network calls to attacker-controlled destinations, no obfuscated payloads, and no persistence or backdoor mechanisms. The version suffix and minimal file count are consistent with a placeholder, staging, or test publication rather than functional code.

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
0.0.0-stage

Indicators of compromise (SHA-256)

8dc37ece0db632118d074f0d0a549b4dba2ccd639a3a01c7b0b682bae81b1fc0
c623f39e0d4b0b51a05de329eccc8daa9ea567d83dc8365f3523462b2bd08b09

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for 8i7pp4 (version 0.0.0-stage).

  2. If you installed it — respond

    8i7pp4 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 8i7pp4 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. 8i7pp4 on npm has been identified as a malicious package (version 0.0.0-stage flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-97qj-xxch-gv59IN-MAL-2026-021542

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

8i7pp4 (npm) malicious package — MAL-2026-17952 | O3 Security