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

kambxjowhdsgywnpm

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

Malicious code in kambxjowhdsgyw (npm)

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

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

3 flagged
1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

24a5333661877d64a01408993c063ef6f4a943dd4024c01943a63f527a030514
966589b88833a788509808e69f3fd935c370ff4093b9fc3fb50482431434a6b5
fddf018ca515bee8858190f73811749c4e507233639b1be8d371f8c5f7cb8b8e
47a2e7676cdbdb027a39ce160d344a72e23370f801babd75d9074bf0e344e505

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 kambxjowhdsgyw (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kambxjowhdsgyw across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

GHSA-pmhv-gqr9-wrgrIN-MAL-2026-020389IN-MAL-2026-020390IN-MAL-2026-020391

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

kambxjowhdsgyw (npm) malicious package — MAL-2026-16397 | O3 Security