What is the jscrambler npm supply chain attack?
On July 11, 2026, attackers used a stolen npm publishing credential to push five malicious jscrambler releases over roughly three hours — 8.14.0, 8.16.0, 8.17.0, 8.18.0, and 8.20.0 — plus four compromised companion plugins. Each shipped hidden native binaries that harvested cloud, crypto-wallet, and AI coding assistant credentials, according to Rescana and Socket.
Answered in
Malware Hid Inside a Popular Obfuscation Tool — and Went Hunting for Your AI Coding Agent's CredentialsStolen npm credentials let attackers slip native-binary malware into jscrambler, hunting for Claude Desktop, Cursor, and Windsurf credentials.
Read the full analysisOther questions this article answers
More development best practices questions
- Why is a large-scale test framework migration usually so slow to do by hand?
- Why did retry loops with error feedback outperform carefully engineered prompts?
- When does a migration pipeline need rich prompt context instead of just retries?
- How do you migrate the last 3% of files that automation can't fully finish?
- Does this approach only work for test framework migrations?
- What is Project Polaris and how does it relate to GitHub Copilot?
- What architecture does Project Polaris use?
- How does Project Polaris perform compared to GPT-4 Turbo on coding benchmarks?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.