pymaas
Affected
- Versions:
99.99.0
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in pymaas (PyPI)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (3d07b21485fb1007b5cca6c07b48620d235200b19dd62e8d6018d019ec5557dc)
On import pymaas, top-level code in the package invokes a _canary() function that collects the entire os.environ dictionary and socket.gethostname(), serializes them as JSON, and POSTs the payload via urllib.request.urlopen to the hardcoded host https://vuorblucjega.dssldrf.net/python-install-log/pymaas. The behavior runs unconditionally on import with no consent, no gating, and no relationship to the destination domain. Combined with the implausibly high version 99.99.0 and the package's own dependency confusion test description, the shipped code is a dependency-confusion beacon that harvests any credentials present in the process environment (CI tokens, cloud provider keys, registry auth tokens, database passwords) and delivers them to an external non-publisher host.
Source: kam193 (81e7303aa1cc62cb0fd1e4e6bc28ce118568e8eb5fb56d2a44818bacedf5ebdb)
During import, the package exfiltrates environment variables.
---
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-09-amirgo4496
Reasons (based on the campaign):
Not rated by the source.
99.99.0None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0