@vscode/deviceid 0.1.6
PkgFire would install this release with a warning.·Checked 33 minutes ago·Published 9 November 2026
Why
-
warnSuspicious behaviour
Binary file/s detected in package: 1db12903faa5359c366720c6e7d2a0398f3429c41f57eb20bba80da27137fdfe: @vscode+deviceid.node (exe) c6425b4d11c8c860344b28b3b3c7b962b2d2120c7e994e66bb81cc148e9cef6e: @vscode+deviceid.node (exe)
-
warnSuspicious behaviour
3 new behaviours since 0.1.5
-
warnRelease cooldown
Published 8 hours 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.
-
warnInstall script added
The install script is new or changed since 0.1.5: install "node scripts/install.mjs". A release that starts running code on install is how event-stream, ua-parser-js and the 2025 npm worms spread. It was already installed before this scan.
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.