Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @ks-radar published 13 malicious packages. See the full campaign →
Malicious package

@ks-radar/radar-error-collectnpm

@ks-radar/radar-error-collect is a confirmed malicious npm package (MAL-2023-8057) that executes malicious code on install (malicious version 9.1.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ks-radar/radar-error-collect (npm)

MAL-2023-8057
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @ks-radar/radar-error-collect

What this malware does

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

1 flagged
9.1.10

Indicators of compromise (SHA-256)

2a7e2199870f46f65ae301b77a8853c7c0203492bd65638277944190b9b406d0
faad577b12fc35c5c09875f8dc1b8eb41657bde51da3f5c5cddc8ceaaff4671d
8a9b6c83c4e8229aee4bdaaef56cac9f89bda90898909785a196d3dcde376221

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 @ks-radar/radar-error-collect (version 9.1.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ks-radar/radar-error-collect across your stack and pipelines.

  2. If you installed it — respond

    Remove @ks-radar/radar-error-collect 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-radar/radar-error-collect 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 @ks-radar/radar-error-collect 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. @ks-radar/radar-error-collect on npm has been identified as a malicious package (version 9.1.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vw3v-52fj-6p2gRLMA-2024-00114

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks @ks-radar/radar-error-collect-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

@ks-radar/radar-error-collect (npm) malicious package — MAL-2023-8057 | O3 Security