Which versions of pf25262 are malicious?

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

How do I remediate pf25262 if I installed it?

pf25262 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 pf25262 — how do I know if it already compromised me?

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

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

Malicious package

pf25262npm

pf25262 is a confirmed malicious npm package (MAL-2026-16340) 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 pf25262 (npm)

MAL-2026-16340

Immediate action

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

npm uninstall pf25262

What this malware does

index.js contains a browser exfiltration snippet that issues a credentialed fetch to /profile, extracts a DGA{...} token or falls back to capturing document.cookie plus the response length, and redirects the browser to a hardcoded collector URL at https://webhook.site/c4e39647-bfb8-47ef-b6d4-a112aacc6cd1/ with the captured data appended to the path. The package's entire shipped payload is this authenticated-session-data exfiltration snippet, sending same-origin credentials and cookies to an attacker-controlled webhook.site bin.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

95274790fd43042ecd1fc97b2c01dc194e863809626cdaee5c7e6b0a411f8aeb

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 pf25262 (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 pf25262 across your stack and pipelines.
If you installed it — respond
pf25262 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 pf25262 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 pf25262 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. pf25262 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-020236

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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