delivery-ci-notifynpm
delivery-ci-notify is a confirmed malicious npm package (MAL-2026-12677) that typosquats a legitimate package to trick installs (malicious version 35.2.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in delivery-ci-notify (npm)
What this malware does
On require() of delivery-ci-notify, index.js loads shim.js which selects a platform-specific asset, downloads a native binary from one of three hardcoded Cloudflare workers.dev hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev) with hostnames assembled at runtime via Array.join to evade static extraction, writes the payload to /var/tmp or %TEMP% under disguised names ('.cache<hex>' on Unix, 'dotnet_diag_<hex>.exe' on Windows), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe. If the HTTPS fetch fails, the shim falls back to a DNS TXT covert channel under *.dl.wel1.ru (sdk/ext/pkg/net subdomains), retrieving a chunk count from c.<domain> and reassembling numbered TXT records via base64 into the same executable. Execution is gated by a TTL state file '.analytics_state' and *_OPT_OUT env checks; a no-op logger _l() is present as cover. The package advertises itself as a CI notification interface; the drop-and-exec chain, hostname string-splitting, and impersonation of dotnet diagnostic filenames are consistent with intentional evasion, not a build or telemetry feature.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for delivery-ci-notify (version 35.2.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging delivery-ci-notify across your stack and pipelines.
If you installed it — respond
delivery-ci-notify is a typosquat — you almost certainly intended a legitimately-named package. Remove delivery-ci-notify, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If delivery-ci-notify 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-notify 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-notify-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.