Which versions of plogme are malicious?

The following npm versions of plogme are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate plogme if I installed it?

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

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

Yes — plogme is associated with the IN-MAL-2026-020773, IN-MAL-2026-020774, IN-MAL-2026-020771, IN-MAL-2026-020770 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 plogme across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for plogme (4 malicious versions).

Malicious package

plogmenpm

Advisory published Sep 8, 2026Updated Sep 30, 2026

plogme is a confirmed malicious npm package (MAL-2026-16199) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in plogme (npm)

MAL-2026-16199

Immediate action

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

npm uninstall plogme

What this malware does

plogme is a renamed fork of the Baileys WhatsApp Web library from the same publisher-controlled family as @crysnovax/baileys (MAL-2026-15917), and versions 1.0.0 through 1.0.3 carry the same forced-follow and fingerprint modules. lib/Utils/channel-policy.js (javascript-obfuscator output, identical to the file in MAL-2026-15917) hardcodes the publisher's WhatsApp newsletter channels 120363423670814885@newsletter and 120363402922206865@newsletter and exports followCrysnovaxTrustedChannels(); lib/Socket/socket.js invokes it from the connection.update handler, so the user's own authenticated WhatsApp account silently follows both channels on every successful connection, with no opt-out. lib/Utils/integrity.js hashes hostname, platform, arch, cpu model and Node version into a machine fingerprint and POSTs it with the package identity to https://bailey.crysnovax.link/api/v1/verify on every socket connect. The obfuscated follow module was decoded, not executed.

The package was found to contain malicious code or consuming dependency that contains malicious code

Malicious versions

4 flagged

1.0.01.0.11.0.21.0.3

Indicators of compromise (SHA-256)

119fcc6129acfa344451ddc3153a9f5215ec2a2c9650a8cb891efc29e774f5f1

6bb65c1526d48d46d8cefcbeaa3663739b5575898d0ae337475453f5809ab10f

910cb874b9df298181240891f01e41aece4a3f674f8de8efe3744b006783256f

d4d72ac4eb16e8ce1e67583792162e2565f96c0153f07453b8a2f6569a368eab

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for plogme (4 malicious versions).
If you installed it — respond
Remove plogme 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 plogme 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. plogme on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020773IN-MAL-2026-020774IN-MAL-2026-020771IN-MAL-2026-020770

References

Credits

Amazon Inspector · finder
pkgwarden · finder

Detect & block this

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