DependencyWatch.io
FeedSolutionsSubmitScan your lockfile
HighPyPI1 affected version

apachelicense

apachelicense has 1 version 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 apachelicense.

  • apachelicense@0.1a1

The incident that flagged it

High

DPRK Contagious Interview campaign expands across 5 ecosystems

Socket disclosed a fresh wave of DPRK Contagious Interview / FAMOUS CHOLLIMA packages spanning npm, PyPI, Go modules, crates.io, and Packagist. They impersonate logging / license developer tooling and act as staged loaders for credential stealers and RATs across Windows, macOS and Linux. The Windows variant deploys a keylogger and AnyDesk for hands-on access.

Versions named here: 0.1a1

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

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