Which versions of atrix-mongoose are malicious?

The following npm versions of atrix-mongoose are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate atrix-mongoose if I installed it?

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

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

Yes — atrix-mongoose is associated with the GHSA-pc63-7f4c-3qv5 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 atrix-mongoose 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 atrix-mongoose (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging atrix-mongoose across your stack and pipelines.

Malicious package

atrix-mongoosenpm

Malicious code in atrix-mongoose (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190692

Immediate action

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

npm uninstall atrix-mongoose

What this malware does

The package atrix-mongoose 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

a7b1ca5c62f87d30469e55f9e277026bdbedad7e3060cea2e2a80f20a87dc438

9dc27b71b0a6bedd292b899cd2cafaae36c887c103fbebc76f31189538787ffc

8210cb0987a07bb27c875b0f0a9c6661de7ddffb11e0be9317b8021b0300b83f

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

Campaign

GHSA-pc63-7f4c-3qv5

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks atrix-mongoose-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