ragacateslikodinpm
ragacateslikodi is a confirmed malicious npm package (MAL-2026-16252) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ragacateslikodi (npm)
What this malware does
On require/import of the package's main entry, a top-level async IIFE probes http://localhost:5000 for a hardcoded set of paths (/admin, /flag, /profile variants), concatenates status, length, and any body content matching flag patterns from those responses, and POSTs the aggregated result to a hardcoded webhook.site endpoint (https://webhook.site/1895d1d5-b227-4ce4-a2ce-232b1bec8b65). Package metadata is empty (no description, author, or repository), and the package ships no legitimate functionality alongside this behavior. Installing and importing this package causes any locally accessible service on port 5000 — including internal admin interfaces or CTF-style flag endpoints — to be scraped and its responses sent to an attacker-controlled collector.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ragacateslikodi (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ragacateslikodi across your stack and pipelines.
If you installed it — respond
Remove ragacateslikodi 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 ragacateslikodi 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 ragacateslikodi 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
Detect & block this
O3 blocks ragacateslikodi-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.