Which versions of delivery-ci-unit are malicious?

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

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

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.

I already installed delivery-ci-unit — how do I know if it already compromised me?

If delivery-ci-unit was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

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

Search your lockfiles and build artifacts for delivery-ci-unit (version 35.9.3).

Malicious package

delivery-ci-unitnpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

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)

MAL-2026-12684

Immediate action

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

npm uninstall delivery-ci-unit

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

1 flagged

35.9.3

Indicators of compromise (SHA-256)

69ab1e8e2553a7469b1ce9a50549b0f1cb964160096693715d10643a853eade4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for delivery-ci-unit (version 35.9.3).
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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-015094

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database