# MAL-2026-5386: Malicious code in @0xlr/prisma-client-js (npm)


- **Type:** Malicious package
- **Package:** `@0xlr/prisma-client-js` (npm)
- **Published:** 9 Jun 2026
- **Also known as:** GHSA-mrxf-wq2g-xvxm

## What is MAL-2026-5386?

MAL-2026-5386 is a malicious package in @0xlr/prisma-client-js, published on 9 Jun 2026. 

### Official description

On `npm install`, postinstall.js enumerates all of process.env, collects hostname, username, homedir, cwd, argv, platform/arch/release, memory and CPU info, and POSTs the resulting JSON blob over HTTPS to the hardcoded attacker-controlled domain `rytxau88zxh61dw6qz4yn19naeg54vsk.oastify.com` (a Burp Collaborator out-of-band exfiltration host). The package name `@0xlr/prisma-client-js` impersonates the legitimate prisma-client-js / @prisma/client packages, and the 999.0.0 version is the canonical dependency-confusion override pattern; the package.json description self-identifies as a 'Placeholder reservation' for that namespace. Any installer running `npm install` against this package leaks the full process environment — including AWS_*, NPM_TOKEN, GH_*, CI/CD secrets — plus host identifiers to the attacker.

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

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-5386 is a malicious package: @0xlr/prisma-client-js (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-5386/ (Markdown: https://insights.sbomify.com/MAL-2026-5386/index.md)
```

## Sources

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

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