# MAL-2026-6249: Malicious code in blinkit-core (npm)


- **Type:** Malicious package
- **Package:** `blinkit-core` (npm)
- **Published:** 21 Jun 2026

## What is MAL-2026-6249?

MAL-2026-6249 is a malicious package in blinkit-core, published on 21 Jun 2026. 

### Official description

On `npm install`, the package's `preinstall` lifecycle hook runs `curl` against `http://d8s0b82plbq3u5sb2vo0sb3a9obr4yjt7.oast.site/` and POSTs the installer's hostname (`hostname -f`), current user (`whoami`), working directory, and a base64-encoded dump of the entire process environment (`env | base64 -w0`) — which on CI/build hosts routinely contains tokens, cloud credentials, and registry auth. The package itself is hollow: `index.js` only exports `{ name, version }` and provides no functionality. The `repository.url` claims `git+https://github.com/zomato/blinkit-core.git` while publishing under that internal-sounding name on the public registry, matching the canonical dependency-confusion attacker shape against Zomato's internal `blinkit-core` namespace. Installer harm: any build pipeline that resolves this public package instead of an internal mirror leaks host identity and the full environment (including secrets) to the attacker's out-of-band interaction listener at install time, before any other code runs.

The OpenSSF Package Analysis project identified 'blinkit-core' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

- The package executes one or more commands associated with malicious behavior.

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

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-6249 is a malicious package: blinkit-core (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-6249/ (Markdown: https://insights.sbomify.com/MAL-2026-6249/index.md)
```

## Sources

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

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