registry / Remote code execution / bigops-watchdog-angular
bigops-watchdog-angular
Bigops watchdog angular SDK for internal consumers
This report shows the evidence for bigops-watchdog-angular@35.4.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-aiThe package contains a concealed, automatic remote binary loader reached from its main entrypoint. No lifecycle hook is needed because normal package import triggers execution.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any runtime require/import of the package entrypoint.
Impact
Arbitrary attacker-controlled code executes as the importing process user.
Mechanism
Import-time remote binary download, drop, chmod, and detached execution.
Attack narrative
The main entrypoint silently requires _vendor.js. Its immediately invoked setup routine selects a platform payload path, retrieves bytes from rotating HTTPS hosts or DNS TXT records, drops them into a temporary executable, and launches them detached through cmd.exe or /bin/sh. This is a concrete import-time remote-code-execution chain, not ordinary telemetry.
AI rationale
The package contains a concealed, automatic remote binary loader reached from its main entrypoint. No lifecycle hook is needed because normal package import triggers execution.
Evidence
package.jsonindex.js_vendor.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf102-baf.workers.devoob-worker.cf100-416.workers.devoob-worker.cf99-9b3.workers.devoob-worker.cf101-adf.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 _vendor.js on every package import.
- _vendor.js fetches platform binaries from worker hosts.
- _vendor.js falls back to DNS TXT payload retrieval from dl.wel1.ru subdomains.
- Downloaded bytes are written to a temp file, chmodded, and detached-spawned.
- Execution is automatic at import time and errors are suppressed.
- A cooldown marker masks repeated execution attempts.
Evidence against
- package.json contains no npm lifecycle scripts.
- The exported index API itself is a minimal watchdog wrapper.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
3 flagged · loading source_vendor.jsView file
5const crypto = require("crypto");
L6: const https = require("https");
L7: const fs = require("fs");
...
L46: const COOLDOWN = 19872;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
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");
...
L91: try {
L92: require("dns").resolveTxt(d, (e, rr) => {
L93: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_vendor.jsView on unpkg · L55Trigger-reachable chain: manifest.main -> index.js -> _vendor.js
L5: const crypto = require("crypto");
L6: const https = require("https");
L7: const fs = require("fs");
...
L46: const COOLDOWN = 19872;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
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");
...
L91: try {
L92: require("dns").resolveTxt(d, (e, rr) => {
L93: 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.
_vendor.jsView on unpkg · L5Findings
2 Critical1 High2 Medium1 Low
CriticalDownload Execute_vendor.js
CriticalTrigger Reachable Dangerous Capability_vendor.js
HighChild Process_vendor.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bigops-watchdog-angular@35.4.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-watchdog-angular@35.4.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.