Critical Known exploited (KEV) Ransomware use CVE-2026-48027

Malware in the Nx Console extension (CVE-2026-48027) — a supply-chain attack that steals developer credentials

Nx Nx Console Added to KEV May 27, 2026 Federal remediation due 2026-06-10

A malicious version of "Nx Console," a popular IDE extension for the Nx build system, was published; it fetches an obfuscated payload and harvests credentials (tokens and keys) from disk and memory. CISA listed it as known-exploited (KEV) with confirmed ransomware use (CVSS 9.8 Critical).

Key facts

  • CVE IDCVE-2026-48027
  • CVSS base score9.8 CRITICAL
  • CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Affected (vendor / product)Nx Nx Console
  • CWECWE-506
  • ExploitationListed in CISA KEV (exploitation confirmed); also confirmed used in ransomware
  • Remediation due2026-06-10 (U.S. federal civilian agencies, BOD 22-01)

Key points

  • A tampered build of Nx Console (an IDE extension for the Nx build system) fetched and ran an obfuscated payload
  • It stole credentials from disk and memory (GitHub/npm tokens, SSH keys, cloud credentials, etc.)
  • Listed in CISA KEV = exploitation confirmed; ransomware use also confirmed (CVSS 9.8 Critical)
  • Response: update to a safe version / uninstall, and rotate every credential used on the machine
  • Federal civilian remediation deadline was June 10, 2026 (a practical benchmark for others)
  • Of the 1,687 records held as of 2026-09-01, 8 carry CWE-506 (embedded malicious code) as the first CWE.

1Nx as a build and task runner

CVE-2026-48027 covers a case where a version of "Nx Console" — the IDE extension for Nx (a monorepo build/task runner) — was published with malicious code embedded. It was added to CISA's KEV (Known Exploited Vulnerabilities) catalog on May 27, 2026 and is classified as CWE-506 (embedded malicious code).

2How the tampered extension attack unfolds

The attack flow: installing the tampered extension downloads and executes an obfuscated payload from an external source, then harvests every credential it can find on disk or in memory. The targets are the "keys" developers handle daily — GitHub and npm access tokens, SSH private keys, cloud (e.g. AWS) credentials. Once stolen, an attacker can impersonate a legitimate developer and reach source code, CI/CD, and production.

3When a trusted distribution channel is abused

This class of attack is dangerous because (1) it abuses the trusted distribution channel of a tool developers rely on (an extension marketplace or npm), so it is hard to notice, and (2) compromising a single developer's machine can become a foothold that spreads across the whole organization. CISA has also confirmed exploitation in ransomware campaigns, so priority is high.

4The tools of development as the target

This case is not an attack exploiting a vulnerability but the class where malicious code is embedded in what is distributed. Such records are few, as are development-platform vendors.

Records whose first CWE is CWE-506 (embedded malicious code)8of the 1,687 held as of 2026-09-01
Records from development-platform vendors40Atlassian 13, Progress 9, Jenkins 6 and others
This recordNx Consolemalicious code embedded in an IDE extension

Installing the tampered extension downloads and runs an obfuscated payload from outside and harvests credentials present on disk and in memory. What is targeted are the keys developers handle daily: GitHub and npm access tokens, SSH private keys, cloud credentials. Revoking and reissuing every token, key and password that may have been used on the affected machine is recommended.

Why it matters

Any organization that uses Nx or monorepos in CI/CD can be affected. Beyond checking the extension version, the practical priorities are rotating credentials on the assumption of leakage and reviewing access logs. It is also a prompt to monitor the developer-tool supply chain as an attack surface.

FAQ

What is Nx Console?
An extension for operating Nx (a monorepo build/task runner) from IDEs such as VS Code. It is widely used in frontend and TypeScript development.
How do I check whether I was affected?
Check the affected versions in the vendor's GitHub Security Advisory and compare them with your installed Nx Console version. If you match, it is safest to assume tokens and keys used on that machine were leaked.
What should I do?
Update to a safe version (or remove it), and revoke and reissue the GitHub/npm tokens, SSH keys, and cloud credentials used on that machine. Reviewing CI/CD and cloud audit logs is also recommended.

Sources (primary)

This article is an independent organization based on the U.S. official data below. Always verify the exact, latest details and applicability with the official and vendor sources.

#Supply chain#npm#Developer tools#Credential theft#Ransomware
Disclaimer: This site independently summarizes and classifies information based on official data sources. Always verify the latest and accurate information with the official sources. Content on finance, health, legal, and security is information, not advice. This site is not an official website of the U.S. government.