CVE-2025-59142: CWE-506: Embedded Malicious Code in Qix- color-string
color-string is a parser and generator for CSS color strings. On 8 September 2025, the npm publishing account for color-string was taken over after a phishing attack. Version 2.1.1 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments. Local environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. npm removed the offending package from the registry over the course of the day on 8 September. On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. This issue has been resolved in 2.1.2.
AI Analysis
Technical Summary
CVE-2025-59142 is a high-severity supply chain vulnerability affecting the 'color-string' npm package, a widely used parser and generator for CSS color strings maintained by the Qix- project. On September 8, 2025, attackers successfully compromised the npm publishing account of 'color-string' via a phishing attack. They published a malicious version 2.1.1 that was functionally identical to the previous patch but contained embedded malware targeting browser environments. Specifically, the malware attempts to intercept and redirect cryptocurrency transactions by manipulating wallet interactions, such as those involving MetaMask, to attacker-controlled addresses. This malicious payload activates only in browser contexts where the package is bundled or directly included as a script, leaving local, server, and command-line environments unaffected. The malicious package was promptly removed from the npm registry the same day, and a clean patch version 2.1.2 was released on September 13 to invalidate cached compromised versions, especially in private registries. The vulnerability is classified under CWE-506 (Embedded Malicious Code) and carries a CVSS 4.0 score of 8.8, reflecting its network attack vector, no required privileges or user interaction, and high impact on integrity due to unauthorized transaction redirection. Although no known exploits in the wild have been reported, the potential for financial theft via cryptocurrency wallets makes this a critical supply chain threat for web applications relying on this package in browser contexts. Developers using 'color-string' in frontend builds with tools like Babel, Rollup, Vite, or Next.js must audit their dependencies and rebuild bundles with the patched version to eliminate the malware.
Potential Impact
For European organizations, the impact of this vulnerability can be significant, particularly for those involved in fintech, cryptocurrency services, e-commerce platforms accepting crypto payments, and any web applications that integrate the 'color-string' package in browser environments. The malware’s ability to silently redirect cryptocurrency transactions compromises the integrity and confidentiality of financial operations, potentially leading to direct financial losses and reputational damage. Organizations relying on frontend JavaScript bundles that include 'color-string' version 2.1.1 risk exposure to theft of digital assets from users interacting with compromised web applications. This could undermine trust in digital payment systems and complicate regulatory compliance with European data protection and financial security standards. Additionally, the supply chain nature of the attack highlights risks in software development practices, emphasizing the need for stringent package management and verification processes. While server-side and local environments are not affected, the widespread use of npm packages in frontend development means many European organizations could be indirectly impacted if they have not updated or rebuilt their browser bundles after the incident.
Mitigation Recommendations
To mitigate this threat, European organizations should: 1) Immediately audit all frontend projects to identify any usage of 'color-string' version 2.1.1, especially in browser-targeted bundles. 2) Rebuild all affected frontend bundles using the patched version 2.1.2 or later to purge the malicious code. 3) Clear caches in private npm registries and CI/CD pipelines to prevent inadvertent reuse of the compromised package. 4) Implement strict supply chain security measures such as package signing verification, integrity checks (e.g., using npm’s 'integrity' field), and monitoring for unexpected package updates. 5) Educate development teams on phishing risks to prevent credential compromise of publishing accounts. 6) Employ runtime monitoring in browser environments to detect suspicious wallet transaction redirections or anomalies. 7) Coordinate with security teams to review incident response plans for supply chain attacks and ensure rapid patch deployment capabilities. 8) Consider adopting tools that provide automated dependency vulnerability scanning and alerting to catch similar threats early.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Estonia, Luxembourg
CVE-2025-59142: CWE-506: Embedded Malicious Code in Qix- color-string
Description
color-string is a parser and generator for CSS color strings. On 8 September 2025, the npm publishing account for color-string was taken over after a phishing attack. Version 2.1.1 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments. Local environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt. The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. npm removed the offending package from the registry over the course of the day on 8 September. On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. This issue has been resolved in 2.1.2.
AI-Powered Analysis
Technical Analysis
CVE-2025-59142 is a high-severity supply chain vulnerability affecting the 'color-string' npm package, a widely used parser and generator for CSS color strings maintained by the Qix- project. On September 8, 2025, attackers successfully compromised the npm publishing account of 'color-string' via a phishing attack. They published a malicious version 2.1.1 that was functionally identical to the previous patch but contained embedded malware targeting browser environments. Specifically, the malware attempts to intercept and redirect cryptocurrency transactions by manipulating wallet interactions, such as those involving MetaMask, to attacker-controlled addresses. This malicious payload activates only in browser contexts where the package is bundled or directly included as a script, leaving local, server, and command-line environments unaffected. The malicious package was promptly removed from the npm registry the same day, and a clean patch version 2.1.2 was released on September 13 to invalidate cached compromised versions, especially in private registries. The vulnerability is classified under CWE-506 (Embedded Malicious Code) and carries a CVSS 4.0 score of 8.8, reflecting its network attack vector, no required privileges or user interaction, and high impact on integrity due to unauthorized transaction redirection. Although no known exploits in the wild have been reported, the potential for financial theft via cryptocurrency wallets makes this a critical supply chain threat for web applications relying on this package in browser contexts. Developers using 'color-string' in frontend builds with tools like Babel, Rollup, Vite, or Next.js must audit their dependencies and rebuild bundles with the patched version to eliminate the malware.
Potential Impact
For European organizations, the impact of this vulnerability can be significant, particularly for those involved in fintech, cryptocurrency services, e-commerce platforms accepting crypto payments, and any web applications that integrate the 'color-string' package in browser environments. The malware’s ability to silently redirect cryptocurrency transactions compromises the integrity and confidentiality of financial operations, potentially leading to direct financial losses and reputational damage. Organizations relying on frontend JavaScript bundles that include 'color-string' version 2.1.1 risk exposure to theft of digital assets from users interacting with compromised web applications. This could undermine trust in digital payment systems and complicate regulatory compliance with European data protection and financial security standards. Additionally, the supply chain nature of the attack highlights risks in software development practices, emphasizing the need for stringent package management and verification processes. While server-side and local environments are not affected, the widespread use of npm packages in frontend development means many European organizations could be indirectly impacted if they have not updated or rebuilt their browser bundles after the incident.
Mitigation Recommendations
To mitigate this threat, European organizations should: 1) Immediately audit all frontend projects to identify any usage of 'color-string' version 2.1.1, especially in browser-targeted bundles. 2) Rebuild all affected frontend bundles using the patched version 2.1.2 or later to purge the malicious code. 3) Clear caches in private npm registries and CI/CD pipelines to prevent inadvertent reuse of the compromised package. 4) Implement strict supply chain security measures such as package signing verification, integrity checks (e.g., using npm’s 'integrity' field), and monitoring for unexpected package updates. 5) Educate development teams on phishing risks to prevent credential compromise of publishing accounts. 6) Employ runtime monitoring in browser environments to detect suspicious wallet transaction redirections or anomalies. 7) Coordinate with security teams to review incident response plans for supply chain attacks and ensure rapid patch deployment capabilities. 8) Consider adopting tools that provide automated dependency vulnerability scanning and alerting to catch similar threats early.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-09-09T15:23:16.326Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 68c866d82e2c3e5d6abeedb5
Added to database: 9/15/2025, 7:19:52 PM
Last enriched: 9/15/2025, 7:20:59 PM
Last updated: 9/18/2025, 12:10:45 AM
Views: 15
Related Threats
CVE-2025-9083: CWE-502 Deserialization of Untrusted Data in Ninja Forms
HighCVE-2025-8942: CWE-284 Improper Access Control in WP Hotel Booking
MediumCVE-2025-10631: Cross Site Scripting in itsourcecode Online Petshop Management System
MediumCVE-2025-10629: Command Injection in D-Link DIR-852
MediumCVE-2025-10628: Command Injection in D-Link DIR-852
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.