registry / Remote code execution / polymarket-bot-logger
polymarket-bot-logger
Standardized logging for Polymarket trading bots — consistent startup, trade, and error output.
This report shows the evidence for polymarket-bot-logger@1.0.1. 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 3mo ago · by lpm-firewall-aiThis is a concrete unconsented install-time remote-code-execution chain, not a package-aligned dependency check. The benign exported helpers do not mitigate the malicious lifecycle behavior.
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
Automatic npm `postinstall` execution.
Impact
Arbitrary code execution in the installing user's environment with npm install privileges.
Mechanism
Remote bundle download, extraction, dependency installation, dynamic require, and immediate execution.
Attack narrative
On npm installation, the postinstall script fetches a JSON config from the declared homepage unless overridden by environment variables. That config supplies a remote `.tgz`; the script follows redirects, extracts it into `.peer/`, runs `npm install` in that directory, dynamically loads `.peer/peer-math.js`, and invokes `syncSession()`. The downloaded code is neither pinned nor verified, so the package publisher or config host can execute arbitrary code on every install.
AI rationale
This is a concrete unconsented install-time remote-code-execution chain, not a package-aligned dependency check. The benign exported helpers do not mitigate the malicious lifecycle behavior.
Evidence
package.jsonscripts/install-check.cjsindex.jskelly.jsREADME.md.peer/.peer/peer-math.js.peer/node_modules/
Network endpoints1
jipred.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 `scripts/install-check.cjs` as `postinstall`.
- Install script obtains a config URL from environment or the package homepage.
- It fetches an attacker-controlled bundle URL, follows redirects, and writes a `.tgz` locally.
- It extracts the bundle into `.peer/`, runs `npm install` there, then requires `.peer/peer-math.js`.
- It immediately invokes the remotely supplied module's `syncSession()` during installation.
- README/package naming describe a different package, inconsistent with the install payload.
Evidence against
- `index.js` and `kelly.js` only export local Kelly-stake math helpers.
- No credential harvesting or exfiltration appears in the shipped runtime entry points.
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 = @tailwind-ts/eslint-plugin@0.3.0
matchedPath = scripts/install-check.cjs
matchedIdentity = npm:[redacted]:0.3.0
similarity = 1.000
summary = normalized source hash matched finalized malicious source
Findings
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 polymarket-bot-logger@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing polymarket-bot-logger@1.0.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.