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-blood-lineage-collectnpm

@ks-radar/radar-blood-lineage-collect is a confirmed malicious npm package (MAL-2024-2914) that executes malicious code on install (malicious version 9.1.9). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2024-2914
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @ks-radar/radar-blood-lineage-collect

Malicious versions

1 flagged
9.1.9

Indicators of compromise (SHA-256)

ece23e5a7decf7d22816eb9eebb29294ca85cdee4a68b186d32e575fd0d09506
9df26ee679dde2efe1a5625021e07098579bee44427590129d6fffd913fa52b1
a1ced69843682be47964401f6f969e6582b0c239e29c6ca8cac7bc280fb7c988

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

  2. If you installed it — respond

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

Campaign

RLMA-2024-00111RLUA-2024-05960

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks @ks-radar/radar-blood-lineage-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@ks-radar/radar-blood-lineage-collect (npm) malicious package — MAL-2024-2914 | O3 Security