Qix node-backslash 0.2.1 malicious code

Summaryinfo

A vulnerability classified as critical has been found in Qix node-backslash 0.2.1. Affected is an unknown function. This manipulation causes malicious code. The identification of this vulnerability is CVE-2025-59140. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Qix node-backslash 0.2.1. It has been declared as critical. Affected by this vulnerability is some unknown processing. 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. The summary by CVE is:

backlash parses collected strings with escapes. On 8 September 2025, the npm publishing account for backslash was taken over after a phishing attack. Version 0.2.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 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 issues is resolved in 0.2.2.

The advisory is shared at github.com. This vulnerability is known as CVE-2025-59140 since 09/09/2025. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available.

It is declared as attacked.

Upgrading to version 0.2.2 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• Qix

Name

• node-backslash

Version

• 0.2.1

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion