What does the delivery-ci-cli malware do?

On require of delivery-ci-cli, index.js loads _bootstrap.js which downloads a platform-specific native binary from string-split-obfuscated Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev), writes it to /var/tmp or %TEMP% under cover-story names such as.cache_ , dotnet_diag_ .exe, and.analytics_state, chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe with unref(). No hash or signature verification is performed. If HTTPS mirrors fail, _bootstrap.js falls back to a DNS-TXT covert channel: it queries TXT records at c. and 0. ..N. under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.we

Which versions of delivery-ci-cli are malicious?

The following npm versions of delivery-ci-cli are flagged malicious: 35.3.5. Treat any of these as compromised.

How do I remediate delivery-ci-cli if I installed it?

Remove delivery-ci-cli 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 delivery-ci-cli — how do I know if it already compromised me?

If delivery-ci-cli 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.

Is delivery-ci-cli part of a known attack campaign?

Yes — delivery-ci-cli is associated with the IN-MAL-2026-016992 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 delivery-ci-cli across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for delivery-ci-cli (version 35.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging delivery-ci-cli across your stack and pipelines.

Malicious package

delivery-ci-clinpm

delivery-ci-cli is a confirmed malicious npm package (MAL-2026-13538) that executes malicious code on install (malicious version 35.3.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in delivery-ci-cli (npm)

MAL-2026-13538

Immediate action

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

npm uninstall delivery-ci-cli

What this malware does

On require of delivery-ci-cli, index.js loads bootstrap.js which downloads a platform-specific native binary from string-split-obfuscated Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev), writes it to /var/tmp or %TEMP% under cover-story names such as.cache<hex>, dotnet_diag_<hex>.exe, and.analytics_state, chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe with unref(). No hash or signature verification is performed. If HTTPS mirrors fail, _bootstrap.js falls back to a DNS-TXT covert channel: it queries TXT records at c.<domain> and 0.<domain>..N.<domain> under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru, base64-decodes the concatenated response into a buffer, writes it to disk, and executes it. Hostnames and API names are assembled at runtime via array.join to evade static string matching. The package README presents it as a benign 'CI CLI SDK' with empty dependencies, which serves as cover for the dropper behavior.

Malicious versions

1 flagged

35.3.5

Indicators of compromise (SHA-256)

25daa792f30733f69d4530266b44c1b6ba9a5f4d11f47cce95b714792a39ca89

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for delivery-ci-cli (version 35.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging delivery-ci-cli across your stack and pipelines.
If you installed it — respond
Remove delivery-ci-cli 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-cli 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-cli 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

No. delivery-ci-cli on npm has been identified as a malicious package (version 35.3.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016992

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks delivery-ci-cli-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