PyPI PACKAGE

unsloth-zoo 2026.10.11

Warn

PkgFire would install this release with a warning.·Checked 34 hours ago·Published 30 October 2026

pypi.org

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 system info collection combined with network exfiltration (hostname/user in HTTP requests)

  • 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 dynamic code loading: downloading and importing/executing code at runtime

  • warnSuspicious behaviour

    Detects extensive system/network enumeration activities

  • warnSuspicious behaviour

    Detects base64 decoding followed by code execution

  • warnSuspicious behaviour

    Detects dynamic import chains used to obfuscate code execution

  • warnSuspicious behaviour

    Detects steganography decode followed by code execution

  • warnSuspicious behaviour

    Suspicious code in the published package: pkgfire-py-reads-browser-or-wallet-secrets

  • 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
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.

  • code-credentialsscripts/scan_packages.py, unsloth_zoo/converter_scan.py, unsloth_zoo/llama_cpp.py
  • code-evalscripts/lint_dynamic_exec.py, scripts/lint_exec_literals.py, scripts/scan_packages.py, unsloth_zoo/compiler.py, unsloth_zoo/converter_scan.py
  • code-execscripts/lint_risky_loaders.py, scripts/scan_packages.py, scripts/verify_comment_only_diff.py, unsloth_zoo/compiler.py, unsloth_zoo/converter_scan.py
  • code-networkscripts/scan_packages.py, unsloth_zoo/device_type.py, unsloth_zoo/diffusion_studio/shim.py, unsloth_zoo/llama_cpp.py, unsloth_zoo/mlx/trainer.py

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.

Start free How it works