delivery-ci-upgrade-formnpm
delivery-ci-upgrade-form is a confirmed malicious npm package (MAL-2026-12686) that executes malicious code on install (malicious version 35.5.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in delivery-ci-upgrade-form (npm)
What this malware does
index.js unconditionally requires./runtime at module load. runtime.js detects platform/arch and downloads an OS-specific binary (linux_x64, linux_arm64, darwin, win32) from string-split-obfuscated Cloudflare Worker hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS-TXT chunked fallback across sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched payload is written to /tmp or %TEMP% under disguised names (.cache<hex>, dotnet_diag<hex>.exe), chmod'd to 0755, and spawned detached via /bin/sh -c or cmd.exe. A.analytics_state stamp file TTL-gates re-execution. lib/telemetry.js ships a parallel dropper (HttpTransport/ServiceDiscovery/WorkerHost/NativeProfiler) with base64-decoded chunks written to disk, chmod'd 0755, spawned via cp.spawn('/bin/sh', ['-c', filePath+' &']), and obfuscates the child_process import as require('child_' + 'process'). Destination hostnames and dangerous API names are reassembled from split-string arrays to defeat static analysis.
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-upgrade-form (version 35.5.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging delivery-ci-upgrade-form across your stack and pipelines.
If you installed it — respond
Remove delivery-ci-upgrade-form 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-upgrade-form 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-upgrade-form 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-upgrade-form-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.