registry / Remote code execution / bigops-alerts-widget
bigops-alerts-widget
embeddable widget
This report shows the evidence for bigops-alerts-widget@35.8.3. 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-triggered remote native payload execution chain unrelated to the advertised widget. The duplicate telemetry implementation corroborates the same downloader/launcher design.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Runtime require/import of bigops-alerts-widget
Impact
Arbitrary native code execution under the importing process user.
Mechanism
remote payload download, drop, chmod, and detached execution
Attack narrative
A normal require of index.js silently requires _vendor.js. Its async run routine fetches a platform-specific binary from rotating hard-coded hosts, or rebuilds one from DNS TXT records. It stores the bytes in a temp path, marks Unix files executable, and launches them via shell/cmd as a detached process. A stamp file throttles repeat execution.
AI rationale
This is a concrete, import-triggered remote native payload execution chain unrelated to the advertised widget. The duplicate telemetry implementation corroborates the same downloader/launcher design.
Evidence
package.jsonindex.js_vendor.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%\analytics_state%TEMP%\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf100-416.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf99-9b3.workers.devoob-worker.cf101-adf.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.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 on every package import.
- _vendor.js downloads platform payloads from four hard-coded worker hosts.
- _vendor.js reconstructs payload bytes from DNS TXT records as fallback.
- _vendor.js writes payloads to /var/tmp or TEMP, chmods them, and detached-spawns them.
- The runtime action is hidden behind a swallowed error and a ~6.5-hour stamp file.
Evidence against
- package.json has no lifecycle scripts.
- No credential harvesting or AI-agent control-surface mutation was found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading source_vendor.jsView file
6const crypto = require("crypto");
L7: const https = require("https");
L8:
...
L46: const CACHE_TTL = 23321;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
L59: const isWin = _p("platform") === "win32";
L60: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L61: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L93: try {
L94: require("dns").resolveTxt(d, (e, rr) => {
L95: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_vendor.jsView on unpkg · L66Trigger-reachable chain: manifest.main -> index.js -> _vendor.js
L6: const crypto = require("crypto");
L7: const https = require("https");
L8:
...
L46: const CACHE_TTL = 23321;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
L59: const isWin = _p("platform") === "win32";
L60: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L61: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L93: try {
L94: require("dns").resolveTxt(d, (e, rr) => {
L95: 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 · L6122
Findings
2 Critical2 High3 Medium2 Low
CriticalDownload Execute_vendor.js
CriticalTrigger Reachable Dangerous Capability_vendor.js
HighChild Process_vendor.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-alerts-widget@35.8.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-alerts-widget@35.8.3. 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.