registry / Staged payload carrier / twapfetch
twapfetch
Simple Polymarket RTDS client for Chainlink TWAP prices (30s / 60s)
This report shows the evidence for twapfetch@1.1.1. 3 of 4 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe shipped API does not need this installer, while its postinstall executes a remotely controlled dependency payload. This is concrete install-time remote code execution.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
npm postinstall
Impact
Arbitrary code from a remotely selected package can run with the installing user's permissions.
Mechanism
remote bundle download, npm install, and dynamic module execution
Attack narrative
During postinstall, the package downloads JSON from its homepage (or an environment-selected URL), obtains a bundle URL, downloads and extracts the tgz to .peer, runs npm install there, and requires .peer/peer-math.js before calling syncSession. The remote operator can replace the configuration or bundle to execute arbitrary code during installation.
AI rationale
The shipped API does not need this installer, while its postinstall executes a remotely controlled dependency payload. This is concrete install-time remote code execution.
Evidence
package.jsonscripts/install-check.cjsindex.jsREADME.md.peer<temporary>/psm-sync-*/peer-bundle.tgz.peer/peer-math.js
Network endpoints1
slimopump.vercel.app/config/clob-math.json
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json runs postinstall.
- scripts/install-check.cjs fetches homepage config.
- Remote config selects a .tgz bundle URL.
- Postinstall extracts bundle into .peer and runs npm install.
- Dynamically requires .peer/peer-math.js and invokes syncSession().
- README advertises absent RTDS API; index.js exports only Kelly helpers.
Evidence against
- Bundled index.js and kelly.js contain only local math helpers.
- No direct credential harvesting is present in shipped source.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/install-check.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgindex.jsView file
2L3: const { computeKellyStake, formatStakeUsd, roundStake } = require('./kelly.js');
L4:
Medium
scripts/install-check.cjsView file
•matchType = normalized_sha256
matchedPackage = fetchrtds@1.1.0
matchedPath = scripts/install-check.cjs
matchedIdentity = npm:ZmV0Y2hydGRz:1.1.0
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
scripts/install-check.cjsView on unpkg•matchType = malicious_source_fingerprint_signature
signature = 7a6b9f9c6080c2a1
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = fetchrtds@1.1.0
matchedPath = scripts/install-check.cjs
matchedIdentity = npm:ZmV0Y2hydGRz:1.1.0
similarity = 1.000
shingleOverlap = 2
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.
scripts/install-check.cjsView on unpkgFindings
3 High4 Medium2 Low
HighInstall Time Lifecycle Scriptspackage.json
HighKnown Malware Source Similarityscripts/install-check.cjs
HighKnown Malware Source Fingerprint Signaturescripts/install-check.cjs
MediumDynamic Requireindex.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to twapfetch@1.1.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing twapfetch@1.1.1. 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.