Which versions of @kvytech/medusa-plugin-management are malicious?

The following npm versions of @kvytech/medusa-plugin-management are flagged malicious: 0.0.5. Treat any of these as compromised.

How do I remediate @kvytech/medusa-plugin-management if I installed it?

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

If @kvytech/medusa-plugin-management 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 @kvytech/medusa-plugin-management part of a known attack campaign?

Yes — @kvytech/medusa-plugin-management is associated with the GHSA-9299-g7fr-hxx9 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 @kvytech/medusa-plugin-management 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 @kvytech/medusa-plugin-management (version 0.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @kvytech/medusa-plugin-management across your stack and pipelines.

Malicious package

@kvytech/medusa-plugin-managementnpm

Malicious code in @kvytech/medusa-plugin-management (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190745

Immediate action

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

npm uninstall @kvytech/medusa-plugin-management

What this malware does

The package @kvytech/medusa-plugin-management 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.5

Indicators of compromise (SHA-256)

0910748cbd21d909fd4d2d47a2b05d74b138b65dc5448f18befc0b21c7d648af

3db2ba6d2369e5b53d1dfd5a6c8642c90217140b644f1349b42ec9d3e58fdb04

66ace6bea11aa4a81f0e01af5e161d8e8f7706b588f49890fc383bf874522ed8

3de9b55d1856e0972cdd294171a1fd9c6902723104ed689dbda283355648d6da

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

Campaign

GHSA-9299-g7fr-hxx9

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @kvytech/medusa-plugin-management-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