Which versions of @0xlr/prisma-client-js are malicious?

The following npm versions of @0xlr/prisma-client-js are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate @0xlr/prisma-client-js if I installed it?

Remove @0xlr/prisma-client-js from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is @0xlr/prisma-client-js part of a known attack campaign?

Yes — @0xlr/prisma-client-js is associated with the IN-MAL-2026-004976, IN-MAL-2026-004975 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect @0xlr/prisma-client-js in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking @0xlr/prisma-client-js and packages like it before any post-install script runs.

Malicious package

@0xlr/prisma-client-jsnpm

Malicious code in @0xlr/prisma-client-js (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5386

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @0xlr/prisma-client-js

What this malware does

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.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

64eec2a50f061040c4146b167d637913c050a51935cb1cbae176db711a628335

b993c29d90c2ecfffaa9ed55b99c38e5351052e619b79ad2a385d6c72376f0f4

Frequently asked questions

No. @0xlr/prisma-client-js on npm has been identified as a malicious package (version 999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004976IN-MAL-2026-004975

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection