delivery-ci-unitnpm
delivery-ci-unit is a confirmed malicious npm package (MAL-2026-12684) that executes malicious code on install (malicious version 35.9.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in delivery-ci-unit (npm)
What this malware does
On require of the package, index.js loads loader.js, which reconstructs attacker-controlled hostnames from split-string fragments (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, plus DNS TXT chunked-base64 fallbacks at sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), fetches a platform-specific binary over HTTPS, writes it to /tmp/.cache<hex> on Unix or TEMP\dotnet_diag_<hex>.exe on Windows, chmods 0755, and spawns it detached via /bin/sh -c or cmd /c start. No signature or hash verification is performed; filenames masquerade as system caches; a TTL marker rate-limits execution; environment-variable checks are used as evasion; and a DNS TXT covert channel serves as a fallback delivery path. The fetch host is reconstructed at runtime with no legitimate purpose, and the destinations are not the package's publisher.
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-unit (version 35.9.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging delivery-ci-unit across your stack and pipelines.
If you installed it — respond
Remove delivery-ci-unit 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-unit 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-unit 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-unit-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.