akshare 1.20.48
PkgFire would install this release with a warning.·Checked 3 hours ago·Published 14 November 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 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
- 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.59warn14 Nov 20261.20.58warn14 Nov 20261.20.57warn14 Nov 20261.20.56warn14 Nov 20261.20.55warn14 Nov 20261.20.54warn14 Nov 20261.20.53warn14 Nov 20261.20.52warn14 Nov 20261.20.51warn14 Nov 20261.20.50warn14 Nov 20261.20.49warn14 Nov 20261.20.48warn14 Nov 20261.20.47warn14 Nov 20261.20.46warn14 Nov 20261.20.45warn14 Nov 20261.20.44warn14 Nov 20261.20.43warn14 Nov 20261.20.42warn13 Nov 20261.20.41warn13 Nov 20261.20.40warn13 Nov 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.