Which versions of magentaa11y are malicious?

The following npm versions of magentaa11y are flagged malicious: 9.9.15. Treat any of these as compromised.

How do I remediate magentaa11y if I installed it?

Remove magentaa11y from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

Yes — magentaa11y is associated with the GHSA-q8qr-982j-49vc 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 magentaa11y 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 magentaa11y (version 9.9.15). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging magentaa11y across your stack and pipelines.

Malicious package

magentaa11ynpm

Malicious code in magentaa11y (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2632

Immediate action

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

npm uninstall magentaa11y

What this malware does

The package magentaa11y was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'magentaa11y' @ 9.9.15 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

9.9.15

Indicators of compromise (SHA-256)

1c1c14e542b99ac8e01a06fd61158c90ffe14fbedbf4834d97f38d65d477ebb5

43cbd330a3aaaf8c00dba0e307d001f9a82ab17c63382d10e90a20ffafda20f6

995b52a2411e3213a611e58f659a941136e8021a88e1d638a232018265d5c11a

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for magentaa11y (version 9.9.15). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging magentaa11y across your stack and pipelines.
If you installed it — respond
Remove magentaa11y from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If magentaa11y 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 magentaa11y 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. magentaa11y on npm has been identified as a malicious package (version 9.9.15 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-q8qr-982j-49vc

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks magentaa11y-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring