Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
CriticalCISA KEVExploited in the wildPublic exploit

Nx Console Embedded Malicious Code Vulnerability

IdentifiersCVE-2026-48027CWE-506· Embedded Malicious Code

CVE-2026-48027 tracks a software supply-chain compromise of Nx Console, the user interface extension for Nx and Lerna. A malicious build, Nx Console version 18.95.0, was briefly published to the Visual Studio Marketplace on 2026-05-19 from 12:30 UTC to 12:48 UTC and to OpenVSX from 12:33 UTC to 13:09 UTC. The compromised extension was also reported as being distributable through VS Code’s automatic update mechanism to systems that already had Nx Console installed. According to the provided content, the malicious extension contained embedded malicious code and fetched an obfuscated secondary payload. That payload was capable of harvesting credentials from multiple sources on disk and in memory, including developer and cloud-related secrets. Additional reporting in the provided context states that when a developer opened a workspace with the compromised extension installed, the extension silently retrieved and executed the hidden payload, which targeted items such as GitHub tokens, AWS credentials, Kubernetes configuration, npm tokens, Vault secrets, and 1Password data. The issue is therefore not a conventional memory-corruption flaw in a legitimate code path, but a maliciously published trojanized extension release under a trusted distribution channel.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in compromise of the developer workstation and theft of credentials and secrets accessible from that system. The provided content indicates the payload could harvest credentials from disk and memory and specifically targeted GitHub tokens, cloud credentials, Kubernetes configuration, npm tokens, Vault secrets, and password-manager material. Because Nx Console is a developer tool with access to project context and is distributed through trusted extension marketplaces, compromise can extend beyond the local host into source-code repositories, CI/CD pipelines, package registries, cloud environments, and infrastructure-as-code systems. CISA guidance cited in the content states that any machine that ran the compromised extension should be treated as fully compromised.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade and host remediation cannot be completed, disable or uninstall Nx Console version 18.95.0 and prevent installation of that version from Visual Studio Marketplace or OpenVSX. Treat systems with prior Nx Console installations as potentially exposed because the malicious build may have been delivered via automatic update. As interim risk reduction, restrict extension installation sources to trusted and verified releases, pin approved extension versions where possible, monitor developer endpoints for suspicious outbound activity and secret access, and audit repositories and CI/CD workflows for unauthorized changes. Delay trust in newly published packages or extensions until they have aged sufficiently for ecosystem review, and limit standing developer credentials and token scope to reduce blast radius.

Remediation

Patch, then assume compromise.

Upgrade Nx Console to version 18.100.0, which the provided content identifies as not compromised. Remove the malicious 18.95.0 release anywhere it is installed. Because the extension carried credential-stealing malware, remediation should not stop at upgrading: affected systems should be investigated as compromised hosts, rebuilt or remediated from a trusted state as appropriate, and scanned for indicators of compromise. Organizations should rotate or revoke all credentials that may have been exposed on affected developer machines, including GitHub tokens, npm tokens, cloud credentials, Kubernetes credentials, Vault secrets, SSH keys, and CI/CD-accessible secrets. Repository activity, workflow changes, CI/CD logs, and cloud audit trails should also be reviewed for follow-on abuse.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
NxNx Consoleapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence2

Every observed campaign linking this CVE to a named adversary.

Associated malware1

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity16

Community discussion across Reddit, Mastodon, and other social sources.