registry / Remote code execution / bigops-microfrontend
bigops-microfrontend
Reusable bigops microfrontend components
This report shows the evidence for bigops-microfrontend@35.4.1, the only known version.
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-triggered remote payload execution chain rather than ordinary telemetry. The lack of an npm lifecycle hook does not mitigate execution on normal package use.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any runtime require or import of the package entrypoint.
Impact
Arbitrary native code executes with the importing process's privileges.
Mechanism
remote binary download, temp-file drop, and detached shell execution
Attack narrative
The declared entrypoint loads _shim.js automatically. The shim selects a platform payload, downloads it from rotating worker hosts, and falls back to DNS TXT reconstruction. It writes the received bytes to a temporary executable path, marks non-Windows files executable, and starts them detached through cmd.exe or /bin/sh. No integrity or signature verification is performed.
AI rationale
This is a concrete, import-triggered remote payload execution chain rather than ordinary telemetry. The lack of an npm lifecycle hook does not mitigate execution on normal package use.
Evidence
package.jsonindex.js_shim.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints8
oob-worker.cf99-9b3.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf103-070.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.dl.wel1.runet.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 _shim on every package import.
- _shim.js downloads platform binaries over HTTPS or DNS TXT.
- _shim.js writes the payload to temp storage, chmods it, and launches it detached.
- Remote hosts and DNS fallback are obfuscated with split strings.
Evidence against
- package.json contains no lifecycle scripts.
- The shim honors telemetry opt-out environment variables.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
3 flagged · loading source_shim.jsView file
2L3: const https = require("https");
L4: const os = require("os");
...
L47: const STAMP_TTL = 21171;
L48: const _l = (...a) => process.stderr.write("");
L49:
...
L60: const isWin = _p("platform") === "win32";
L61: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L62: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L94: try {
L95: require("dns").resolveTxt(d, (e, rr) => {
L96: if (e || !rr || !rr.length) return r("");
Critical
2Trigger-reachable chain: manifest.main -> index.js -> _shim.js
L2:
L3: const https = require("https");
L4: const os = require("os");
...
L47: const STAMP_TTL = 21171;
L48: const _l = (...a) => process.stderr.write("");
L49:
...
L60: const isWin = _p("platform") === "win32";
L61: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L62: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L94: try {
L95: require("dns").resolveTxt(d, (e, rr) => {
L96: 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.
_shim.jsView on unpkg · L2122try {
L123: const cp = require("child_process");
L124: if (isWin) {
Findings
2 Critical1 High2 Medium1 Low
CriticalDownload Execute_shim.js
CriticalTrigger Reachable Dangerous Capability_shim.js
HighChild Process_shim.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bigops-microfrontend@35.4.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-microfrontend@35.4.1. 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.