Which versions of @ks-radar/radar-component-collect are malicious?

The following npm versions of @ks-radar/radar-component-collect are flagged malicious: 9.1.10. Treat any of these as compromised.

How do I remediate @ks-radar/radar-component-collect if I installed it?

Remove @ks-radar/radar-component-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.

I already installed @ks-radar/radar-component-collect — how do I know if it already compromised me?

If @ks-radar/radar-component-collect 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.

Is @ks-radar/radar-component-collect part of a known attack campaign?

Yes — @ks-radar/radar-component-collect is associated with the RLMA-2024-00112, RLUA-2024-05961 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @ks-radar/radar-component-collect across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @ks-radar/radar-component-collect (version 9.1.10).

Part of a larger attack: @ks-radar published 13 malicious packages. See the full campaign →

Malicious package

@ks-radar/radar-component-collectnpm

Advisory published Jun 25, 2024Updated Oct 24, 2024

@ks-radar/radar-component-collect is a confirmed malicious npm package (MAL-2024-2915) 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-component-collect (npm)

MAL-2024-2915

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @ks-radar/radar-component-collect

Malicious versions

1 flagged

9.1.10

Indicators of compromise (SHA-256)

c58e389dfde5ad2b61c911ab92e448951f2d9bcceab452ebc84ffa9d938d25b4

0548fcc98c2cdbbfbea47624c699452725453d6c47fb210cad10a9e792a2e983

0a67f8cd81a6599fa3081ab4645684015c69d524f10c35f0291a053704700587

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @ks-radar/radar-component-collect (version 9.1.10).
If you installed it — respond
Remove @ks-radar/radar-component-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.
Did it already run?
If @ks-radar/radar-component-collect 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-radar/radar-component-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

RLMA-2024-00112RLUA-2024-05961

Credits

ReversingLabs · finder

Detect & block this

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