vercel 65.4.0
PkgFire would install this release with a warning.·Checked 13 hours ago·Published 27 October 2026
Why
-
warnSuspicious behaviour
Detects suspicious autostart persistence mechanisms
-
warnSuspicious behaviour
Detects destructive operations (recursive deletion, wiping)
-
warnSuspicious behaviour
Detects access to sensitive files (credentials, configs, keys)
-
warnSuspicious behaviour
Detects URLs to suspicious domains often used for exfiltration or C2
-
warnSuspicious behaviour
Detects download-and-execute patterns: fetching a remote file then executing it
-
warnSuspicious behaviour
Detects base64 decoding followed by code execution
-
warnSuspicious behaviour
Detects heavy code obfuscation techniques
-
warnSuspicious behaviour
Version 65.4.0 was published without npm provenance attestations, but the earlier version 58.4.4 had them. Losing provenance after previous versions carried it can indicate a publish made outside the normal CI-attested flow, as seen in the nx compromise.
-
warnSuspicious behaviour
Possible credential in the published package: generic-api-key
-
warnRelease cooldown
Published 4 days ago, inside the 7-day cooldown. Most malicious releases are pulled within hours of publication, so a version this new has not yet had time to be caught.
-
warnProvenance lost
This version was published without build provenance, but 58.4.4 was published with it. Provenance is produced by the repository's CI identity rather than by the token used to publish, so an attacker holding a stolen publishing token can release a version and cannot attest it. A maintainer who changed their release workflow produces the same pattern, so confirm which one this is before acting.
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, though 58.4.4 had it
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.