registry / Remote code execution / delivery-ci-upgrade-from

delivery-ci-upgrade-from

Delivery ci upgrade from provider for microservice architecture

This report shows the evidence for delivery-ci-upgrade-from@35.6.9. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.

This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.

AI Security Review

scanned 3mo ago · by lpm-firewall-ai

The package's import path directly activates an obfuscated remote binary downloader and executor. The absence of an install hook does not mitigate runtime compromise on normal import.

Static reason

High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review

Trigger

Any application require/import of the package main entrypoint.

Impact

Unconsented remote code execution under the importing user's privileges.

Mechanism

import-time remote binary download and detached execution

Attack narrative

The declared main, index.js, silently requires _bridge.js during import. Its bootstrap downloads a platform-specific binary over HTTPS from rotating hosts, or reconstructs one from DNS TXT records, writes it to temporary storage, makes it executable on Unix, and launches it detached through a shell or cmd.exe. This is a concrete remote payload execution chain.

AI rationale

The package's import path directly activates an obfuscated remote binary downloader and executor. The absence of an install hook does not mitigate runtime compromise on normal import.

Evidence

package.jsonindex.js_bridge.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>

Network endpoints7

oob-worker.cf102-baf.workers.devoob-worker.cf100-416.workers.devoob-worker.cf103-070.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.dl.wel1.runet.dl.wel1.ru

Decision evidence

public snapshot

AI called this Malicious at 99.0% confidence as Malware with low false-positive risk.

Evidence for block

index.js imports _bridge.js at module load.
_bridge.js downloads platform binaries from workers.dev hosts.
_bridge.js falls back to DNS TXT payload retrieval from dl.wel1.ru.
Downloaded bytes are written to /var/tmp or Windows Temp, chmodded, then spawned detached.
No lifecycle hook is needed: importing the declared main triggers bootstrap.

Evidence against

package.json declares no lifecycle scripts.
lib/telemetry.js is not referenced by the public entrypoint.

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetwork

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 84.4 KB of source

Source & flagged code

5 flagged

lib/telemetry.jsView file

27L28: const https = require("https"); L29: const dns = require("dns"); L30: const fs = require("fs"); ... L116: const _logger = new Logger( L117: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE L118: ); ... L224: "BUILD_NUMBER", L225: "GITHUB_ACTIONS", L226: "GITLAB_CI", ... L275: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(), L276: device_app_hash: hashString(process.cwd()),

Critical

Download Execute

Source downloads or fetches remote code and executes it.

lib/telemetry.jsView on unpkg · L27

494L495: fork() { L496: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L494

•matchType = normalized_sha256 matchedPackage = claims-claims-api-adapters@35.7.9 matchedPath = lib/telemetry.js matchedIdentity = npm:[redacted]:35.7.9 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

lib/telemetry.jsView on unpkg

Low

Weak Crypto

Package source references weak cryptographic algorithms.

lib/telemetry.jsView on unpkg · L27

_bridge.jsView file

5Trigger-reachable chain: manifest.main -> index.js -> _bridge.js L5: const fs = require("fs"); L6: const https = require("https"); L7: const crypto = require("crypto"); ... L42: const EXPIRE_SEC = 23314; L43: const _l = (...a) => process.stderr.write(""); L44: ... L55: const isWin = _p("platform") === "win32"; L56: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp"; L57: return path.join(dir, isWin ? "analytics_state" : ".analytics_state"); ... L87: try { L88: require("dns").resolveTxt(d, (e, rr) => { L89: if (e || !rr || !rr.length) return r("");

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

_bridge.jsView on unpkg · L5

Source & flagged code

5 flagged · loading source

lib/telemetry.jsView file

Critical

Download Execute

Source downloads or fetches remote code and executes it.

lib/telemetry.jsView on unpkg · L27

494L495: fork() { L496: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L494

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

lib/telemetry.js

Findings

2 Critical2 High2 Medium2 Low

CriticalDownload Executelib/telemetry.js

CriticalTrigger Reachable Dangerous Capability_bridge.js

HighChild Processlib/telemetry.js

HighKnown Malware Source Similaritylib/telemetry.js

MediumNetwork

MediumEnvironment Vars

LowWeak Cryptolib/telemetry.js

LowFilesystem

Affected versions and remediation

This report applies to delivery-ci-upgrade-from@35.6.9.

The versions list below shows the verdict for each recorded version.

Avoid installing delivery-ci-upgrade-from@35.6.9. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.

Evidence last updated: 2026-08-05 13:32:41.611Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

2 known versions

0.0.1-securitylatestClean—AllowPublishedAug 5, 2026, 2:57 PM 35.6.9shownMaliciousRemote Code ExecutionBlockPublishedAug 5, 2026, 1:29 PM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other remote code execution packages

Source & flagged code

Related packages

Other remote code execution packages