Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

decimal-format-corenpm

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)

MAL-2026-6689
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall decimal-format-core

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

7 flagged
3.1.03.2.03.3.03.5.23.5.33.5.43.5.5

Indicators of compromise (SHA-256)

7b2044c0f0e89b9329d67d82ec5e5308318aa06503c4e7c2065f9211d00159d2
41dcb1eea736b0aba6c078a55b8b60553925e6981452e5c4f56e57e419801f87
2f05d898f2df459b73e0f596c5a32f304f067189aebcf113308461c01223efbb
5dbe5d2cb44c76cea7687f602605084c02fc811ba652c1ccba2d27b491268f7c
ff503dca96ac8ccafcff6d4200ef4b60525e8f6fa62d5a604ed672a044f0fd24
7418b3fb88f3b25773cddacaa807900d6e5aab486723f17a4bc6306f1aa247fd
d0f9f6c8a5a3e88e1d6ad2df471da63ffd6eb76952455de784307a92d40dcd19
07d73eb9b3d87a4d1a65dcb4e485fca74b01a1473a305a52345a5c7be95b0631

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for decimal-format-core (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging decimal-format-core across your stack and pipelines.

  2. 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.

  3. Did it already run?

    If decimal-format-core was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks decimal-format-core before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. decimal-format-core on npm has been identified as a malicious package (versions 3.1.0, 3.2.0, 3.3.0, 3.5.2, 3.5.3, 3.5.4, 3.5.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007812IN-MAL-2026-007811IN-MAL-2026-008871IN-MAL-2026-008872IN-MAL-2026-008870GHSA-jpc6-jpfr-f453IN-MAL-2026-009834IN-MAL-2026-009875

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.

Explore

decimal-format-core (npm) malicious package — MAL-2026-6689 | O3 Security