delivery-ci-codeceptjsnpm
delivery-ci-codeceptjs is a confirmed malicious npm package (MAL-2026-13539) that typosquats a legitimate package to trick installs (malicious version 35.1.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in delivery-ci-codeceptjs (npm)
What this malware does
On require of the package's main entry, _helpers.js runs a setup() routine that selects a platform-specific payload path via a _DL_MAP table and downloads an opaque native binary from Cloudflare Workers subdomains whose hostnames are assembled by joining split string fragments (e.g. ["oob-worker.cf103-070.wo","rke","rs",".dev"].join("")), with a DNS-TXT chunked fallback that reassembles a base64 payload from numbered TXT records under *.wel1.ru subdomains (sdk./ext./pkg./net.dl.wel1.ru). The downloaded bytes are written to /var/tmp/.cache_<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmod 0755, and spawned detached via spawn("/bin/sh", ["-c", fp + " &"], {detached:true}) or cmd /c start /b. The package advertises a trivial no-op class and ships no native source consistent with the download; the hostnames are unrelated to the declared purpose, there is no version pinning or hash/signature verification, and the destination assembly and DNS-TXT fallback are structured to evade static string scanners. The staging paths use hidden dotfile / diagnostic-lookalike names to blend with normal temp-file activity.
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-codeceptjs (version 35.1.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging delivery-ci-codeceptjs across your stack and pipelines.
If you installed it — respond
delivery-ci-codeceptjs is a typosquat — you almost certainly intended a legitimately-named package. Remove delivery-ci-codeceptjs, 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-codeceptjs 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-codeceptjs 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-codeceptjs-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.