Malicious code in privacypass-py (PyPI)
Published Sources: OSV (Schadpakete)
- Malicious package
What is affected, what to do
Uninstall the package, isolate affected environments and rotate credentials that were available during installation.
Not sure whether and how you are affected? Ask a question about this vulnerability
Malicious package
PyPIprivacypass-py
“privacypass-py” is registered as malicious in the PyPI repository. Anyone who installed the package should uninstall it immediately, isolate affected environments and rotate credentials that were present during installation.
Affected versions (3)
- 0.1.100
- 0.1.101
- 0.1.99
purl: pkg:pypi/privacypass-py
Sources (2)
amazon-inspector
IN-MAL-2026-022471Versions from this source: 0.1.101
sha256: 0ca6e88317dac5ec524d2dc6ec4b2af7934e2213569ed7c8a757e59edb45b0c3
kam193
pypi/GENERIC-standard-pypi-install-pentest/privacypass-pyVersions from this source: 0.1.99, 0.1.100, 0.1.101
sha256: 1c4699b191565636c74fc5e6e8ece237bb0186ca11f021298ac91b2931756c09
The OSSF `malicious-packages` namespace lists packages flagged as malicious by static analysis or sandbox detonation. An entry here is a confirmed finding, not a suspicion.
Metrics
—
Priority
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 30.00 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (0ca6e88317dac5ec524d2dc6ec4b2af7934e2213569ed7c8a757e59edb45b0c3)
The package presents itself as 'Privacy Pass client primitives' but ships no cryptographic functionality. Its only runtime effect is a data-exfiltration beacon. setup.py invokes a _report() routine during build/install that collects hostname, username, current working directory, argv, the parent process command line read from /proc//cmdline, and environment variable names and values matching credential-related prefixes (AWS_, GITHUB_, PIP_, and others), then POSTs the JSON payload to the hardcoded bare-IP endpoint http://85.190.112.236:8881/b/ over plain HTTP. privacypass_py/init.py repeats the same beacon at module top level, calling _report('import') on every import privacypass_py with an expanded prefix list (CLOUDFLARE_, SUPERTOKENS, HOME, USER, PATH) and an additional secretish_names list filtered by substrings KEY/SECRET/TOKEN/PASS/CRED/PRIVATE/SEED/MNEMONIC/SIGNATURE/COOKIE/SESSION/AUTH, sent to http://85.190.112.236:8881/f/. The import-time path fires outside pip build isolation. The name and description function as cover for a package whose only shipped code is the beacon.
Source: kam193 (1c4699b191565636c74fc5e6e8ece237bb0186ca11f021298ac91b2931756c09)
Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.
Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.
Campaign: GENERIC-standard-pypi-install-pentest
Reasons (based on the campaign):
-
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
-
The package overrides the install command in setup.py to execute malicious code during installation.