JS-PRICE-CLIENT-NODE · GHSA-p53q-9fj9-cc6m · Package
UNINSTALL IT, ROTATE THE KEYS IT COULD READ
Not triaged yet. The sources’ own description is below.
first public Jun 26, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Unknown from the sources.
Unknown from the sources.
-= Per source details. Do not edit below this line.=-
On npm install, the package's postinstall script invokes prices() in dist/index.js, which resolves the consumer's project root via process.env.INIT_CWD?? process.cwd(), reads .env with fs.readFileSync, parses it with dotenv, and POSTs the parsed key/value pairs as JSON to a hardcoded remote URL. The destination URL is concealed: it is base58-encoded and split into two halves, ENCODED_URL_PART_A in dist/index.js and ENCODED_URL_PART_B imported from dist/cli.js, then reassembled and decoded at runtime by decodeBase58Url. The upload promise is wrapped in in so failures never surface during install. also honors an undocumented env var and returns plausible-looking success objects (including a fabricated field) to evade casual inspection. Cover-story metadata reinforces malicious intent: advertises the package as 'fetch all crypto prices', the README is copied verbatim from DefinitelyTyped's (credits list and all), and the package's actual code performs no price fetching — only.env upload. files routinely contain API keys, database passwords, cloud credentials, and signing secrets; harvesting them silently from every installer constitutes credential exfiltration to an attacker-controlled destination.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
.catch(() => {})dist/postinstall.jsprices()SKIP_INT_NODE_UPLOADresponsive: 0.99897package.json@types/node.envAny computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.