registry / Remote code execution / prediction-trader
prediction-trader
Core trading utilities for automated prediction-market bots.
This report shows the evidence for prediction-trader@2.3.0, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe exported runtime behavior is an unauthenticated remote payload loader and executor, unrelated to the stated trading utility purpose. Lack of lifecycle hooks limits activation to API use but does not remove the concrete RCE behavior.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Consumer invokes the default-exported getPlugin function.
Impact
Remote operator can execute arbitrary JavaScript in the consuming process.
Mechanism
Remote response code execution through Function.
Attack narrative
A consumer calling the package’s default export causes a request to a hard-coded IP endpoint. The package parses the JSON response and supplies its credits field to the Function constructor, then invokes the result with require, process, global, Buffer, and path context. This lets the endpoint operator run arbitrary code with the consumer process’s permissions.
AI rationale
The exported runtime behavior is an unauthenticated remote payload loader and executor, unrelated to the stated trading utility purpose. Lack of lifecycle hooks limits activation to API use but does not remove the concrete RCE behavior.
Evidence
package.jsonindex.js
Network endpoints1
31.97.137.157:45000/icons/108
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- Default API targets a fixed remote IP endpoint.
- Remote JSON response is passed directly to Function.
- Executed payload receives require, process, global, and filesystem path context.
- The remote-code loader is the package’s default export.
Evidence against
- package.json has no preinstall, install, or postinstall hook.
- Import defines the loader but does not invoke it immediately.
- No first-party credential harvesting or file writes are present in the inspected files.
Behavioral surface
EvalNetwork
Source & flagged code
8 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 = velora-kit@12.1.2
matchedPath = index.js
matchedIdentity = npm:dmVsb3JhLWtpdA:12.1.2
similarity = 1.000
shingleOverlap = 1
summary = package final verdict is malicious
High
Findings
1 Critical7 High2 Medium1 Low
CriticalRemote Response Code Executionindex.js
HighEvalindex.js
HighKnown Malware Source Fingerprint Signatureindex.js
HighAi Review Evidenceindex.js
HighAi Review Evidenceindex.js
HighAi Review Evidenceindex.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 prediction-trader@2.3.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing prediction-trader@2.3.0. 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.