Popular JavaScript libraries were hijacked this week and turned into malware droppers, in a supply chain attack achieved via targeted phishing and credential theft. The npm package eslint-config-prettier, downloaded over 30 million times weekly, was compromised after its maintainer fell victim to a phishing attack. Other packages, namely eslint-plugin-prettier, synckit, @pkgr/core, and napi-postinstall from the same maintainer, were also targeted. The attacker(s) used stolen credentials to publish multiple unauthorized versions of the packages with malicious code to infect Windows machines. On July 18th, developers began noticing unusual behavior after installing versions 8.10.1, 9.1.1, 10.1.6, and 10.1.7 of eslint-config-prettier. These versions were published to the npm registry but had no corresponding changes in the GitHub repository that'd corroborate the releases, raising immediate suspicion within the open-source community. Libraries like eslint-config-prettier and eslint-plugin-prettier make it easier for developers to work with Prettier and ESLint by ensuring that the code formatting rules are consistenly styled across the project without conflicts or rendundant linting. Developer Dasa Paddock initially raised a GitHub issue in the project's repository shedding light on the matter and community members quickly chimed in. Shortly afterward, the package's maintainer, JounQin, confirmed that he had fallen victim to a phishing attack. This allowed an unauthorized party ...
Popular npm linter packages hijacked via phishing to drop malware
BleepingComputer
·Ax Sharma
·Published Jul 19, 2025
·Updated
Affected Software
8 affected components
npm eslint-config-prettier=8.10.1
npm eslint-config-prettier=9.1.1
npm eslint-config-prettier=10.1.6
npm eslint-config-prettier=10.1.7
npm eslint-plugin-prettier
npm synckit
npm @pkgr/core
npm napi-postinstall
Frequently Asked Questions
1
What is the focus of this security article?
The article discusses a supply chain attack involving hijacked npm linter packages used to distribute malware.
2
How were the npm packages compromised?
The npm packages were hijacked through targeted phishing attacks that led to credential theft.
3
Which specific npm packages were affected by this attack?
The affected npm packages include eslint-config-prettier, eslint-plugin-prettier, synckit, and others.
4
What are the versions of the eslint-config-prettier package that were impacted?
The impacted versions of eslint-config-prettier include 8.10.1, 9.1.1, 10.1.6, and 10.1.7.
5
What are the potential risks associated with installing the compromised packages?
Installing the compromised packages can lead to the introduction of malware on users' systems.