@limebike/supreme-data-gridnpm
Advisory published Updated
@limebike/supreme-data-grid is a confirmed malicious npm package (MAL-2026-4189) that typosquats a legitimate package to trick installs (malicious versions 85.14.46, 85.14.47, 85.14.48). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @limebike/supreme-data-grid (npm)
What this malware does
@limebike/supreme-data-grid occupies the @limebike npm scope (private-looking namespace) with placeholder metadata and a README stating 'Claimed by dphoeniixx'. Both preinstall and postinstall lifecycle hooks invoke index.js, which collects the installer's hostname, all non-internal network interface IPs, current working directory, directory listings of cwd / /app /../../, and the contents of /app/package.json, then POSTs the data as JSON to http://poc.khz.bar/install over plain HTTP. The combination of an internal-scope-impersonating package name plus install-time reconnaissance of host identity, internal IPs, and nearby project metadata is the canonical dependency-confusion attack shape — fires on npm install with no consent, exposing private network topology and project information to an external attacker-controlled host.
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
TyposquatFind it
Search your lockfiles and build artifacts for @limebike/supreme-data-grid (3 malicious versions).
If you installed it — respond
@limebike/supreme-data-grid is a typosquat — you almost certainly intended a legitimately-named package. Remove @limebike/supreme-data-grid, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @limebike/supreme-data-grid 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
Detect & block this
O3 blocks @limebike/supreme-data-grid-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.