Malicious code in prisma-callback (npm)

prisma-callback@1.0.3 is a name-confusion attack against the genuine prisma ORM package. The malicious package declares a preinstall hook in package.json that appears benign (node./scripts/only-allow-pnpm.js pnpm) but actually dispatches on system architecture and unconditionally executes one of two compiled Go binaries shipped in the tarball root: prisma-amd64 (1.6 MB) or prisma-arm64 (2.2 MB). These binaries are executed via child_process.execSync with inherited stdio, running under whatever privileges the npm install process holds.\n\nNeither binary exists in the genuine Prisma source tree; both are opaque compiled artifacts that cannot be inspected or verified by the installer. To evade detection, the tarball includes a verbatim copy of the real Prisma monorepo (README, issue templates, and sub-package metadata all reference github.com/prisma/prisma), and the preinstall script includes a misleading comment claiming it is "only used for testing purposes" to discourage code review.\n\nThe attack combines multiple deception vectors: typosquatting a top-tier OSS package, shipping undeclared native binaries, executing them at preinstall time without integrity checks, and using filename obfuscation and false legitimacy signals to lower scrutiny. Any developer or automated system that installed this version would execute arbitrary native code with the privileges of the npm process.