# MAL-2026-5933: Malicious code in react-vite-assert (npm)


- **Type:** Malicious package
- **Package:** `react-vite-assert` (npm)
- **Published:** 16 Jun 2026

## What is MAL-2026-5933?

MAL-2026-5933 is a malicious package in react-vite-assert, published on 16 Jun 2026. 

### Official description

react-vite-assert@1.4.1 executes attacker-controlled JavaScript whenever the package is imported. The main entry transitively loads src/features/extras/config.js, which runs a top-level async IIFE that issues an HTTPS GET to https://www.jsonkeeper.com/b/HXDNM, takes the `data.config` string from the response, wraps it with `new Function('require', s)`, and invokes it with a `createRequire(import.meta.url)`-built `require` — granting the fetched code full Node.js access (filesystem, network, child_process, env). The fetch is retried up to 5 times. The remote URL and request headers are disguised by a fake local `process` shadow object whose keys are named DEV_API_KEY/DEV_SECRET_KEY/DEV_SECRET_VALUE, where DEV_API_KEY actually holds the paste URL and the other two hold a request header name/value — deliberate misdirection rather than configuration. jsonkeeper.com is an anonymous, mutable paste host: whoever controls /b/HXDNM can change the executed payload at any time without republishing the package. The combination of import-time auto-execution, anonymous mutable code source, eval of fetched bytes with full `require`, and cover-story variable naming is unambiguous supply-chain attack tradecraft.

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

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

## Sources

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

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