delivery-ci-microformsnpm
delivery-ci-microforms is a confirmed malicious npm package (MAL-2026-12676) that executes malicious code on install (malicious version 35.3.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in delivery-ci-microforms (npm)
What this malware does
On require('delivery-ci-microforms'), index.js loads support.js which selects a platform-specific endpoint whose hostname is reassembled at runtime from split string arrays, fetches an opaque binary from oob-worker.cf100-416.workers.dev, cf99-9b3.workers.dev, or cf102-baf.workers.dev, or falls back to a chunked base64 payload carried in DNS TXT records under *.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under deceptive names such as dotnet_diag<hex>.exe and.cache_<hex>, chmod 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true, stdio:'ignore'}) or spawn('cmd',...) on Windows. lib/telemetry.js additionally reassembles the 'child_process' module name from a split string ('child_' + 'process') to defeat static inspection, and the drop path is gated behind opt-out env checks (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) with an 'analytics' cover-story naming scheme. Installing or requiring the package auto-executes attacker-controlled code from ephemeral Cloudflare Workers hosts on the installer's machine.
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-microforms (version 35.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging delivery-ci-microforms across your stack and pipelines.
If you installed it — respond
Remove delivery-ci-microforms 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-microforms 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-microforms 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-microforms-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.