Which versions of @guards-lib/auth are malicious?

The following npm versions of @guards-lib/auth are flagged malicious: 99.9.0. Treat any of these as compromised.

How do I remediate @guards-lib/auth if I installed it?

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

If @guards-lib/auth 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 @guards-lib/auth part of a known attack campaign?

Yes — @guards-lib/auth is associated with the GHSA-649h-jv39-hh5v, RLMA-2026-01857 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 @guards-lib/auth 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 @guards-lib/auth (version 99.9.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @guards-lib/auth across your stack and pipelines.

Malicious package

@guards-lib/authnpm

Malicious code in @guards-lib/auth (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2582

Immediate action

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

npm uninstall @guards-lib/auth

What this malware does

The package @guards-lib/auth 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

1 flagged

99.9.0

Indicators of compromise (SHA-256)

47112682da1426da21d8164ed1b9dd3a0dfa3e989e43b8143aad8831987f6530

ab1d52dd0f21364fc408f42ecbd0542aafb997548ea2c2f2c432e8a0f4872752

0b72a9569fc4d43fe6d130bd5ecad08b4e9442b7ca7d8b03c4bfc8a44916d3e6

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

Campaign

GHSA-649h-jv39-hh5vRLMA-2026-01857

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @guards-lib/auth-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