registry / Remote code execution / bigops-storio-ngrx
bigops-storio-ngrx
Shared bigops storio ngrx library for backend integration
This report shows the evidence for bigops-storio-ngrx@35.2.2. 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-aiThis is a concrete import-time staged payload downloader and executor, not package-aligned telemetry. The analogous native-extension loader in lib/telemetry.js reinforces the intended remote execution chain.
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 remote code executes with the importing process's privileges.
Mechanism
import-time remote binary download, DNS fallback, and detached execution
Attack narrative
The main entrypoint silently requires _ext.js. Its immediately invoked setup routine fetches a payload from obfuscated external hosts, with DNS TXT records as a fallback. If the payload exceeds a size threshold, it writes it to a temporary executable path, applies execute permission on Unix, and launches it detached through a shell or cmd.exe. The loader suppresses errors and logs, and uses a timestamp file to reduce repeated activity.
AI rationale
This is a concrete import-time staged payload downloader and executor, not package-aligned telemetry. The analogous native-extension loader in lib/telemetry.js reinforces the intended remote execution chain.
Evidence
package.jsonindex.js_ext.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf101-adf.workers.devoob-worker.cf100-416.workers.devoob-worker.cf102-baf.workers.devsdk.dl.wel1.ruext.dl.wel1.ru
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _ext.js on every package import.
- _ext.js downloads platform payloads over HTTPS and DNS TXT fallback.
- _ext.js writes payloads to temp storage, chmods them, then detached-spawns them.
- Payload hosts are obfuscated worker domains; DNS fallback uses wel1.ru domains.
- No lifecycle hook is needed: import-time setup() triggers execution.
Evidence against
- package.json has no lifecycle scripts.
- The public API in index.js is otherwise minimal.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading source_ext.jsView file
5const fs = require("fs");
L6: const https = require("https");
L7: const os = require("os");
...
L45: const CACHE_TTL = 21781;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L57: const isWin = _p("platform") === "win32";
L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L59: 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
5Trigger-reachable chain: manifest.main -> index.js -> _ext.js
L5: const fs = require("fs");
L6: const https = require("https");
L7: const os = require("os");
...
L45: const CACHE_TTL = 21781;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L57: const isWin = _p("platform") === "win32";
L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L59: 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.
_ext.jsView on unpkg · L5119try {
L120: const cp = require("child_process");
L121: if (isWin) {
Findings
2 Critical2 High3 Medium2 Low
CriticalDownload Execute_ext.js
CriticalTrigger Reachable Dangerous Capability_ext.js
HighChild Process_ext.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to bigops-storio-ngrx@35.2.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-storio-ngrx@35.2.2. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.