debug-js debug 4.4.2 malicious code

Summaryinfo

A vulnerability, which was classified as critical, was found in debug-js debug 4.4.2. This affects an unknown part. Executing a manipulation can lead to malicious code. This vulnerability is tracked as CVE-2025-59144. The attack can be launched remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in debug-js debug 4.4.2. This vulnerability affects some unknown functionality. The manipulation with an unknown input leads to a malicious code vulnerability. The CWE definition for the vulnerability is CWE-506. The product contains code that appears to be malicious in nature. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

debug is a JavaScript debugging utility. On 8 September 2025, the npm publishing account for debug was taken over after a phishing attack. Version 4.4.2 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, preventing further downloads from npm proper. 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. Users should upgrade to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch. Those operating private registries or registry mirrors should purge the offending versions from any caches. This issue has been resolved in 4.4.3.

The advisory is shared for download at github.com. This vulnerability was named CVE-2025-59144 since 09/09/2025. The exploitation appears to be easy. The attack can be initiated remotely. There are neither technical details nor an exploit publicly available.

It is declared as attacked.

Upgrading to version 4.4.3 eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• debug-js

Name

• debug

Version

• 4.4.2

Website

• Product: https://github.com/debug-js/debug/

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion