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

kwp-shared-components-production-systemnpm

Malicious code in kwp-shared-components-production-system (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-480
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall kwp-shared-components-production-system

What this malware does

The package kwp-shared-components-production-system 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.

Malicious versions

4 flagged
0.0.1-security6.6.67.7.79.9.9

Indicators of compromise (SHA-256)

2b2bf82ab1e7b02c2c3398dc73b6c1635e7f3e8da7f0a3aa11123d5db5a19b56
da9ef3ed80c88933ad9c55e74914ecc58ae0f5ff58929a8d1f6aab88fa9ad9d8
2921793e680a6b1db313148bc3f067d04eccf13d9fa0381d3afd0f0d2273e4d3

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

  2. If you installed it — respond

    Remove kwp-shared-components-production-system 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 kwp-shared-components-production-system 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 kwp-shared-components-production-system 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. kwp-shared-components-production-system on npm has been identified as a malicious package (versions 0.0.1-security, 6.6.6, 7.7.7, 9.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5rrx-w333-h86qRLMA-2026-01395

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks kwp-shared-components-production-system-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.

kwp-shared-components-production-system (npm) malicious package — MAL-2026-480 | O3 Security