Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@mastra/authnpm

@mastra/auth is a confirmed malicious npm package (MAL-2026-5940) that executes malicious code on install (malicious version 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @mastra/auth (npm)

MAL-2026-5940
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @mastra/auth

What this malware does

The package was found to contain malicious code or consuming dependency that contains 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
1.0.3

Indicators of compromise (SHA-256)

17414cdad6ecebc4308a1ef3124a1180d524e7a4a3a85d8dfde64ec1d0f6660b
8918dd16aca072972c93ebb866b08d6d5fda0b443955a2d4589ecbdbf4b87539

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @mastra/auth (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @mastra/auth across your stack and pipelines.

  2. If you installed it — respond

    Remove @mastra/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.

  3. Did it already run?

    If @mastra/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.

  4. How O3 protects you

    O3 blocks @mastra/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. @mastra/auth on npm has been identified as a malicious package (version 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-957m-hm9p-jqrvIN-MAL-2026-008421

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @mastra/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.

Explore

@mastra/auth (npm) malicious package — MAL-2026-5940 | O3 Security