Which versions of medusa-plugin-logs are malicious?

The following npm versions of medusa-plugin-logs are flagged malicious: 0.0.17. Treat any of these as compromised.

How do I remediate medusa-plugin-logs if I installed it?

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

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

Yes — medusa-plugin-logs is associated with the GHSA-8583-h7rv-pqr2 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 medusa-plugin-logs 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 medusa-plugin-logs (version 0.0.17). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging medusa-plugin-logs across your stack and pipelines.

Malicious package

medusa-plugin-logsnpm

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

MAL-2025-191128

Immediate action

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

npm uninstall medusa-plugin-logs

What this malware does

The package medusa-plugin-logs 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

0.0.17

Indicators of compromise (SHA-256)

56ef7dfa5334ac20cee294d6035539e84d9f3997f6a4a5278a739a0b8ff0402f

cc9421dcde6a1a16f9a2319c584b707425df0d60ef5013874bdc601d731fed82

7af11d8b0e347690c78b45c790ef5d54f7cadf6d5d2fa89a86ef6c1765ab136f

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 medusa-plugin-logs (version 0.0.17). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging medusa-plugin-logs across your stack and pipelines.
If you installed it — respond
medusa-plugin-logs 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 medusa-plugin-logs 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 medusa-plugin-logs 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. medusa-plugin-logs on npm has been identified as a malicious package (version 0.0.17 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8583-h7rv-pqr2

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks medusa-plugin-logs-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