Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

kamafhbnowctnpm

kamafhbnowct is a confirmed malicious npm package (MAL-2026-16450) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kamafhbnowct (npm)

MAL-2026-16450
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall kamafhbnowct

What this malware does

The package was found to contain malicious code or consuming dependency that contains 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.

Malicious versions

2 flagged
1.0.01.0.1

Indicators of compromise (SHA-256)

87e15811e108a2a80c81c60340e92751a09556a88009dab85d150e1dad45a8a2
646021a6b47fafd23415f7357b91660f4ce18545fa5f9b2ba370842c632fb92d
6c44e5e3f55c73b23e3255f875d0d73bd409ffbc291265b9d28d2be9dff0baaf

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for kamafhbnowct (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kamafhbnowct across your stack and pipelines.

  2. If you installed it — respond

    Remove kamafhbnowct from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If kamafhbnowct 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.

  4. How O3 protects you

    O3 blocks kamafhbnowct 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. kamafhbnowct on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j87m-pgqx-mpg5IN-MAL-2026-020478IN-MAL-2026-020479

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks kamafhbnowct-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

kamafhbnowct (npm) malicious package — MAL-2026-16450 | O3 Security