Which versions of pflag14570 are malicious?

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

How do I remediate pflag14570 if I installed it?

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

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

Yes — pflag14570 is associated with the IN-MAL-2026-020245, GHSA-qxgf-vc83-fc34 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 pflag14570 across my projects, lockfiles, and CI pipelines?

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

Malicious package

pflag14570npm

Advisory published Sep 21, 2026Updated Oct 1, 2026

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

MAL-2026-16341

Immediate action

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

npm uninstall pflag14570

What this malware does

index.js is an IIFE that executes at module load, reads document.cookie, fetches a list of authenticated application paths (/profile, /admin, /api/me, /settings, and similar), extracts a flag-shaped substring from the responses, and POSTs the aggregated JSON to the hardcoded collector https://webhook.site/42c6d937-77c7-42a5-8678-ef06b4501e38. The package metadata is a stub with no legitimate documented function; the shipped body is a browser-context session-cookie stealer and endpoint scraper directed at a third-party attacker-controlled collector.

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)

2b7164c1405ab2587c562b3b9eb8cdad8258aab8f25b829da64c83d7185eab6c

06175f7a39cb50eac8845d48ee3996962973a147480eeab9238f039a91d5da2f

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for pflag14570 (version 1.0.0).
If you installed it — respond
pflag14570 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 pflag14570 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. pflag14570 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-020245GHSA-qxgf-vc83-fc34

References

Credits

Amazon Inspector · finder

Detect & block this

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