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

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

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

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

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

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

Malicious package

@kvytech/medusa-plugin-announcementnpm

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

MAL-2025-190744

Immediate action

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

npm uninstall @kvytech/medusa-plugin-announcement

What this malware does

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

Indicators of compromise (SHA-256)

1f7c7aaddcf6972e795a38a7fba83c71af159b3b69576fa1822e85bc598e41ff

8fda18824e7544b009117ab962028a53a03245d741b85fa30789a9cda67f5b1b

a211bdbaa506109031b2d47d33a86568c7f210dd18fffb9bf2c3b75ccc480b26

baddf83634391fc236f08a831982d9f8d83ea6347c94253bbfafdcfad6246699

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

Campaign

GHSA-53mv-xhh4-47h8

References

Credits

Amazon Inspector · finder

Detect & block this

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