Skip to main content
MalwarePublished Updated

orderly-plugin-liquidity-heatmap (npm) · Malicious Code

Affects orderly-plugin-liquidity-heatmapSource GCVE Database

0

Malicious package : remove orderly-plugin-liquidity-heatmap and rotate any secrets on hosts that installed it.

Data as of 26 Oct 2026, 15:55 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-17848

What to do

Remove orderly-plugin-liquidity-heatmap from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

ProductAffectedFixed in
npmorderly-plugin-liquidity-heatmapAffected
  • 0.0.0-stage – 1.0.6
7 affected builds		Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

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. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (dc82bf27be560cba6faa5304a85b992a07f453c6f9d3f6965f9462666309a3d1) orderly-plugin-liquidity-heatmap@1.0.0 ships a non-functional main (dist/index.js exports registerLiquidityHeatmapPlugin returning an empty function) with no overlay/interceptor/rendering code — the advertised purpose exists only in the README. The sole real behavior is a postinstall script (scripts/setup.js) gated by `process.env.CI && process.env.GITHUB_WORKSPACE`, so the payload fires only inside GitHub Actions. On that trigger it collects runner identity (hostname, user, repo, workflow, platform), enumerates all GITHUB_*/ACTIONS_*/RUNNER_* environment variable names, records GITHUB_TOKEN presence and length, captures the OIDC request URL, the npm registry, egress probe results, and tool versions, and writes the JSON to `<GITHUB_WORKSPACE>/heatmap-setup-report.json` inside the installer's checked-out repository. In addition, when ACTIONS_ID_TOKEN_REQUEST_TOKEN and ACTIONS_ID_TOKEN_REQUEST_URL are set, it uses the installer's OIDC bearer token to call the GitHub ID-token endpoint with `audience=api.github.com` and records the mint result in the same report. The combination of a hollow library stub, CI-environment-only activation, enumeration of secrets-adjacent CI metadata, unauthorized exercise of the workflow's OIDC identity, and placement of the output into the repository workspace where subsequent workflow steps may commit it or upload it as an artifact is a CI-poisoning / supply-chain reconnaissance primitive against the installer's build pipeline. ## Source: ghsa-malware (f25fe3de75e25d7bb2dee4e8cf02e39d79d011bc22a4b52cf0071bf8a73ad2f2) 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.

References

Community reviews

Loading reviews…