registry / Credential exfiltration / poly-price-node
poly-price-node
fetch all crypto prices
This report shows the evidence for poly-price-node@1.1.2, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is concrete, unconsented install-time credential/configuration exfiltration. The endpoint is intentionally concealed and the lifecycle hook suppresses errors.
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 installation, unless SKIP_INT_NODE_UPLOAD is preset
Impact
Disclosure of secrets and deployment configuration from the install project.
Mechanism
postinstall .env harvesting and HTTP POST exfiltration
Attack narrative
Installing the package runs dist/postinstall.js, which calls prices(). By default, prices() resolves the install project’s .env, parses it, and POSTs all values to a Base58-obfuscated endpoint. Failures are deliberately suppressed so installation succeeds without exposing the network operation. The bundled CLI provides the same upload primitive.
AI rationale
This is concrete, unconsented install-time credential/configuration exfiltration. The endpoint is intentionally concealed and the lifecycle hook suppresses errors.
Evidence
package.jsondist/postinstall.jsdist/index.jsdist/cli.js.env
Network endpoints1
45.8.22.112:3000/api/clob
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- postinstall invokes prices() during npm installation.
- prices() uploads the install project’s .env unless disabled.
- The .env is parsed and POSTed as JSON to an obfuscated default URL.
- Decoded default endpoint is http://45.8.22.112:3000/api/clob.
- CLI also exposes direct .env upload functionality.
Evidence against
- No evidence that the package writes or deletes project files.
- Network failure is suppressed, making install-time exfiltration less visible.
Behavioral surface
EnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
6 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node dist/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node dist/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/index.jsView file
•matchType = normalized_sha256
matchedPackage = price-scripping-js@1.1.2
matchedPath = dist/index.js
matchedIdentity = npm:cHJpY2Utc2NyaXBwaW5nLWpz:1.1.2
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.
dist/index.jsView on unpkgFindings
5 High3 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighKnown Malware Source Similaritydist/index.js
HighKnown Malware Source Fingerprint Signaturedist/index.js
HighSuspicious Lifecycle Evidencedist/postinstall.js
HighAi Review Evidencedist/index.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to poly-price-node@1.1.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing poly-price-node@1.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.