registry / Remote code execution / bigops-tcrm-permissions
bigops-tcrm-permissions
This report shows the evidence for bigops-tcrm-permissions@35.6.1. 2 of 2 known versions are blocked or flagged. 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 malicious loader is directly reachable from the declared main entrypoint without a lifecycle hook or user opt-in. Its download-and-execute chain is concrete and unrelated to the advertised SDK.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Any runtime require/import of the package's main entrypoint.
Impact
Arbitrary attacker-supplied native code executes under the importing process's user.
Mechanism
Remote binary download, disk drop, chmod, and detached process execution.
Attack narrative
Requiring index.js silently loads _runtime.js. Its init routine checks a temp stamp, downloads a platform-specific binary from rotating HTTPS hosts or reconstructs one from DNS TXT records, writes it to a temporary path, marks it executable on Unix, and launches it through a detached shell or cmd.exe process. Failures are suppressed.
AI rationale
The malicious loader is directly reachable from the declared main entrypoint without a lifecycle hook or user opt-in. Its download-and-execute chain is concrete and unrelated to the advertised SDK.
Evidence
package.jsonindex.js_runtime.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf102-baf.workers.dev/pkg/packagesdk.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 ./_runtime on every package import.
- _runtime.js downloads platform binaries over HTTPS or DNS TXT.
- _runtime.js writes, chmods, and detached-spawns the downloaded binary.
- Payload hosts are obfuscated and unrelated to the stated permissions SDK.
- A temp-file stamp throttles repeated execution.
Evidence against
- package.json has no lifecycle scripts.
- No credential harvesting or exfiltration was found in the entrypoint chain.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
6 flagged · loading source_runtime.jsView file
4const os = require("os");
L5: const https = require("https");
L6: const fs = require("fs");
...
L45: const STAMP_TTL = 20878;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
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");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: 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 os = require("os");
L5: const https = require("https");
L6: const fs = require("fs");
...
L45: const STAMP_TTL = 20878;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
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");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: 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 Critical4 High2 Medium1 Low
CriticalDownload Execute_runtime.js
CriticalTrigger Reachable Dangerous Capability_runtime.js
HighChild Process_runtime.js
HighKnown Malware Source Similaritylib/telemetry.js
HighKnown Malware Source Similarity_runtime.js
HighKnown Malware Source Fingerprint Signaturelib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bigops-tcrm-permissions@35.6.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-tcrm-permissions@35.6.1. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.