Which versions of kwami are malicious?

The following npm versions of kwami are flagged malicious: 1.5.9, 1.5.10. Treat any of these as compromised.

How do I remediate kwami if I installed it?

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

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

Yes — kwami is associated with the GHSA-5x6x-h76w-7669 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 kwami 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 kwami (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kwami across your stack and pipelines.

Malicious package

kwaminpm

Malicious code in kwami (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191121

Immediate action

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

npm uninstall kwami

What this malware does

The package kwami 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

2 flagged

1.5.91.5.10

Indicators of compromise (SHA-256)

4bb8cadf47cecbcb6cc8b75632c3af5f67d8d202bc8a30ac4dad5521edcadfd2

fb3005ddddbc133827efc76644be12639b7a6de3b1e52d431ad055e04c0f0cd7

962220b95b8768ca9d0f5211baf9f5169003e56d4e99013aee0fc583b97dd51b

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

Campaign

GHSA-5x6x-h76w-7669

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks kwami-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