Which versions of better-auth-nuxt are malicious?

The following npm versions of better-auth-nuxt are flagged malicious: 0.0.10. Treat any of these as compromised.

How do I remediate better-auth-nuxt if I installed it?

better-auth-nuxt 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 better-auth-nuxt — how do I know if it already compromised me?

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

Yes — better-auth-nuxt is associated with the GHSA-8jwp-6329-28fq 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 better-auth-nuxt 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 better-auth-nuxt (version 0.0.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging better-auth-nuxt across your stack and pipelines.

Malicious package

better-auth-nuxtnpm

Malicious code in better-auth-nuxt (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191073

Immediate action

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

npm uninstall better-auth-nuxt

What this malware does

The package better-auth-nuxt 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

0.0.10

Indicators of compromise (SHA-256)

14fe0837bf9131779e90c6a1e8530acbe2d811b2df09dfa25d2d86c5a151c08f

c0550a511cd4a6d4027229a7e48b124afafd892c28c931a34e1d748f2be286e2

63a2c1f5ccee32dc0e1c83e0664d434add6b894caa54c57f137fe0367cba558f

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

Campaign

GHSA-8jwp-6329-28fq

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks better-auth-nuxt-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