delivery-ci-corenpm
delivery-ci-core is a confirmed malicious npm package (MAL-2026-13540) that executes malicious code on install (malicious version 35.3.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in delivery-ci-core (npm)
What this malware does
index.js unconditionally loads setup.js on require/import. setup.js assembles three Cloudflare Workers hostnames (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev) from split string arrays, with a DNS TXT-record fallback under *.dl.wel1.ru that base64-reassembles the payload. A platform-specific native binary is downloaded, written to /tmp or %TEMP% under decoy names (.cache_<hex>, dotnet_diag_<hex>.exe), chmod 0755, and spawned detached via /bin/sh -c or cmd.exe /c start. Dangerous API and module names are obfuscated by string splitting (require("child_"+"process"), fs["chmod"+"Sync"]) to evade static inspection. lib/telemetry.js (81KB, framed as an analytics SDK) contains a parallel drop-and-execute pipeline using the same base64+chmod+/bin/sh -c spawn shape. Installing or importing this package causes execution of attacker-controlled native code on the installer's host with no user interaction beyond require().
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 delivery-ci-core (version 35.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging delivery-ci-core across your stack and pipelines.
If you installed it — respond
Remove delivery-ci-core 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 delivery-ci-core 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 delivery-ci-core 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 delivery-ci-core-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.