Which versions of strapi-plugin-health are malicious?

The following npm versions of strapi-plugin-health are flagged malicious: 3.6.8. Treat any of these as compromised.

How do I remediate strapi-plugin-health if I installed it?

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

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

Yes — strapi-plugin-health is associated with the GHSA-8c3v-gc8j-xp6p 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 strapi-plugin-health across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for strapi-plugin-health (version 3.6.8).

Malicious package

strapi-plugin-healthnpm

Advisory published Apr 3, 2026Updated Apr 7, 2026

strapi-plugin-health is a confirmed malicious npm package (MAL-2026-2464) that steals credentials and exfiltrates sensitive data (malicious version 3.6.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in strapi-plugin-health (npm)

MAL-2026-2464

Immediate action

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

npm uninstall strapi-plugin-health

What this malware does

strapi-plugin-health is a malicious npm package disguised as a Strapi CMS plugin. On install, it runs a postinstall script that executes an 11-phase attack: stealing .env files, environment variables, Strapi configuration, private keys, Redis data, Docker/Kubernetes secrets, and network topology. It then opens a polling C2 loop that accepts and executes arbitrary shell commands from a remote server.

The package strapi-plugin-health was found to contain malicious code.

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

3.6.8

Indicators of compromise (SHA-256)

dd2c06da003c0152c006fff83c7c096ec261045271548f6e8c114d25d65d5b42

f85febdc75e5d35eefd778345ab9c11e2c3f8e6bbe586e706ce6d6fb1dfb2e7e

Detection & response playbook

Credential / info stealer

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

Campaign

GHSA-8c3v-gc8j-xp6p

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks strapi-plugin-health-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