Which versions of auth-next-gen are malicious?

The following npm versions of auth-next-gen are flagged malicious: 1.6.29, 1.7.2, 1.7.11. Treat any of these as compromised.

How do I remediate auth-next-gen if I installed it?

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

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

Yes — auth-next-gen is associated with the IN-MAL-2026-009720, IN-MAL-2026-009718, IN-MAL-2026-009719 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 auth-next-gen 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 auth-next-gen (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging auth-next-gen across your stack and pipelines.

Malicious package

auth-next-gennpm

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

MAL-2026-10180

Immediate action

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

npm uninstall auth-next-gen

What this malware does

On require of auth-next-gen, index.js loads lib/writer.js, which at module top level performs an axios GET against a base64-obfuscated URL (https://www.jsonkeeper.com/b/GS6NQ, with a second hex-encoded URL https://www.jsonkeeper.com/b/HY6M6 staged the same way) and passes the response body to eval(), yielding arbitrary code execution on the installer under attacker control. In parallel, writer.js builds a data object at module top containing the full process.env, os.platform(), os.hostname(), os.userInfo().username, and non-internal MAC addresses, staged alongside the fetched payload for exfiltration. The destination URLs and the axios/get/then identifiers are hidden behind base64 (atob) and a hex-decoding helper. The package.json advertises the module as an SSR auth-sync helper and the code, keywords (logger, stream, json), and image assets (pino-banner.png, pino-logo-hire.png) are lifted from the pino logger project, functioning as a lure that is unrelated to the actual payload in writer.js. jsonkeeper.com is an anonymous pastebin-style host with mutable content — the exec'd bytes can change at any time without a package update.

Malicious versions

3 flagged

1.6.291.7.21.7.11

Indicators of compromise (SHA-256)

b8dce692ce1195a96313ec4a46a421bffa6a6f1f7a31db072e75210bc82658f1

ee9e59b304ae8be37c7b156735cc840fccb9c0a6b642a29016320df16b640375

fe0926f0a2c1f47072efaac014be38bb00c8e9f31f59badf188b1ed74dd5c2ce

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

Campaign

IN-MAL-2026-009720IN-MAL-2026-009718IN-MAL-2026-009719

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks auth-next-gen-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