Which versions of pflag29424 are malicious?

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

How do I remediate pflag29424 if I installed it?

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

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

Yes — pflag29424 is associated with the IN-MAL-2026-020244, GHSA-8jr8-g7mm-57m6 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 pflag29424 across my projects, lockfiles, and CI pipelines?

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

Malicious package

pflag29424npm

Advisory published Sep 21, 2026Updated Oct 1, 2026

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

MAL-2026-16342

Immediate action

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

npm uninstall pflag29424

What this malware does

index.js (the package's declared main) unconditionally executes on module load: it calls fetch('/profile'), scans the response for a DGA{...} token, and sends either the matched token or the first 300 characters of the response as a query parameter to a hardcoded anonymous collector at https://webhook.site/42c6d937-77c7-42a5-8678-ef06b4501e38. The package has no README, no documented purpose, and a generic throwaway name; the sole effect of loading it is to relay content from the loading context to an attacker-controlled webhook.site endpoint.

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)

d9b974c9d8555f026dfc5556c4f628d366fbaedca83eab549559fe95fc984602

cd211e848e5775cbc33c73e1f7a6a83bf8b42418e22b32479ba479fdd3430e85

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for pflag29424 (version 1.0.0).
If you installed it — respond
Remove pflag29424 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 pflag29424 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. pflag29424 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-020244GHSA-8jr8-g7mm-57m6

References

Credits

Amazon Inspector · finder

Detect & block this

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