registry / Remote code execution / tick-forge
tick-forge
TypeScript SDK for the Polymarket CLOB API.
This report shows the evidence for tick-forge@11.5.2. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is a concrete remote code-execution loader, not package-aligned icon functionality. Absence of an install hook does not mitigate the runtime execution path.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Consumer imports the ESM entrypoint and calls its default export.
Impact
Arbitrary code execution in the consuming process.
Mechanism
Remote payload fetch followed by Function-based execution.
Attack narrative
Calling the default export invokes getPlugin(), which fetches JSON from a hard-coded IP endpoint and executes data.credits via new Function. The evaluated payload is supplied require, process, globalThis, Buffer, and timer APIs, enabling arbitrary dependency loading, environment access, and further actions in the host process.
AI rationale
This is a concrete remote code-execution loader, not package-aligned icon functionality. Absence of an install hook does not mitigate the runtime execution path.
Evidence
package.jsonindex.jsREADME.md
Network endpoints1
31.97.137.157:45000/icons/107
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/107.
- index.js passes response data.credits to new Function.
- Remote code receives require, process, global, Buffer, and timers.
- README documents unrelated tickforge API; implementation is a remote loader.
Evidence against
- package.json has no lifecycle hooks.
- No direct local file writes or credential harvesting appear in package source.
Behavioral surface
EvalNetwork
Source & flagged code
2 flagged · loading sourceindex.jsView file
149// 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 = async-mutex-lock@5.3.1
matchedPath = index.js
matchedIdentity = npm:YXN5bmMtbXV0ZXgtbG9jaw:5.3.1
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
2 High1 Medium1 Low
HighEvalindex.js
HighKnown Malware Source Fingerprint Signatureindex.js
MediumNetwork
LowScripts Present
Affected versions and remediation
This report applies to tick-forge@11.5.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing tick-forge@11.5.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.