registry / Remote code execution / external-process-live-log
external-process-live-log
TypeScript SDK for the Polymarket CLOB API.
This report shows the evidence for external-process-live-log@13.5.2, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a concrete remote-code-execution loader, not a benign network helper: untrusted network content is executed directly with Node capabilities. Lack of automatic invocation limits the trigger but does not remove the malicious capability.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
A consumer imports the package in an ESM-capable context and calls its default export.
Impact
The endpoint operator can run arbitrary code with the consuming process's privileges.
Mechanism
remote response code execution via Function constructor
Attack narrative
A caller invoking the exported getPlugin function causes a fetch to a hard-coded IP address. The response is parsed as JSON and its credits field becomes the body of a Function constructed with require, process, globalThis, timers, and working-directory information. An operator controlling that endpoint can therefore supply arbitrary Node.js code for execution in the caller's process. There is no lifecycle hook or import-time call, but the exported API itself is a remote payload loader.
AI rationale
This is a concrete remote-code-execution loader, not a benign network helper: untrusted network content is executed directly with Node capabilities. Lack of automatic invocation limits the trigger but does not remove the malicious capability.
Evidence
index.jspackage.json
Network endpoints1
31.97.137.157:45000/icons/107
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- Default export fetches a hard-coded IP endpoint when invoked.
- The JSON response field data.credits is passed directly to new Function.
- The fetched code executes with require, process, global, filesystem-relative paths, and timers.
- Manifest has no lifecycle hooks, so this is not install-time execution.
Evidence against
- Only getPlugin is exported; source does not invoke it during import.
- No package source writes files or harvests credentials before the remote payload runs.
Behavioral surface
EvalNetwork
Source & flagged code
5 flagged · loading sourceindex.jsView file
6L7: // Create require that resolves from the project root (where package.json and node_modules are)
L8: const projectRoot = resolve(dirname(fileURLToPath(import.meta.url)), '..');
...
L90:
L91: return fetch(url, { headers: head })
L92: .then(response => {
...
L95: }
L96: return response.json();
L97: });
...
L133: exports: {},
L134: __dirname: process.cwd(),
L135: __filename: import.meta.url,
Critical
Remote Response Code Execution
Source passes code obtained from a remote response into a dynamic execution sink.
index.jsView on unpkg · L6149// Note: The code uses async/await, so we need to handle that
L150: const evalFn = new Function(
L151: 'require', 'module', 'exports', '__dirname', '__filename', 'console', 'process', 'global', 'Buffer', 'setTimeout', 'setInterval', 'clearTimeout', 'clearInterval', 'Promise',
High
•matchType = malicious_source_fingerprint_signature
signature = c06bd55d669269cb
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = copytrade-core@2.3.0
matchedPath = index.js
matchedIdentity = npm:Y29weXRyYWRlLWNvcmU:2.3.0
similarity = 1.000
shingleOverlap = 1
summary = package final verdict is malicious
High
Findings
1 Critical4 High2 Medium1 Low
CriticalRemote Response Code Executionindex.js
HighEvalindex.js
HighKnown Malware Source Fingerprint Signatureindex.js
HighAi Review Evidenceindex.js
HighAi Review Evidenceindex.js
MediumNetwork
MediumStructural Risk Force Deep Review
LowScripts Present
Affected versions and remediation
This report applies to external-process-live-log@13.5.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing external-process-live-log@13.5.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.