Which versions of strapi-plugin-logger are malicious?

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

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

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

If strapi-plugin-logger was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is strapi-plugin-logger part of a known attack campaign?

Yes — strapi-plugin-logger is associated with the GHSA-3f9q-mrvh-3g67 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-logger across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for strapi-plugin-logger (version 3.6.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging strapi-plugin-logger across your stack and pipelines.

Malicious package

strapi-plugin-loggernpm

Malicious code in strapi-plugin-logger (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2469

Immediate action

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

npm uninstall strapi-plugin-logger

What this malware does

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

dcdd49229d2f4aa5cdd4c01e40e20ef8c6821a5f843cd5c489e32d97ebe5a7be

b112e673207be14eacf69a3e9f49d5e6952c27a5303aae7455ac41a6a316c88e

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for strapi-plugin-logger (version 3.6.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging strapi-plugin-logger across your stack and pipelines.
If you installed it — respond
strapi-plugin-logger 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-logger was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks strapi-plugin-logger before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. strapi-plugin-logger 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-3f9q-mrvh-3g67

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

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