NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@ks-cqc/h5-sig4npm

Advisory published Updated

@ks-cqc/h5-sig4 is a confirmed malicious npm package (MAL-2026-16524) that executes malicious code on install (malicious version 2.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ks-cqc/h5-sig4 (npm)

MAL-2026-16524
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @ks-cqc/h5-sig4

Malicious versions

1 flagged
2.99.99

Indicators of compromise (SHA-256)

c0065ecf6611b82d45b5e7a5778f6d9c1f29a125393e04ceb250d201849b50fc

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for @ks-cqc/h5-sig4 (version 2.99.99).

  2. If you installed it — respond

    Remove @ks-cqc/h5-sig4 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 @ks-cqc/h5-sig4 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @ks-cqc/h5-sig4 on npm has been identified as a malicious package (version 2.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-10637

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks @ks-cqc/h5-sig4-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@ks-cqc/h5-sig4 (npm) malicious package — MAL-2026-16524 | O3 Security