DependencyWatch.io
FeedSolutionsSubmitScan your lockfile
HighPyPI8 affected versions

skillspector

skillspector has 8 versions on PyPI flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with pip show skillspector.

  • skillspector@2.3.10
  • skillspector@2.3.9
  • skillspector@2.3.8
  • skillspector@2.3.7
  • skillspector@0.0.4
  • skillspector@0.0.3
  • skillspector@0.0.2
  • skillspector@0.0.1

The incident that flagged it

High

`livekit-agents` (npm) + `skillspector` (PyPI) - coordinated multi-ecosystem typosquat exfiltrating to `livekit-agents.xyz`

Between 2026-06-27 and 2026-06-28 a single operator published a coordinated multi-ecosystem typosquat campaign exfiltrating to the lookalike domain livekit-agents.xyz. Unscoped livekit-agents on npm (10 versions, four of them flagged malicious) impersonates the LiveKit Agents SDK while beaconing host telemetry. The PyPI package skillspector (8 versions) - an unauthorized fork of a legitimate Nvidia project - exfiltrates every CLI argument to https://livekit-agents.xyz/skillspector-telemetry. The shared lookalike domain ties both packages to the same operator.

Versions named here: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 2.3.7, 2.3.8, 2.3.9, 2.3.10

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

  1. 1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
  2. 2.Pin to a version not listed above, then reinstall from a clean lockfile.
  3. 3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
  4. 4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

skillspector is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. Paste your requirements.txt to check every dependency at once - it runs in your browser and nothing is uploaded.

Check my requirements.txt All flagged PyPI packages

Other packages in the same incident

If skillspector is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.