Which versions of magique-ai are malicious?

The following PyPI versions of magique-ai are flagged malicious: 0.4.4, 0.4.5. Treat any of these as compromised.

How do I remediate magique-ai if I installed it?

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

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

Yes — magique-ai is associated with the 2026-06-compr-woodpecker, IN-MAL-2026-009465 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 magique-ai 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 magique-ai (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging magique-ai across your stack and pipelines.

Malicious package

magique-aiPyPI

Malicious code in magique-ai (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-5294

Immediate action

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

pip uninstall magique-ai

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

Versions 0.4.4, 0.4.5 were compromised.

Compromised packages start an obfuscated infostealer. The infostealer is a heavily obfuscated JavaScript code executed using Bun runtime on Python startup. It collectes all kinds of sensitive data, including API keys, credentials to package repositories, cryptocurrency assets, password manager data. Infostealer actively queries online services to collect additional secrets as well as attempts to gain persistence and spread further by publishing infected packages using collected credentials. Data are exfiltrated likely using Github. The code seems to threaten to wipe the user's data if it detects invalid GitHub tokens. Cleanup should be done with caution.

It seems to be related to the recent Mini Shai Hulud campaign.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-06-compr-woodpecker

Reasons (based on the campaign):

compromised-package
exfiltration-env-variables
exfiltration-cloud-tokens
exfiltration-credentials
abuses-pth
obfuscation
infostealer
The package contains code to detect if it is running in a sandbox environment.
exfiltration-crypto
files-exfiltration
destructive-actions

Malicious versions

2 flagged

0.4.40.4.5

Indicators of compromise (SHA-256)

155a3b7ed9c67010006ca571bfcd1fd23d957f4ff7ed21eec9dc6bda7cc44c9a

e7a8794a0420572e9321175e1e4944322bfa6fc69c02b2c3757c3f6ade659d6f

b72f42ba16d4fe37941bf123a6c3f2cbe8c30befbdfcfb3ea16bffb825169101

1869b0097e6865f64af827344d548d3c153fdfea7f461dac575d8e96554d4c23

6806267ad399a4b51411f5176e26470cccb7803dff5f0f6f1e3dca6e6c82170c

4241e99d1053712e6909db44c939421695dff66556055a93058f9a55f8694929

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

Campaign

2026-06-compr-woodpeckerIN-MAL-2026-009465

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks magique-ai-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