registry / Remote code execution / config-helper-kit
config-helper-kit
TypeScript config toolkits
This report shows the evidence for config-helper-kit@1.3.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 dynamic evaluation pattern. It is runtime-triggered rather than install-time, but warrants blocking because an untrusted remote server controls executable code with full Node capabilities.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Consumer imports and calls the default-exported getPlugin function.
Impact
Remote operator can execute arbitrary Node.js code in the consuming process.
Mechanism
remote response code execution through Function constructor
Attack narrative
A consumer that calls the package's default export causes a request to a hard-coded IP endpoint. If the response is successful JSON, its `credits` property is supplied as the body of `new Function` and immediately invoked with `require`, `process`, `globalThis`, and other Node capabilities. The endpoint can therefore deliver arbitrary code to run in the consumer's environment.
AI rationale
This is a concrete remote-code-execution loader, not a benign dynamic evaluation pattern. It is runtime-triggered rather than install-time, but warrants blocking because an untrusted remote server controls executable code with full Node capabilities.
Evidence
index.jspackage.json
Network endpoints1
31.97.137.157:45000/icons/109
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- Default export invokes a remote plugin fetch when called.
- Remote JSON field `credits` is passed directly to `new Function`.
- Fetched code receives `require`, `process`, global objects, and timers.
- The hard-coded endpoint is an IP address on port 45000.
Evidence against
- package.json has no preinstall, install, or postinstall hook.
- Source contains no direct credential harvesting or file writes; payload behavior is remote-controlled.
Behavioral surface
EvalNetwork
Source & flagged code
7 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 = tailwind-plugin-kit@1.3.2
matchedPath = index.js
matchedIdentity = npm:dGFpbHdpbmQtcGx1Z2luLWtpdA:1.3.2
similarity = 1.000
shingleOverlap = 1
summary = package final verdict is malicious
High
Findings
1 Critical6 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
MediumNetwork
MediumStructural Risk Force Deep Review
LowScripts Present
Affected versions and remediation
This report applies to config-helper-kit@1.3.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing config-helper-kit@1.3.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.