For your digest
backslash: backslash@0.2.1 contains malware after npm account takeover
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
backslash (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- backslash (npm): from 0.2.1, before 0.2.2
The fix
backslash (npm) fixed in 0.2.2
npmnpm install backslash@0.2.2pnpmpnpm add backslash@0.2.2yarnyarn add backslash@0.2.2bunbun add backslash@0.2.2Check what is installednpm ls backslashPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency backslash to 0.2.2 or the nearest later release, to fix CVE-2025-59140. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".