@vertexa/prisma-fetch-enginenpm
Advisory published Updated
@vertexa/prisma-fetch-engine is a confirmed malicious npm package (MAL-2026-13608) that typosquats a legitimate package to trick installs (malicious versions 7.8.0, 7.8.1, 7.8.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @vertexa/prisma-fetch-engine (npm)
What this malware does
Package is published under the @vertexa scope but brands itself as @prisma/fetch-engine: README titled '# @prisma/fetch-engine', author 'Tim Suchanek [email protected]', homepage https://www.prisma.io, bug URL github.com/prisma/prisma/issues. Its dependencies rebrand the Prisma toolchain into @vertexa/prisma-debug, @vertexa/prisma-engines-version, and @vertexa/prisma-get-platform. The engine download URL builder in the bundled dist/ chunks resolves the Prisma query-engine native binary to https://github.com/lh0x00/prisma/releases/download/engines-b436f5b358bf3b9d72861631111333dd40434f73/<binary> — a personal GitHub account unaffiliated with Prisma — rather than the official binaries.prisma.sh CDN. Sibling bundles ship additional variants pointing at github.com/lh0x00/@lamhieu/prisma/releases/... and github.com/lh0x00/@lamhieu/@lamhieu/prisma/releases/.... The fetched bytes are written to disk, chmod +x'd, and subsequently invoked by Prisma tooling as the query engine, so a consumer installing this package and running Prisma executes attacker-controlled native code as the database engine process. No hash or signature verification is performed on the downloaded binary, and the download host does not match the impersonated publisher.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Search your lockfiles and build artifacts for @vertexa/prisma-fetch-engine (6 malicious versions).
If you installed it — respond
@vertexa/prisma-fetch-engine is a typosquat — you almost certainly intended a legitimately-named package. Remove @vertexa/prisma-fetch-engine, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @vertexa/prisma-fetch-engine was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @vertexa/prisma-fetch-engine-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.