akshare 1.20.14
PkgFire would install this release with a warning.·Checked 42 minutes ago·Published 30 October 2026
Why
-
warnSuspicious behaviour
Detects URLs to suspicious domains often used for exfiltration or C2
-
warnSuspicious behaviour
Detects JavaScript variable name mangling (_0x pattern) used by obfuscation tools
-
warnSuspicious behaviour
Possible credential in the published package: generic-api-key
-
warnRelease cooldown
Published 2 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.
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
- Not signed
- Build provenance
- Attested
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
1.20.21warn31 Oct 20261.20.20warn31 Oct 20261.20.19warn31 Oct 20261.20.18warn30 Oct 20261.20.17warn30 Oct 20261.20.16warn30 Oct 20261.20.15warn30 Oct 20261.20.14warn30 Oct 20261.20.13warn30 Oct 20261.20.12warn30 Oct 20261.20.11warn30 Oct 20261.20.10warn30 Oct 20261.20.9warn30 Oct 20261.20.8warn30 Oct 20261.20.7warn30 Oct 20261.20.6warn29 Oct 20261.20.5warn29 Oct 20261.20.4warn29 Oct 20261.20.3warn29 Oct 20261.20.2warn28 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.