registry / Remote code execution / ts-utility-plus
ts-utility-plus
TypeScript toolkit for reusable utilities.
This report shows the evidence for ts-utility-plus@1.3.2, the only known version.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe package contains a concrete remote-payload execution chain, not merely a dynamic-evaluation primitive. Although it is user-invoked rather than install-time, the hard-coded external loader has no integrity or trust boundary.
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 and calls its default getPlugin export.
Impact
Remote operator can run arbitrary Node.js code with the consumer process privileges.
Mechanism
Fetch remote JSON then execute data.credits via Function.
Attack narrative
At runtime, getPlugin requests a hard-coded IP endpoint and parses its JSON response. It constructs a Function from data.credits and invokes it with require, process, global, Buffer, and timers, allowing the server to supply arbitrary Node.js code in the caller's environment. No lifecycle hook is needed; calling the advertised default export triggers the chain.
AI rationale
The package contains a concrete remote-payload execution chain, not merely a dynamic-evaluation primitive. Although it is user-invoked rather than install-time, the hard-coded external loader has no integrity or trust boundary.
Evidence
package.jsonindex.js
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
- index.js:getPlugin fetches https://31.97.137.157:45000/icons/109 by default.
- index.js passes remote JSON field data.credits to new Function and executes it.
- Executed remote code receives require, process, global, Buffer, and filesystem path context.
- package.json has no lifecycle hooks; execution requires importing and calling the default export.
Evidence against
- No install/preinstall/postinstall scripts in package.json.
- No direct credential harvesting or file writes are present in the inspected 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 = tick-forge@11.5.2
matchedPath = index.js
matchedIdentity = npm:dGljay1mb3JnZQ:11.5.2
similarity = 1.000
shingleOverlap = 1
summary = package final verdict is malicious
High
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 ts-utility-plus@1.3.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing ts-utility-plus@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.