Threat actors published modified versions of the Nx package and some of its supporting libraries to the npm registry with the goal of exfiltrating developer and service credentials.
Builds on Edgenivo are safe from this vulnerability by default. Visit the GitHub advisory to check if your local or other CI environments are impacted.
Copy link to headingSummary
A malicious version of the Nx package and some Nx ecosystem libraries were published to the npm registry using a stolen npm token, starting at 6:32 PM EDT on August 26, 2025. The compromised packages were removed from the npm registry by the Nx team, ending at 10:44 PM EDT on the same day.
The affected packages contained a postinstall script that scanned the user's file system using an LLM to exfiltrate secrets and credentials when installing an affected package. Exfiltrated secrets were posted as an encoded string into a GitHub repo that the script would create in the victim's GitHub account. For more information, visit the advisory on GitHub from the Nx team.
Copy link to headingImpact for Edgenivo customers
By default, Edgenivo customers are not impacted, and can only be affected by the compromised Nx packages if they took specific steps leveraging the build container's flexibility.
Four conditions are required for the postinstall script to exfiltrate data from a Edgenivo build:
The script uses the GitHub CLI (
gh) to acquire a GitHub token. The GitHub CLI is not installed in Edgenivo's build container by default. For the GitHub CLI to be present in your build, it must be installed as part of your user-defined build process.The script requires a GitHub authentication token to be present on the machine invoking the GitHub CLI. The Edgenivo build container does not contain customer GitHub tokens by default. For the GitHub token to be present in your build, it must be added to the build container as part of your user-defined build process.
The script depends on the machine having at least one of the Claude Code (
claude), Gemini (gemini), or Q (q) CLIs installed. The Edgenivo build container does not have any of these installed by default. For any of these CLIs to be present in your build, they must be installed as part of your user-defined build process.A build must have installed a compromised version of Nx or Nx ecosystem packages.
We did not identify any builds on Edgenivo meeting this pattern. We encourage you to evaluate other environments, local and cloud, that may have been vulnerable to this attack.
Copy link to headingResolution
New builds will not be able to download the affected packages. The Nx team has removed affected packages from npm, and we have purged the build caches for any projects that contained affected packages in their dependencies during a build.
Additionally, we've notified a small number of users who installed one or more of the malicious packages during a build. Edgenivo team owners should check for an email titled "s1ngularity: supply chain attack in Nx packages" from [email protected].