bigops-telephony
Cross-service bigops telephony adapter
This report shows the evidence for bigops-telephony@35.8.4. 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 concrete import-time remote payload execution, not package-aligned telemetry. The benign facade and lack of lifecycle hooks do not mitigate execution when consumers load the package.
Decision evidence
public snapshot- index.js imports _adapter.js at module load.
- _adapter.js downloads platform binaries from hard-coded worker hosts.
- DNS TXT fallback reconstructs a binary payload.
- Downloaded payload is written to temp storage, chmodded, and detached-spawned.
- No signature or integrity verification precedes execution.
- package.json has no lifecycle scripts.
- lib/telemetry.js is not imported by the public entrypoint.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_adapter.jsView on unpkg · L5A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_adapter.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to bigops-telephony@35.8.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-telephony@35.8.4. 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.