cypress 16.3.0
PkgFire would stop this release from installing.·Checked 1 hour ago·Published 10 November 2026
Why
-
blockRelease suspect
PkgFire reviewed this release when it was published and compared it with 16.2.1. It has the shape of a hijacked release. It stays blocked until the PkgFire operator has checked it; if you have checked it yourself, add the package to Always allow. Files 16.2.1 also shipped gained what they did not have there: running other programs (dist/exec/xvfb.js). The package could already do this elsewhere; code injected into an existing file looks like this, and so does a refactor. Static analysis finds behaviour 16.2.1 did not have: threat-process-spawn-silent.
Provenance
A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.
- Signature
- Verified against the registry's key
- Build provenance
- None, and no earlier version had any
What the code does
On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.
Code reading
PkgFire's own reading of the files: what the code can do.
Source patterns
Patterns found in the source, including those malware is known to use.
Other checked releases
Check every dependency before it installs
This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.