Which versions of pf23727 are malicious?

The following npm versions of pf23727 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate pf23727 if I installed it?

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.

I already installed pf23727 — how do I know if it already compromised me?

If pf23727 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 pf23727 part of a known attack campaign?

Yes — pf23727 is associated with the IN-MAL-2026-020246 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 pf23727 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 pf23727 (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 pf23727 across your stack and pipelines.

Malicious package

pf23727npm

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f83e32460196d036eca65e46845ea4717a9d5e64a5c2360d657d1ae6c92dfe96

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 pf23727 (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 pf23727 across your stack and pipelines.
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.
Did it already run?
If pf23727 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 pf23727 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. 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-020246

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database