What does the playgod malware do?

The package playgod was found to contain malicious code. The OpenSSF Package Analysis project identified 'playgod' @ 1.1.2 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of playgod are malicious?

The following npm versions of playgod are flagged malicious: 1.1.2. Treat any of these as compromised.

How do I remediate playgod if I installed it?

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

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

How do I find playgod across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for playgod (version 1.1.2).

Malicious package

playgodnpm

Advisory published May 8, 2026Updated May 12, 2026

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

Malicious code in playgod (npm)

MAL-2026-3374

Immediate action

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

npm uninstall playgod

What this malware does

The package playgod was found to contain malicious code.

The OpenSSF Package Analysis project identified 'playgod' @ 1.1.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.1.2

Indicators of compromise (SHA-256)

a700663ab039dd35fa24734d883219fff845bb0c6017a5e0dcb0191dfa4676b0

f0aee4818420709f0d12c4a32c97671628fffdb1255fefd1895b2c3f880f8b2b

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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