@ks-radar/radarnpm
@ks-radar/radar is a confirmed malicious npm package (MAL-2026-11066) that steals credentials and exfiltrates sensitive data (malicious versions 20.0.0, 21.0.0, 22.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @ks-radar/radar (npm)
What this malware does
On npm install, the package's preinstall lifecycle script (preinstall.js) reads a hex-encoded command string from preinstall.json, decodes it via Buffer.from(hexCommand, 'hex'), and passes the decoded string to child_process.exec. The decoded command invokes curl against https://eobdzec83knbura.m.pipedream.net and POSTs installer-side reconnaissance data including the output of whoami, the current working directory, the hostname, and the contents of /etc/passwd and /etc/hosts. The hex encoding of the command serves no legitimate build purpose and hides the exfiltration target and payload from casual inspection of package.json. The destination pipedream.net endpoint is an attacker-controlled request-collection URL, unrelated to any documented publisher infrastructure.
The OpenSSF Package Analysis project identified '@ks-radar/radar' @ 22.0.0 (npm) as malicious.
It is considered malicious because:
-
The package communicates with a domain associated with malicious activity.
-
The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ks-radar/radar (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ks-radar/radar across your stack and pipelines.
If you installed it — respond
@ks-radar/radar is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @ks-radar/radar 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.
How O3 protects you
O3 blocks @ks-radar/radar 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
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks @ks-radar/radar-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.