delivery-ci-sagenpm
Advisory published Updated
delivery-ci-sage is a confirmed malicious npm package (MAL-2026-12680) that steals credentials and exfiltrates sensitive data (malicious version 35.6.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in delivery-ci-sage (npm)
What this malware does
On require() of the package, index.js loads _loader.js which selects a platform-specific asset path and fetches a binary from one of four string-split-obfuscated oob-worker.cf*.workers.dev hostnames (with a DNS TXT chunked-base64 fallback via *.dl.wel1.ru). The fetched bytes are written to /var/tmp/.cache_<hex> (POSIX) or %TEMP%\dotnet_diag_<hex>.exe (Windows), chmod 0755'd, and spawned detached via spawn('/bin/sh',...) or spawn('cmd',...). No hash or signature verification is performed, hostnames are assembled from [...].join('') fragments to evade static inspection, and the code is gated by DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK env vars while dropping a .analytics_state flag file as a telemetry cover story. Filenames impersonate legitimate.NET/system artifacts (dotnet_diag_, dot-prefixed cache). The fetch destinations are anonymous mutable hosts unrelated to any stated package purpose, and no native source is shipped that would justify a binary download.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for delivery-ci-sage (version 35.6.3).
If you installed it — respond
delivery-ci-sage is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If delivery-ci-sage was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks delivery-ci-sage-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.