registry / Remote code execution / bigops-telephony-client
bigops-telephony-client
Bigops telephony client SDK for internal consumers
This report shows the evidence for bigops-telephony-client@35.7.6. 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 remote executable loader is import-time behavior, not a user-invoked telephony feature, and it lacks payload validation. The absence of lifecycle hooks does not mitigate the executable payload chain.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any require/import of the main index.js entrypoint
Impact
Arbitrary native code execution under the importing process user.
Mechanism
Remote payload download, temporary-file drop, and detached execution
Attack narrative
The main entrypoint catches and suppresses errors while importing _runtime.js. That module immediately bootstraps, fetches a platform-specific binary from rotating hosts or DNS TXT records, saves it under a deceptive temporary name, chmods it on Unix, then starts it detached through /bin/sh or cmd.exe. This is an unconsented remote code-execution chain activated by ordinary package import.
AI rationale
The remote executable loader is import-time behavior, not a user-invoked telephony feature, and it lacks payload validation. The absence of lifecycle hooks does not mitigate the executable payload chain.
Evidence
package.jsonindex.js_runtime.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf100-416.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf103-070.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 _runtime.js on every package import.
- _runtime.js downloads platform binaries from obfuscated Workers hosts.
- _runtime.js can reconstruct a binary through DNS TXT records under wel1.ru.
- Downloaded bytes are written to a temp path, made executable, and launched detached via shell/cmd.
- No integrity or signature verification is performed before execution.
Evidence against
- package.json has no lifecycle scripts.
- The visible SDK API is minimal and does not require this runtime loader.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
3 flagged · loading source_runtime.jsView file
4const crypto = require("crypto");
L5: const https = require("https");
L6: const path = require("path");
...
L43: const CACHE_TTL = 23040;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: 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.
_runtime.jsView on unpkg · L44Trigger-reachable chain: manifest.main -> index.js -> _runtime.js
L4: const crypto = require("crypto");
L5: const https = require("https");
L6: const path = require("path");
...
L43: const CACHE_TTL = 23040;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: 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.
_runtime.jsView on unpkg · L4Findings
2 Critical1 High2 Medium1 Low
CriticalDownload Execute_runtime.js
CriticalTrigger Reachable Dangerous Capability_runtime.js
HighChild Process_runtime.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bigops-telephony-client@35.7.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-telephony-client@35.7.6. 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.