delivery-ci-upgrade-from (npm) · Malicious Code
Affects delivery-ci-upgrade-fromSource GCVE Database
Malicious package : remove delivery-ci-upgrade-from and rotate any secrets on hosts that installed it.
Data as of 6 Aug 2026, 18:24 UTC
Malicious package
Published to npm · OSV MAL-2026-12687
What to do
Remove delivery-ci-upgrade-from from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmdelivery-ci-upgrade-from | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (46b1b760480eca3b3ad596491193f7aa55ed0a3e982d6978c071e04e793ff8b0) index.js unconditionally requires _bridge.js, which runs a bootstrap routine on module load. The bootstrap selects a platform-specific path (linux_x64, linux_arm64, darwin, win32), fetches an unsigned binary from split-string-obfuscated Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev), with a base64-chunked DNS TXT covert channel fallback under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru and net.dl.wel1.ru. The retrieved bytes are written to /var/tmp/.cache_<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmod'd to 0755, and spawned detached via /bin/sh -c or cmd.exe /c start. Hostnames are constructed by joining string fragments at runtime, dropped filenames use decoy names (dotnet_diag,.cache_,.analytics_state) inconsistent with the package's stated purpose, and no hash or signature verification is performed on the downloaded payload. The destinations are unrelated to any publisher of this package. ## Source: ghsa-malware (75454f2a282eb740a7f1334cb94456d3fdedc39a065c89e3c8fe7f5fa6a3fcfd) 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.