registry / Remote code execution / ventra-kit
ventra-kit
A lightweight utility toolkit for JavaScript and Node.js projects, providing common helper functions for everyday development.
This report shows the evidence for ventra-kit@1.0.2, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe source implements a direct remotely controlled code-execution path; the lack of an install hook only limits activation to runtime use.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Runtime invocation of the package's exported function.
Impact
Remote server can run arbitrary code in the consuming process.
Mechanism
Remote response fetched and executed with Function.
Attack narrative
index.js exports a function that calls getPlugin(). It fetches JSON from a hard-coded IP address, extracts data.credits, constructs a Function from it, and invokes it with require, process, global, Buffer, and timer APIs. This gives the remote endpoint arbitrary code execution in the consumer's Node process.
AI rationale
The source implements a direct remotely controlled code-execution path; the lack of an install hook only limits activation to runtime use.
Evidence
package.jsonindex.jsREADME.md
Network endpoints1
31.97.137.157:45000/icons/116
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/116.
- index.js passes response JSON field data.credits to new Function.
- Executed payload receives require, process, global, Buffer, and timers.
- Exported function invokes the remote loader when called.
Evidence against
- package.json has no lifecycle hooks.
- No local credential harvesting or file writes appear in 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 = 34c9b829bcd3b8e8
signatureType = suspicious_hashes
sourceLabel = Datadog
matchedPackage = cmc-client@1.0.5
matchedPath = index.js
matchedIdentity = npm:Y21jLWNsaWVudA:1.0.5
similarity = 1.000
shingleOverlap = 1
summary = Datadog malicious npm corpus sample: samples/npm/malicious_intent/cmc-client/1.0.5/2026-02-12-cmc-client-v1.0.5.zip
Findings
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 ventra-kit@1.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing ventra-kit@1.0.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.