PyPI PACKAGE

vllm 0.32.0

Warn

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

pypi.org

Why

  • warnSuspicious behaviour

    Detects suspicious autostart persistence mechanisms

  • 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 steganography decode followed by code execution

  • warnSuspicious behaviour

    Detects unicode homoglyphs and uncommon characters used for obfuscation

  • warnSuspicious behaviour

    Detects suspicious imports in setup.py: network, system, or crypto libraries that have no place in a build script

  • warnSuspicious behaviour

    Binary file/s detected in package: 259d554fa892733414f16373f27124ddd549605f128dbdaa2370b5665d885417: vllm-rs (elf) 3b65016974af6fe3f9379228aae4ba8917ed07c321a1736fdbb5d7b7824a6a90: spinloop.abi3.so (elf) 244ec7ba2009c869cb9663a18841ec2f41733e84edc14427bc7cd0b359b80d86: fs_io_C.abi3.so (elf) 02760bd7a9018e24664b8e736a163b43efc0c90fd9766db8b862851ab332b2df: cumem_allocator.abi3.so (elf) d0b7b1b6da9ed41f1f8645c6a2ea10bec972e614f8886cc30768d48e426dfbcc: _qutlass_C.abi3.so (elf) ebfc37da93aac3844cbaad9e37c8847c74c743b4b834b9ed608ad0285a20d10a: _moe_C_stable_libtorch.abi3.so (elf) 9bd1a07ed88e53ca2629c5bff9c51db9831dbf0ef427875b702c3b5981c3073f: _flashmla_extension_C.abi3.so (elf) 91c394d068c684458169f8b6ecdcdc1ba8b8925e2c27dc03ed8773943b21d3d1: _flashmla_C.abi3.so (elf) 8945a7e7b9e52e833208ef0c56753e3e1cd0c2d49e91fb9e31bf95e43d87ff1f: _flashkda_C.abi3.so (elf) eb954b187c6e225483828a132aba1bdafd504abff9dc4a00909f446fda967ec8: _deepselect_C.abi3.so (elf) 7f9fe0afa75af972b4421d81f72e177b71d5b70f62d42e5787b5e1f1cf534e84: _C_stable_libtorch.abi3.so (elf) f0cee503d57d26c28d63fbefa46d2ec2ebe2b96adf76fbdafd6d12bc075c1281: _vllm_fa3_C.abi3.so (elf) be52450ee26044a3903082a726e05d2f0f0acbdcce994e94e12c6f54274a2246: _vllm_fa2_C.abi3.so (elf) 34f79631897492ff5d53779d6c3e065cb09ccdc580f58bc49bfdc46e45391de6: _C_extension.abi3.so (elf)

  • warnSuspicious behaviour

    Suspicious code in the published package: pkgfire-install-hook-fetches-and-executes

  • warnSuspicious behaviour

    Possible credential in the published package: generic-api-key

  • warnSuspicious behaviour

    Possible credential in the published package: curl-auth-header

  • warnSuspicious behaviour

    Gained an install-time script since 0.31.0

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

Licence and upkeep

Licence
Apache-2.0
Source
github.com/vllm-project/vllm ↗
OpenSSF Scorecard
None published for this repository, which is common for small projects and not the same as scoring badly

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-credentials.buildkite/scripts/hardware_ci/run-amd-test.sh, .buildkite/scripts/upload-release-wheels-pypi.sh, .buildkite/scripts/upload-rocm-wheels.sh, .github/workflows/scripts/run_ci_command.py, setup.py
  • code-evalvllm/compilation/backends.py, vllm/compilation/caching.py, vllm/compilation/codegen.py, vllm/distributed/weight_transfer/ipc_engine.py, vllm/entrypoints/openai/chat_completion/protocol.py
  • code-exec.agents/skills/transformers-upgrade/scripts/find_upstreamed.py, .buildkite/performance-benchmarks/scripts/launch-server.sh, .buildkite/performance-benchmarks/scripts/run-performance-benchmarks.sh, .buildkite/scripts/ci-otel/ci_gpu.py, .buildkite/scripts/hardware_ci/run-amd-test.sh
  • code-network.agents/skills/transformers-upgrade/scripts/dump_model.py, .buildkite/amd-disagg/vllm_disagg.sh, .buildkite/image_build/image_build.sh, .buildkite/performance-benchmarks/scripts/run-performance-benchmarks.sh, .buildkite/scripts/check-ray-compatibility.sh
  • install-credentialssetup.py
  • install-execsetup.py
  • install-networksetup.py

Source patterns

Patterns found in the source, including those malware is known to use.

  • bundled_binary
  • capability-filesystem-delete
  • capability-filesystem-read
  • capability-filesystem-write-executable
  • capability-network-download
  • capability-network-lolbas
  • capability-network-outbound
  • capability-process-schedule
  • capability-process-spawn
  • threat-filesystem-autostart
  • threat-filesystem-read
  • threat-network-exfil-sysinfo
  • threat-network-exfiltration
  • threat-process-download-exec
  • threat-process-hooks
  • threat-process-memory
  • threat-process-spawn-silent
  • threat-runtime-environment-read
  • threat-runtime-obfuscation
  • threat-runtime-obfuscation-steganography
  • threat-runtime-obfuscation-unicode
  • threat-setup-suspicious-imports

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