NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

strapi-plugin-corenpm

Advisory published Updated

strapi-plugin-core is a confirmed malicious npm package (MAL-2026-2456) 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-core (npm)

MAL-2026-2456
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall strapi-plugin-core

What this malware does

strapi-plugin-core 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-core 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)

85e3f70fe767a9478096598c575930664478cb98a7298015ec09b835e8728c8a
92f4c7f7f306bc888b20d0b9146905ad960379530c0ddd17bcf920cada8967f1

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    strapi-plugin-core 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.

  3. Did it already run?

    If strapi-plugin-core 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-core 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-rhv5-72hc-mr25

References

Credits

  • Amazon Inspector · finder
  • SafeDep · finder

Detect & block this

O3 blocks strapi-plugin-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

strapi-plugin-core (npm) malicious package — MAL-2026-2456 | O3 Security