# MAL-2026-4189: Malicious code in @limebike/supreme-data-grid (npm)


- **Type:** Malicious package
- **Package:** `@limebike/supreme-data-grid` (npm)
- **Published:** 20 May 2026
- **Also known as:** GHSA-5jxw-6cjm-j5cf

## What is MAL-2026-4189?

MAL-2026-4189 is a malicious package in @limebike/supreme-data-grid, published on 20 May 2026. 

### Official description

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

## What should I do about MAL-2026-4189?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-4189 is a malicious package: @limebike/supreme-data-grid (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-4189/ (Markdown: https://insights.sbomify.com/MAL-2026-4189/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-4189

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-4189/
Summaries are generated and may contain mistakes; the official description above is the record.