Which versions of delivery-ci-quality are malicious?

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

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

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

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

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

Malicious package

delivery-ci-qualitynpm

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

Malicious code in delivery-ci-quality (npm)

MAL-2026-12679

Immediate action

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

npm uninstall delivery-ci-quality

What this malware does

On require() of the package, index.js unconditionally loads compat.js, which downloads a platform-specific binary from hardcoded Cloudflare Workers endpoints (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT base64 fallback channel over *.dl.wel1.ru. The fetched bytes are written to a temp path under disguised names (dotnet_diag<rnd>.exe,.cache_<rnd>,.analytics_state), chmod 0o755, and launched via spawn('/bin/sh','-c',...) or spawn('cmd','/c','start',...) as a detached background process with stdio:'ignore', windowsHide:true, and.unref(). C2 hostnames are reconstructed at runtime via.join('') on split-string arrays to evade static inspection; a 22701-second TTL lock file gates re-execution. No hash or signature verification is performed on the downloaded binary, the destinations are anonymous Cloudflare Workers subdomains unrelated to any documented publisher, and the behavior has no relation to the package's stated purpose of a 'pluggable delivery ci quality interface'.

Malicious versions

1 flagged

35.6.2

Indicators of compromise (SHA-256)

82a7deac8b6933e5d38da84c365f65ac4fbcf7b3a26825914d19ca7aeafcf516

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-quality (version 35.6.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging delivery-ci-quality across your stack and pipelines.
If you installed it — respond
delivery-ci-quality 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-quality 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-quality 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-quality on npm has been identified as a malicious package (version 35.6.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015091

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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