decimal-format-corenpm
Advisory published Updated
decimal-format-core is a confirmed malicious npm package (MAL-2026-6689) that steals credentials and exfiltrates sensitive data (malicious versions 3.1.0, 3.2.0, 3.3.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in decimal-format-core (npm)
What this malware does
Malicious npm package published as part of a coordinated DeFi-themed infostealer campaign. decimal-format-core uses a dropper technique: a postinstall hook executes scripts/install-check.cjs at install time, which fetches a second-stage infostealer payload from the C2 domain logstream-api.online. The infostealer harvests cryptocurrency wallet vaults (MetaMask, Phantom, Solflare, OKX, Coinbase, TrustWallet, Backpack, TronLink), Chrome/Firefox/Brave cookies and credentials, SSH keys, AWS credentials, .npmrc tokens, Docker config, shell history, and password manager databases, then exfiltrates the data to the attacker-controlled server.
Package advertises itself as a numeric/text formatting utility but ships an install-time and import-time dropper. The postinstall script runs scripts/install-check.cjs, which reads package.json.homepage (https://logstream-api.online/config/dfc-sync.json) as a remote configuration channel, fetches a .tgz bundle URL from that JSON, downloads and extracts the tarball into a .peer/ directory, runs npm install inside it, then require()s the extracted peer-math.js and invokes syncSession() — executing arbitrary attacker-controlled JavaScript on the installer's machine. The same fetch → extract → npm-install → require flow is also queued via setImmediate from the exported createLogger() entrypoint (through runRuntimeProjectSync() calling peer.packProjectBundle(false)), so consumers that install with --ignore-scripts still trigger remote code execution as soon as the library is imported and used. Payload URL indirection through the remote JSON config allows rotation of the executed code without republishing the npm package. The advertised formatting functionality does not require any network access, tarball extraction, or dynamic loading of downloaded modules.
Any 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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for decimal-format-core (7 malicious versions).
If you installed it — respond
decimal-format-core is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If decimal-format-core was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- SafeDep · finder
Detect & block this
O3 blocks decimal-format-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.