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

@limebike/supreme-data-gridnpm

Malicious code in @limebike/supreme-data-grid (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4189
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @limebike/supreme-data-grid

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

3 flagged
85.14.4685.14.4785.14.48

Indicators of compromise (SHA-256)

e59c7707b019ba5e34fa465faff8c3815401a71ada45b3af249401aa146a0915
a8a596bb1d0fcacabd41924a8a40c105edc2bfca1d7091b2049a16a74ca480d2
d72fba8642f710870ab65fff363fc7a6c9b9ef26414823a7ee14acd0ef9a9eb8
fcb6ae9ccb34fe2575693ecc2ce7f1328ae94fac385ee3ad42f001f72d9a1f5d
018193d4f68c2fcaad63da76c3c125ed94d5a6da1efaab85147ff59efafa0b46
7f558e822858706221c4efb8e45af9a7e1dccf5fdc50c4ad75ef9326f3a3ddf6

Detection & response playbook

Typosquat
  1. Find it

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

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

  3. Did it already run?

    If @limebike/supreme-data-grid 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 @limebike/supreme-data-grid 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. @limebike/supreme-data-grid on npm has been identified as a malicious package (versions 85.14.46, 85.14.47, 85.14.48 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5jxw-6cjm-j5cfIN-MAL-2026-003554IN-MAL-2026-003547IN-MAL-2026-003552IN-MAL-2026-003553IN-MAL-2026-003548

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.