registry / Remote code execution / eslintcmd
eslintcmd
Kelly stake sizing and decimal-safe rounding for Polymarket binary markets
This report shows the evidence for eslintcmd@0.2.0. 2 of 2 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is an unconsented install-time remote-code loader hidden inside a small local utility package. The bundled math code does not justify downloading, installing, and executing a mutable peer payload.
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 install executes the `postinstall` lifecycle hook.
Impact
arbitrary code execution with the installing user's permissions; remote payload may add persistence, steal data, or execute further commands.
Mechanism
unsigned remote bundle download, extraction, dependency installation, and dynamic require
Attack narrative
On installation, `postinstall` resolves a URL from environment variables or the package homepage, fetches a remote configuration/bundle, extracts its contents into `.peer`, executes `npm install` in that directory, dynamically requires the fetched `.peer/peer-math.js`, and invokes its exported function. The downloaded code is not pinned or verified, so the remote server can change execution behavior after publication without changing the npm package.
AI rationale
This is an unconsented install-time remote-code loader hidden inside a small local utility package. The bundled math code does not justify downloading, installing, and executing a mutable peer payload.
Evidence
package.jsonscripts/install-check.cjsindex.jskelly.jsREADME.md.peer/.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 `node scripts/install-check.cjs` as `postinstall`.
- `scripts/install-check.cjs` fetches configuration from the manifest homepage or environment-controlled URLs.
- The fetched JSON selects an unsigned `.tgz` bundle with no integrity, signature, or allowlist check.
- The installer extracts the remote bundle into `.peer`, runs `npm install` there, then requires `.peer/peer-math.js` and calls `syncSession()`.
- Redirects are followed and `PSM_PEER_URL` can replace the bundle source, including `file:` paths.
- The documented public API is only local Kelly-rounding helpers, unrelated to remote install-time synchronization.
Evidence against
- `index.js` and `kelly.js` are simple local math exports.
- No credential collection or exfiltration is present in the bundled source itself.
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 = polymarket-bot-logger@1.0.1
matchedPath = scripts/install-check.cjs
matchedIdentity = npm:cG9seW1hcmtldC1ib3QtbG9nZ2Vy:1.0.1
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 eslintcmd@0.2.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing eslintcmd@0.2.0. 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.