Which versions of pymaas are malicious?

The following PyPI versions of pymaas are flagged malicious: 99.99.0. Treat any of these as compromised.

How do I remediate pymaas if I installed it?

pymaas is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed pymaas — how do I know if it already compromised me?

If pymaas was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is pymaas part of a known attack campaign?

Yes — pymaas is associated with the 2026-09-amirgo4496 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find pymaas across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pymaas (version 99.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pymaas across your stack and pipelines.

Malicious package

pymaasPyPI

pymaas is a confirmed malicious PyPI package (MAL-2026-15929) that steals credentials and exfiltrates sensitive data (malicious version 99.99.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pymaas (PyPI)

MAL-2026-15929

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall pymaas

What this malware does

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):

exfiltration-env-variables
dependency-confusion
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

1 flagged

99.99.0

Indicators of compromise (SHA-256)

81e7303aa1cc62cb0fd1e4e6bc28ce118568e8eb5fb56d2a44818bacedf5ebdb

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pymaas (version 99.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pymaas across your stack and pipelines.
If you installed it — respond
pymaas is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If pymaas was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks pymaas before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. pymaas on PyPI has been identified as a malicious package (version 99.99.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-09-amirgo4496

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks pymaas-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database