Which versions of pf25133 are malicious?

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

How do I remediate pf25133 if I installed it?

Remove pf25133 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If pf25133 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.

Is pf25133 part of a known attack campaign?

Yes — pf25133 is associated with the IN-MAL-2026-020243, GHSA-8f7g-cf69-g5p8 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 pf25133 across my projects, lockfiles, and CI pipelines?

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

Malicious package

pf25133npm

Advisory published Sep 21, 2026Updated Oct 1, 2026

pf25133 is a confirmed malicious npm package (MAL-2026-16339) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pf25133 (npm)

MAL-2026-16339

Immediate action

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

npm uninstall pf25133

What this malware does

The package's declared main module index.js is an IIFE that reads document.cookie, fetches a hardcoded list of application paths, extracts flag-shaped patterns from the responses, and POSTs the aggregated data as JSON to a hardcoded webhook.site collector URL (https://webhook.site/c4e39647-bfb8-47ef-b6d4-a112aacc6cd1). The behavior is unconditional on load and the destination is not configurable. webhook.site is a generic anonymous request-bin service unrelated to any legitimate first-party endpoint, and the package ships no functionality other than this collection payload.

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)

504c3f95c937a05e14c220c767a0e18f4cada866ee5eebad0749457232ace73b

2a468a0f803545c964b7fd5cf12d9a26dd7be416ee34d3d3728edecf99d5031f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for pf25133 (version 1.0.0).
If you installed it — respond
Remove pf25133 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If pf25133 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. pf25133 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-020243GHSA-8f7g-cf69-g5p8

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks pf25133-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database