Which versions of delivery-ci-dpat are malicious?

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

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

delivery-ci-dpat establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

If delivery-ci-dpat 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-dpat part of a known attack campaign?

Yes — delivery-ci-dpat is associated with the IN-MAL-2026-016898 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-dpat 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-dpat (version 35.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging delivery-ci-dpat across your stack and pipelines.

Malicious package

delivery-ci-dpatnpm

delivery-ci-dpat is a confirmed malicious npm package (MAL-2026-13500) that opens a backdoor for remote access (malicious version 35.1.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in delivery-ci-dpat (npm)

MAL-2026-13500

Immediate action

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

npm uninstall delivery-ci-dpat

What this malware does

On require() of delivery-ci-dpat, _platform.js runs setup() at module load: it fetches a platform-specific binary over HTTPS from hardcoded Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev), writes it to a hidden path under /tmp or %TEMP%, chmods it 0o755, and spawns it detached via /bin/sh -c '<file> &' or cmd.exe /c start /b. A DNS-TXT covert channel provides a fallback delivery path: dnsChunked() queries c.<domain> under *.dl.wel1.ru for a chunk count, iterates 0..N.<domain> collecting base64-encoded TXT records, reassembles them into a binary buffer, and executes the reconstructed payload the same way. The C2 hostnames and DNS fallback domain are assembled at runtime from split-string fragments (['oob-worker.cf101-adf.worker','s.','dev'].join(''); ['sdk.dl.wel','1.r','u'].join('')) to evade static matching. A filesystem stamp is used for run-once dedup and the behavior is labeled as analytics/telemetry.

Malicious versions

1 flagged

35.1.5

Indicators of compromise (SHA-256)

dcb4f83185cbfb983d8d86e4419deb6b4dcdf74565d5f31ef316c73b34a7948f

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for delivery-ci-dpat (version 35.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging delivery-ci-dpat across your stack and pipelines.
If you installed it — respond
delivery-ci-dpat establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If delivery-ci-dpat 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-dpat 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-dpat on npm has been identified as a malicious package (version 35.1.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016898

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks delivery-ci-dpat-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database