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

orderly-plugin-liquidity-heatmapnpm

Advisory published Updated

orderly-plugin-liquidity-heatmap is a confirmed malicious npm package (MAL-2026-17848) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in orderly-plugin-liquidity-heatmap (npm)

MAL-2026-17848
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall orderly-plugin-liquidity-heatmap

What this malware does

orderly-plugin-liquidity-heatmap poses as a liquidity heatmap plugin for the Orderly Network orderbook widget, but its only export is an empty stub and a postinstall hook runs node ./scripts/setup.js on npm install. When the script detects GitHub Actions (CI and GITHUB_WORKSPACE set), it records the runner's host, user, repository, GITHUB_/ACTIONS_/RUNNER_ variable names, GITHUB_TOKEN presence and length and network egress, and requests an OIDC token from ACTIONS_ID_TOKEN_REQUEST_URL. From 1.0.2 it uses the workflow's GITHUB_TOKEN to commit heatmap-setup-report.json to the default branch of the installing repository, and 1.0.4 also force-pushes a heatmap-setup-<timestamp> git tag with the credentials actions/checkout persists in .git/config; 1.0.6 ships the same setup.js as 1.0.4. The npm account dumtban published the six versions between 13:12 and 16:05 UTC on 2026-10-11, each extending the previous one's access to the CI runner.

Malicious versions

6 flagged
1.0.01.0.11.0.21.0.31.0.41.0.6

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for orderly-plugin-liquidity-heatmap (6 malicious versions).

  2. If you installed it — respond

    orderly-plugin-liquidity-heatmap 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 orderly-plugin-liquidity-heatmap 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

No. orderly-plugin-liquidity-heatmap on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • InvisiRisk, Inc. · finder

Detect & block this

O3 blocks orderly-plugin-liquidity-heatmap-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
orderly-plugin-liquidity-heatmap (npm) malicious package — MAL-2026-17848 | O3 Security