# MAL-2026-4190: Malicious code in @limebike/supreme-date-pickers (npm)


- **Type:** Malicious package
- **Package:** `@limebike/supreme-date-pickers` (npm)
- **Published:** 20 May 2026
- **Also known as:** GHSA-9r56-r4mm-h4p3

## What is MAL-2026-4190?

MAL-2026-4190 is a malicious package in @limebike/supreme-date-pickers, published on 20 May 2026. 

### Official description

On `npm install`, both preinstall and postinstall hooks execute index.js, which collects the installer's hostname, all non-internal network interface IP addresses, directory listings of the current working directory, /app, and../../, and the contents of /app/package.json, then POSTs the data as JSON over plain HTTP to http://poc.khz.bar/install. The package is published under the @limebike scope but its README identifies a different target namespace (@doctolib-apps/native-personalized-services) and is annotated 'Claimed by dphoeniixx' — the canonical dependency-confusion shape: register a public package matching a private/internal name, beacon on install to identify which organizations accidentally resolve to the public registry. Author and description metadata are empty placeholders.

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-4190?

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-4190 is a malicious package: @limebike/supreme-date-pickers (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-4190/ (Markdown: https://insights.sbomify.com/MAL-2026-4190/index.md)
```

## Sources

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

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