CVE-2025-54313 is an embedded malicious code vulnerability in Prettier eslint-config-prettier. CISA added it to the Known Exploited Vulnerabilities catalogue on 22 January 2026, which means attackers have used it in real attacks. Prettier eslint-config-prettier contains an embedded malicious code vulnerability. Installing an affected package executes an install.js file that launches the node-gyp.dll malware on Windows.
What this CVE means in supply-chain terms
This vulnerability is dangerous because it turns package installation into code execution. In practice, a developer or build system that installs the affected package can unknowingly launch malicious code during setup, before normal application controls or review processes have a chance to intervene.
For teams that rely on npm packages in CI/CD, the main security issue is trust in the install path itself. A package can look legitimate until the install step runs, which means dependency review, lockfiles, and repository hygiene do not fully protect you if a malicious package has already entered the software supply chain.
How organisations assess exposure
Exposure starts with finding every place the package may be installed: developer workstations, build agents, test environments, and any downstream project that depends on it. Organisations should confirm whether the package is present directly or transitively, then identify where automated installs could trigger the malicious install.js behavior.
Because this CVE is already in CISA’s Known Exploited Vulnerabilities catalogue, teams should treat it as an active exploitation concern rather than a theoretical defect. The authoritative references for version and fix details are the vendor advisory and the CVE Program, together with the NIST National Vulnerability Database for the canonical record.
Containment and remediation priorities
The safest response is to remove the malicious package from affected environments and replace it with a verified, clean dependency source. If immediate removal is not possible, restrict where installs can run, reduce the blast radius of build credentials, and prevent uncontrolled package execution in unattended pipelines.
Because the attack path depends on installation-time execution, compensating controls should focus on trust boundaries around package ingestion. That includes tighter dependency approval, isolation of build runners, and strong control over who can introduce or update packages in the software delivery chain.
Detection and compromise review after installation
Detection should focus on install-time telemetry, unexpected child processes from package managers, and any signs that Windows hosts executed the malware payload. If the package was installed before remediation, organisations should review endpoint, build, and proxy logs for suspicious follow-on activity that may have occurred during or after installation.
Post-patch review matters because removing the package does not prove the environment was clean. If the malicious code already ran, the organisation may need to investigate credential exposure, lateral movement from build systems, and persistence on developer or CI hosts. Where software supply-chain compromise is suspected, reviewdog Action compromise 2025 and tj-actions/changed-files compromise 2025 show how malicious package and workflow execution can expose CI/CD secrets at scale.
Risk and Threat Considerations
This kind of malicious package is attractive because it exploits a trusted automation step. Attackers do not need to wait for a user to click a file or open a document, they only need the package to be installed in a path that executes its setup logic.
Failure mechanism: the install process runs attacker-controlled code before normal application use, allowing malware to execute during dependency installation and potentially inherit the trust, network reach, or secrets available to the build or developer environment.
Impact: exposed development credentials, poisoned build output, compromised CI/CD systems, and downstream supply-chain spread if the affected package is reused across multiple projects or environments.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CIS Controls v8, NIST SP 800-53 Rev 5 and SLSA set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-16 — Application Software Security | This CVE is a software supply-chain malicious code issue that affects package installation. |
| Recommendation — Harden dependency intake and verify packages before they are allowed to execute in builds. | ||
| NIST SP 800-53 Rev 5 | SI-3 — Malicious Code Protection | The vulnerability installs and runs malware through a package install path. |
| SA-11 — Developer Testing and Evaluation | The issue sits in software acquisition and build-time validation of third-party components. | |
| CM-8 — System Component Inventory | Exposure assessment depends on knowing where the affected package is deployed. | |
| Recommendation — Scan and block malicious code at installation and execution points across endpoints and build hosts. Test third-party components and validate supply-chain inputs before they reach production builds. Inventory affected components so you can locate every system that may execute the malicious package. | ||
| SLSA | Build provenance and supply chain integrity | This is a package compromise that affects build provenance and artifact trust. |
| Recommendation — Require stronger provenance and controlled build inputs for third-party dependencies. | ||
Practitioner Guidance
Why practitioners should care: package installation is part of the attack surface, not just a deployment step. Teams that assume dependency management is safe as long as the package name looks legitimate are missing the execution risk hidden in install scripts.
What to watch for: unexpected script execution during installs, changes in package provenance, and build hosts that suddenly show malware-like behavior after a dependency update. If an environment installed the package, treat that event as a possible compromise trigger rather than a routine maintenance task.
Practitioner takeaway: verify dependency integrity, isolate build execution, and assume any environment that ran the malicious installer may need review, not just patching.
Related resources from NHI Mgmt Group
- What breaks when malicious instructions are embedded in a Claude Code project file?
- What breaks when malicious code hides in build and config files instead of package hooks?
- What breaks when malicious code is embedded in a WordPress plugin or theme update?
- Why does public exploit code make CVE-2025-31324 more dangerous?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 17, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org