Which versions of strapi-plugin-server are malicious?

Every published version of strapi-plugin-server on npm is considered malicious. Remove the package entirely.

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

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

If strapi-plugin-server 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 strapi-plugin-server across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for strapi-plugin-server (all published versions).

Malicious package

strapi-plugin-servernpm

Advisory published Apr 3, 2026Updated Apr 7, 2026

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

Malicious code in strapi-plugin-server (npm)

MAL-2026-2483

Immediate action

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

npm uninstall strapi-plugin-server

What this malware does

strapi-plugin-server 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-server was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

f689c25ace6203687560dc542be39490569ca1a4ac27c2f83fda73cbe5dcbf60

Detection & response playbook

Credential / info stealer

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

References

safedep.io

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

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