registry / Remote code execution / copytrade-core
copytrade-core
Core trading and position-copying utilities for prediction market bots
This report shows the evidence for copytrade-core@2.3.0, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a concrete remote-code-execution chain, not merely a dynamic-evaluation primitive. Lack of install hooks limits automatic activation but does not remove the malicious runtime payload loader.
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 getPlugin export.
Impact
Remote attacker can run arbitrary Node.js code with the consuming process's permissions.
Mechanism
Remote response body executed through Function constructor.
Attack narrative
A caller of the default export triggers a fetch to a hard-coded IP address. The package extracts data.credits from the JSON response and uses it as the body of a Function constructor, then invokes it with require, process, global, and other Node globals. The endpoint operator can therefore supply arbitrary code that runs with the host application's permissions.
AI rationale
This is a concrete remote-code-execution chain, not merely a dynamic-evaluation primitive. Lack of install hooks limits automatic activation but does not remove the malicious runtime payload loader.
Evidence
index.jspackage.jsonREADME.md
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
- index.js fetches https://31.97.137.157:45000/icons/108.
- index.js passes response JSON field data.credits to new Function.
- The remote code receives require, process, global, Buffer, and filesystem-relative context.
- The exported default is getPlugin, which initiates the fetch and execution.
Evidence against
- package.json has no install lifecycle hooks.
- getPlugin is not invoked during module initialization.
- No local credential harvesting or file writes appear in the package source.
Behavioral surface
EvalNetwork
Source & flagged code
3 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 = ts-utility-plus@1.3.2
matchedPath = index.js
matchedIdentity = npm:dHMtdXRpbGl0eS1wbHVz:1.3.2
similarity = 1.000
shingleOverlap = 1
summary = package final verdict is malicious
High
Known Malware Source Fingerprint Signature
Source fingerprint signature matches a known malicious package signature; route for source-aware review.
index.jsView on unpkgFindings
1 Critical2 High2 Medium1 Low
CriticalRemote Response Code Executionindex.js
HighEvalindex.js
HighKnown Malware Source Fingerprint Signatureindex.js
MediumNetwork
MediumStructural Risk Force Deep Review
LowScripts Present
Affected versions and remediation
This report applies to copytrade-core@2.3.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing copytrade-core@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.