registry / Remote code execution / bigops-procedure-player
bigops-procedure-player
Bigops procedure player SDK for internal consumers
This report shows the evidence for bigops-procedure-player@35.8.2, 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 concrete import-time staged remote-code execution unrelated to the advertised minimal SDK. The source directly establishes payload retrieval, disk drop, and detached execution.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any require/import of index.js
Impact
Arbitrary native code execution under the importing process user.
Mechanism
Unauthenticated remote payload download, drop, chmod, and detached execution
Attack narrative
On import, index.js silently loads _loader.js. The loader fingerprints the platform, obtains a binary from hard-coded Workers hosts (with DNS TXT fallback), writes it to a temporary path, makes it executable on Unix, and launches it through a detached shell or cmd.exe process. It does not authenticate the downloaded bytes, so the remote operators control code executed on the victim machine.
AI rationale
This is concrete import-time staged remote-code execution unrelated to the advertised minimal SDK. The source directly establishes payload retrieval, disk drop, and detached execution.
Evidence
package.jsonindex.js_loader.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.cf102-baf.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packagesdk.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 unconditionally imports _loader.js on package import.
- _loader.js downloads platform-specific bytes from hard-coded worker hosts or DNS TXT records.
- _loader.js writes the payload to /var/tmp or Windows Temp, marks it executable, then launches it detached.
- Remote payload source is unauthenticated; no signature or hash verification is performed.
- A temporary stamp suppresses repeated execution, indicating stealthy runtime staging.
Evidence against
- package.json contains no lifecycle hooks.
- The exported SDK class itself is minimal; malicious behavior is in the import-time loader.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading source_loader.jsView file
5const path = require("path");
L6: const https = require("https");
L7: const os = require("os");
...
L45: const TTL = 21859;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
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");
...
L95: try {
L96: require("dns").resolveTxt(d, (e, rr) => {
L97: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_loader.jsView on unpkg · L55Trigger-reachable chain: manifest.main -> index.js -> _loader.js
L5: const path = require("path");
L6: const https = require("https");
L7: const os = require("os");
...
L45: const TTL = 21859;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
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");
...
L95: try {
L96: require("dns").resolveTxt(d, (e, rr) => {
L97: 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.
_loader.jsView on unpkg · L5Findings
2 Critical2 High3 Medium2 Low
CriticalDownload Execute_loader.js
CriticalTrigger Reachable Dangerous Capability_loader.js
HighChild Process_loader.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-procedure-player@35.8.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-procedure-player@35.8.2. 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.