NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

pf23727npm

Advisory published Updated

pf23727 is a confirmed malicious npm package (MAL-2026-16338) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pf23727 (npm)

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

What this malware does

index.js is the package main and runs as an IIFE on require()/import. It reads document.cookie, slices document.body.innerHTML, and issues fetch('/profile', {credentials: 'include'}) to capture an authenticated response, then transmits the concatenated data via navigator.sendBeacon/fetch to a hardcoded collector at https://webhook.site/c4e39647-bfb8-47ef-b6d4-a112aacc6cd1. The destination is an unrelated third-party request-inspection service used as an exfiltration sink; the package has no declared legitimate purpose consistent with reading cookies or authenticated profile content. Behavior is a session-cookie and credentialed-response exfiltration payload rather than a functional library.

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
1.0.0

Indicators of compromise (SHA-256)

f83e32460196d036eca65e46845ea4717a9d5e64a5c2360d657d1ae6c92dfe96
7b5508b450ed2def5348f6955f1ffd3cd20cda6e300d127d779e6d0c8606302d

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for pf23727 (version 1.0.0).

  2. If you installed it — respond

    pf23727 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 pf23727 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. pf23727 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-020246GHSA-p2hc-jmvm-qwc9

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks pf23727-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

pf23727 (npm) malicious package — MAL-2026-16338 | O3 Security