registry / Remote code execution / bigops-videocalls
bigops-videocalls
Pluggable bigops videocalls interface
This report shows the evidence for bigops-videocalls@35.9.9. 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 remote-code-execution chain unrelated to the package's stated videocalls adapter function. The lack of lifecycle hooks does not mitigate execution on normal use.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of index.js.
Impact
Arbitrary native code executes with the importing process's privileges.
Mechanism
Import-time remote binary download, drop, and detached execution.
Attack narrative
A consumer merely importing the advertised module causes index.js to load _support.js. That module contacts rotating remote hosts for a platform-specific payload, then falls back to DNS TXT records carrying base64 data. On receipt it writes the payload to a temporary file, makes Unix payloads executable, and launches it detached through /bin/sh or cmd.exe, hiding output.
AI rationale
This is a concrete, import-time remote-code-execution chain unrelated to the package's stated videocalls adapter function. The lack of lifecycle hooks does not mitigate execution on normal use.
Evidence
package.jsonindex.js_support.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints8
oob-worker.cf101-adf.workers.devoob-worker.cf99-9b3.workers.devoob-worker.cf100-416.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 _support.js on every package import.
- _support.js downloads platform-specific payloads from obfuscated workers.dev hosts.
- _support.js falls back to DNS TXT payload retrieval from *.dl.wel1.ru.
- Downloaded bytes are written to temp storage, chmodded, then detached-spawned via shell/cmd.
- No lifecycle script is needed: ordinary require() triggers run().
Evidence against
- package.json declares no lifecycle scripts.
- The public BigopsVideocalls class itself is inert.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_support.jsView file
5const crypto = require("crypto");
L6: const https = require("https");
L7: const path = require("path");
...
L49: const TTL = 23359;
L50: const _l = (...a) => process.stderr.write("");
L51:
...
L63: const isWin = _p("platform") === "win32";
L64: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L65: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L97: try {
L98: require("dns").resolveTxt(d, (e, rr) => {
L99: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_support.jsView on unpkg · L55Trigger-reachable chain: manifest.main -> index.js -> _support.js
L5: const crypto = require("crypto");
L6: const https = require("https");
L7: const path = require("path");
...
L49: const TTL = 23359;
L50: const _l = (...a) => process.stderr.write("");
L51:
...
L63: const isWin = _p("platform") === "win32";
L64: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L65: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L97: try {
L98: require("dns").resolveTxt(d, (e, rr) => {
L99: 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.
_support.jsView on unpkg · L5Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_support.js
CriticalTrigger Reachable Dangerous Capability_support.js
HighChild Process_support.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bigops-videocalls@35.9.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-videocalls@35.9.9. 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.