Which versions of @msecscc/gaia are malicious?

The following npm versions of @msecscc/gaia are flagged malicious: 0.0.1-security, 9.9.9, 99.9.9. Treat any of these as compromised.

How do I remediate @msecscc/gaia if I installed it?

Remove @msecscc/gaia 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 @msecscc/gaia — how do I know if it already compromised me?

If @msecscc/gaia 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 @msecscc/gaia part of a known attack campaign?

Yes — @msecscc/gaia is associated with the GHSA-9m24-6v7q-pffv, RLMA-2026-01036 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 @msecscc/gaia 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 @msecscc/gaia (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @msecscc/gaia across your stack and pipelines.

Malicious package

@msecscc/gaianpm

Malicious code in @msecscc/gaia (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-740

Immediate action

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

npm uninstall @msecscc/gaia

What this malware does

The package @msecscc/gaia 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.

Malicious versions

3 flagged

0.0.1-security9.9.999.9.9

Indicators of compromise (SHA-256)

5186ac1e518b181d1e03469aa042d8dddefbe3345b3c85d5b795ed329e5c3a73

35c005bdb108aca2e4bc9842086fa98dd73b442764e4e7814fd6e7a9fa7010dd

e93f9dfed6a459ca8ffc1d5915fac3e02f43466f98ab5c8d96f1a2dee28704d9

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

Campaign

GHSA-9m24-6v7q-pffvRLMA-2026-01036

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @msecscc/gaia-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