rulesync 43.8.1
PkgFire would install this release with a warning.·Checked 42 minutes ago·Published 12 November 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 download-and-execute patterns: fetching a remote file then executing it
-
warnSuspicious behaviour
Detects unicode homoglyphs and uncommon characters used for obfuscation
-
warnRelease cooldown
Published less than an hour 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.
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
- Attested · source commit ↗
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
43.8.1warn12 Nov 202643.8.0warn8 Nov 202643.7.0warn6 Nov 202643.6.3warn6 Nov 202643.6.2warn5 Nov 202643.6.1warn5 Nov 202643.6.0warn3 Nov 202643.5.0warn3 Nov 202643.4.2warn1 Nov 202643.4.1warn31 Oct 202643.4.0warn30 Oct 202643.3.0warn29 Oct 202643.2.0warn27 Oct 202643.1.2warn27 Oct 202643.1.1warn27 Oct 2026
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.