registry / Remote code execution / polymarket-trading-developer-tool
polymarket-trading-developer-tool
Kelly stake sizing and decimal-safe rounding for Polymarket binary markets
This report shows the evidence for polymarket-trading-developer-tool@0.1.2. 2 of 3 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection confirms concrete unconsented install-time remote code execution via a remote bundle and npm install/require chain. The behavior is not necessary for the advertised Kelly helper library and is hidden behind a lifecycle hook.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm install / package lifecycle postinstall
Impact
Arbitrary code from a remote tgz can run during installation with the installer user's permissions.
Mechanism
install-time remote bundle download, extraction, dependency install, and require execution
Attack narrative
On installation, package.json invokes scripts/install-check.cjs. That script resolves a config URL from env vars or the package homepage, fetches JSON to locate a bundle URL, downloads a tgz, extracts it into .peer, runs npm install inside that extracted directory, requires .peer/peer-math.js, and awaits syncSession(). The published package's normal runtime code is benign Kelly math, but the lifecycle path delegates execution to remote content not present in the package.
AI rationale
Source inspection confirms concrete unconsented install-time remote code execution via a remote bundle and npm install/require chain. The behavior is not necessary for the advertised Kelly helper library and is hidden behind a lifecycle hook.
Evidence
package.jsonscripts/install-check.cjsindex.jskelly.jsREADME.md.peer<os.tmpdir>/psm-sync-*/peer-bundle.tgz.peer/peer-math.js
Network endpoints4
pm-trading-dev-tools-be.vercel.app/config/clob-math.jsonPSM_PEER_URLPSM_SYNC_CONFIGKELLY_PEER_CONFIG
Decision evidence
public snapshotAI called this Malicious at 97.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json defines postinstall: node scripts/install-check.cjs
- scripts/install-check.cjs fetches config from package homepage or env URLs
- Fetched config supplies peerBundle/bundleUrl/url for remote .tgz download
- Postinstall extracts bundle into .peer, runs npm install, then require(.peer/peer-math.js).syncSession()
- Network/code execution is hidden as an install-time peer dependency check while library exports only Kelly helpers
Evidence against
- index.js only re-exports kelly.js helpers
- kelly.js contains simple numeric stake formatting/math
- README documents Kelly usage and mentions install-time peer dependency check
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemNetwork
Source & flagged code
3 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 = previous_version_dangerous_delta
matchedPackage = polymarket-trading-developer-tool@0.1.1
matchedIdentity = npm:[redacted]:0.1.1
similarity = 0.667
summary = stored previous version shares package body but lacks this dangerous source file
Findings
1 Critical1 High4 Medium2 Low
CriticalPrevious Version Dangerous Deltascripts/install-check.cjs
HighInstall Time Lifecycle Scriptspackage.json
MediumDynamic Requireindex.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to polymarket-trading-developer-tool@0.1.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing polymarket-trading-developer-tool@0.1.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.