bigops-procedure-file-handlers
Bigops procedure file handlers abstraction layer
This report shows the evidence for bigops-procedure-file-handlers@35.7.6, the only known version.
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 concealed import-time downloader and launcher unrelated to the advertised abstraction library. The absence of an npm lifecycle hook does not mitigate the concrete remote-code-execution path.
Decision evidence
public snapshot- index.js imports _runtime.js on every package import.
- _runtime.js downloads a platform payload over HTTPS or DNS TXT.
- _runtime.js writes the payload to /var/tmp or Windows Temp and makes Unix payloads executable.
- _runtime.js starts the downloaded file detached through /bin/sh or cmd.exe.
- Remote hosts are obfuscated by string concatenation and execution errors are suppressed.
- package.json has no lifecycle scripts.
- No credential collection or exfiltration was found in the import path.
Source & flagged code
3 flagged · loading sourceSource downloads or fetches remote code and executes it.
_runtime.jsView on unpkg · L2A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_runtime.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to bigops-procedure-file-handlers@35.7.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-procedure-file-handlers@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.