Malicious code in delivery-ci-sage (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (4b54c7175e494e683cdbc63814267aa5544f88d0373b929b9f0fe3fcb8202bd3) 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. ## Source: ghsa-malware (135914b0e51c8aacf675ddb6fb98037d996d1296a52b77092267cf60e7b05520) 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.
AI Analysis
Technical Summary
The delivery-ci-sage npm package version 35.6.3 includes malicious functionality where, upon require(), it loads a loader script that constructs obfuscated hostnames to fetch a binary payload from anonymous, mutable hosts unrelated to the package's stated purpose. The binary is saved to system temporary directories with filenames mimicking legitimate .NET or system diagnostic tools, given executable permissions, and executed detached via shell or command prompt. No hash or signature verification is performed on the downloaded binary. The code uses environment variables related to telemetry to gate execution and drops a '.analytics_state' file as a cover story. This behavior indicates a supply chain compromise or deliberate inclusion of malware in the package.
Potential Impact
This malicious code can lead to arbitrary code execution on systems that install and require the affected package version, potentially allowing attackers to run unauthorized binaries with the privileges of the Node.js process. The lack of integrity checks and use of anonymous external hosts increases the risk of further payload manipulation or updates by attackers. The impersonation of legitimate system files and telemetry evasion techniques complicate detection and forensic analysis.
Mitigation Recommendations
No official patch or remediation is currently documented for this issue. Users should avoid using delivery-ci-sage version 35.6.3. It is recommended to audit dependencies for this package and remove or replace it with a trusted alternative. Monitor for updates from the package maintainer or security advisories for any official fixes. Until a fix is available, do not install or require this package version in any environment.
Malicious code in delivery-ci-sage (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (4b54c7175e494e683cdbc63814267aa5544f88d0373b929b9f0fe3fcb8202bd3) 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. ## Source: ghsa-malware (135914b0e51c8aacf675ddb6fb98037d996d1296a52b77092267cf60e7b05520) 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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The delivery-ci-sage npm package version 35.6.3 includes malicious functionality where, upon require(), it loads a loader script that constructs obfuscated hostnames to fetch a binary payload from anonymous, mutable hosts unrelated to the package's stated purpose. The binary is saved to system temporary directories with filenames mimicking legitimate .NET or system diagnostic tools, given executable permissions, and executed detached via shell or command prompt. No hash or signature verification is performed on the downloaded binary. The code uses environment variables related to telemetry to gate execution and drops a '.analytics_state' file as a cover story. This behavior indicates a supply chain compromise or deliberate inclusion of malware in the package.
Potential Impact
This malicious code can lead to arbitrary code execution on systems that install and require the affected package version, potentially allowing attackers to run unauthorized binaries with the privileges of the Node.js process. The lack of integrity checks and use of anonymous external hosts increases the risk of further payload manipulation or updates by attackers. The impersonation of legitimate system files and telemetry evasion techniques complicate detection and forensic analysis.
Mitigation Recommendations
No official patch or remediation is currently documented for this issue. Users should avoid using delivery-ci-sage version 35.6.3. It is recommended to audit dependencies for this package and remove or replace it with a trusted alternative. Monitor for updates from the package maintainer or security advisories for any official fixes. Until a fix is available, do not install or require this package version in any environment.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12680
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a735737bf8831d539145caa
Added to database: 08/05/2026, 15:31:03 UTC
Last enriched: 08/05/2026, 16:25:24 UTC
Last updated: 09/15/2026, 19:20:03 UTC
Views: 17
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.