Which versions of macaqua are malicious?

The following PyPI versions of macaqua are flagged malicious: 99.7. Treat any of these as compromised.

How do I remediate macaqua if I installed it?

macaqua 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 macaqua — how do I know if it already compromised me?

If macaqua 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 macaqua part of a known attack campaign?

Yes — macaqua is associated with the 2024-11-byted-dast 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 macaqua 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 macaqua (version 99.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging macaqua across your stack and pipelines.

Malicious package

macaquaPyPI

Malicious code in macaqua (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10417

Immediate action

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

pip uninstall macaqua

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

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: 2024-11-byted-dast

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.
typosquatting
dependency-confusion

The OpenSSF Package Analysis project identified 'macaqua' @ 99.7 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.7

Indicators of compromise (SHA-256)

72d7f8fc3a75036a65efb8bfa775e288fca63ae4201506ac9f8505fee566413d

0d3e5367ad7e61dfd3eb5b1eab8d5ef50319475671f95fc3e322c3c8774e3453

9db53b3efafe9bf793b0bad1ddff35077333c7142f3161706e84d918312b7e4f

d856947e365bc994bd41ff1b8668e94a572ce14aac9466943810db302a9fd065

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 macaqua (version 99.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging macaqua across your stack and pipelines.
If you installed it — respond
macaqua 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 macaqua 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 macaqua 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. macaqua on PyPI has been identified as a malicious package (version 99.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-11-byted-dast

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks macaqua-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