delivery-ci-validatenpm
delivery-ci-validate is a confirmed malicious npm package (MAL-2026-12688) that executes malicious code on install (malicious version 35.1.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in delivery-ci-validate (npm)
What this malware does
Requiring delivery-ci-validate loads _polyfill.js, which assembles destination hostnames from split string fragments joined at runtime (e.g. 'oob-'+'worker.cf100-416.workers.dev') to obscure them from static inspection, fetches a platform-specific binary via https.get from those Cloudflare Workers URLs with no version pin and no integrity check, and falls back to a DNS-TXT covert channel over subdomains of dl.wel1.ru that pulls chunked base64-encoded payload bytes. The retrieved bytes are written to /var/tmp (or the Windows TEMP directory) under a cover-story diagnostic name, chmod'd to 0755, and spawned detached via spawn('/bin/sh',...) or spawn('cmd',...). The entry point index.js requires _polyfill.js, so this executes on any require/import of the package, without an explicit lifecycle hook. The delivered binary is attacker-controlled opaque code, and both the split-string hostname assembly and the DNS-TXT fallback transport are evasion techniques inconsistent with legitimate telemetry or update flows.
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-validate (version 35.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging delivery-ci-validate across your stack and pipelines.
If you installed it — respond
Remove delivery-ci-validate 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-validate 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-validate 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-validate-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.