registry / Remote code execution / bigops-storio-store-adapter

bigops-storio-store-adapter

state container

This report shows the evidence for bigops-storio-store-adapter@35.9.8. 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 source establishes a reachable, import-time download-and-execute path with attacker-controlled remote payload bytes. Lack of an install hook does not mitigate runtime execution when consumers import the package.

Static reason

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

Trigger

Any runtime require/import of the package entrypoint.

Impact

Arbitrary attacker-controlled native code can run with the importing process's privileges.

Mechanism

remote payload download, temporary-file drop, permission change, and detached process execution

Attack narrative

The normal module entrypoint silently requires _bridge.js. On import, it selects platform-specific endpoints, downloads a binary from hard-coded HTTPS mirrors or reconstructs one from DNS TXT records, writes it to a temporary directory, marks it executable on Unix, and launches it detached through a shell or cmd.exe. This is an unconsented remote-code-execution chain; the similarly structured telemetry module corroborates the capability.

AI rationale

Evidence

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

Network endpoints7

oob-worker.cf99-9b3.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf103-070.workers.devsdk.dl.wel1.ruext.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 on every package import.
_bridge.js downloads platform binaries over HTTPS.
DNS TXT records can supply a base64 fallback payload.
Downloaded data is written under /var/tmp or Windows Temp, chmodded, and spawned detached.
Hosts and DNS domains are split into strings to obscure them.
lib/telemetry.js contains the same download-to-execute primitive.

Evidence against

package.json has no npm lifecycle scripts.
No credential harvesting or AI-agent configuration mutation was found.

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetwork

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 84.9 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

490L491: fork() { L492: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L490

•matchType = normalized_sha256 matchedPackage = devplatform-hooks@35.2.1 matchedPath = lib/telemetry.js matchedIdentity = npm:ZGV2cGxhdGZvcm0taG9va3M:35.2.1 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

3Trigger-reachable chain: manifest.main -> index.js -> _bridge.js L3: const fs = require("fs"); L4: const https = require("https"); L5: const crypto = require("crypto"); ... L45: const STAMP_TTL = 22818; L46: const _l = (...a) => process.stderr.write(""); L47: ... L58: const isWin = _p("platform") === "win32"; L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp"; L60: return path.join(dir, isWin ? "analytics_state" : ".analytics_state"); ... L90: try { L91: require("dns").resolveTxt(d, (e, rr) => { L92: 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 · L3

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

490L491: fork() { L492: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L490

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 bigops-storio-store-adapter@35.9.8.

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

Avoid installing bigops-storio-store-adapter@35.9.8. 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 16:39:55.853Z (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, 6:36 PM 35.9.8shownMaliciousRemote Code ExecutionBlockPublishedAug 5, 2026, 2:05 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

Related packages

Other remote code execution packages

Source & flagged code