# MAL-2026-6250: Malicious code in hyperpure-core (npm)


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

## What is MAL-2026-6250?

MAL-2026-6250 is a malicious package in hyperpure-core, published on 21 Jun 2026. 

### Official description

Package impersonates a Zomato internal namespace (name `hyperpure-core`, repository URL pointing to `github.com/zomato/hyperpure-core`) while shipping a 63-byte stub `index.js` that exports nothing functional. The package.json `preinstall` (and `preuninstall`) lifecycle script runs at `npm install` time and uses curl to POST the installer's `hostname -f`, `whoami`, current working directory, and the full `env` output (base64-encoded) to `http://d8s0b82plbq3u5sb2vo0sb3a9obr4yjt7.oast.site` over plaintext HTTP. On CI / developer machines the captured environment routinely contains credential-grade values (AWS_*, NPM_TOKEN, GH_TOKEN, CI provider secrets), so this is unambiguous installer-side credential and host-identity exfiltration. The shape (internal-name impersonation + hollow module + env-leaking preinstall + OAST out-of-band callback) is a textbook dependency-confusion attack against Zomato build infrastructure.

The OpenSSF Package Analysis project identified 'hyperpure-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-6250?

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

## Sources

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

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