Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

Malicious code in auth-next-gen (npm)

0
Critical
Published: 07/10/2026 (07/10/2026, 22:42:02 UTC)
Source: GCVE Database
Product: auth-next-gen

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (fe0926f0a2c1f47072efaac014be38bb00c8e9f31f59badf188b1ed74dd5c2ce) 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. ## Source: ghsa-malware (8f52954814f4b0c9537e621a23b42653a6d1e5ec73344441a0a020031ee9983c) 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.

Affected software

npmghsa
auth-next-gen
Affected versions
=1.6.29=1.7.11=1.7.2

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/11/2026, 09:43:33 UTC

Technical Analysis

The auth-next-gen npm package versions 1.6.29, 1.7.2, and 1.7.11 include a malicious module (writer.js) that performs an axios GET request to a base64- and hex-obfuscated URL hosted on jsonkeeper.com, an anonymous pastebin service. The response body is passed directly to eval(), enabling arbitrary code execution controlled by the attacker at install or runtime. Concurrently, the module collects extensive system information including environment variables, OS platform, hostname, username, and MAC addresses, which it stages for exfiltration alongside the fetched payload. The package's metadata and assets are designed to appear as a legitimate SSR auth-sync helper, using assets from the pino logger project as a lure. Because the payload is hosted on a mutable external service, the executed code can change dynamically without any package update. This results in a fully compromised system upon installation or execution of the package.

Potential Impact

Any system with the affected versions of auth-next-gen installed or running is fully compromised, as the package executes arbitrary attacker-controlled code and exfiltrates sensitive system information. All secrets and keys stored on the compromised system should be considered exposed and must be rotated immediately. Removal of the package alone does not guarantee eradication of all malicious artifacts or backdoors introduced by the attacker.

Mitigation Recommendations

No official patch or fix is available. Immediate removal of the auth-next-gen package versions 1.6.29, 1.7.2, and 1.7.11 is strongly recommended. All secrets, credentials, and keys on affected systems should be rotated from a separate, trusted environment. Due to the severity and nature of the compromise, affected systems should be treated as fully compromised and undergo thorough incident response and remediation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
MAL-2026-10180
Osv Schema Version
1.7.4
Aliases
["GHSA-8qpp-8j53-4wh7"]
Ecosystems
["npm"]
Database Specific Severity
null
Cvss Version
null

Threat ID: 6a520e9e68715ace438f3f88

Added to database: 07/11/2026, 09:36:30 UTC

Last enriched: 07/11/2026, 09:43:33 UTC

Last updated: 07/31/2026, 11:19:29 UTC

Views: 69

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses