Which versions of medusa-plugin-momo are malicious?

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

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

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

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

Yes — medusa-plugin-momo is associated with the GHSA-3whr-4xm2-9pvr 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-momo 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-momo (version 0.0.68). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging medusa-plugin-momo across your stack and pipelines.

Malicious package

medusa-plugin-momonpm

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

MAL-2025-190850

Immediate action

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

npm uninstall medusa-plugin-momo

What this malware does

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

Indicators of compromise (SHA-256)

0cde6fd1ff9ede7f7cdf302b201f820ff874931c8395e15cfb1c79c5bc113c65

4670d82d1db3b1865426e69d47798cb98aaed8be48cec99e86be3741872aa936

5073c40031e52deb8e0d0062a23f9616dde8f25e38e0bbbf9f03f3a6f38abec3

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

Campaign

GHSA-3whr-4xm2-9pvr

References

Credits

Amazon Inspector · finder

Detect & block this

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