eslint-angular-reactnpm
Advisory published Updated
eslint-angular-react is a confirmed malicious npm package (MAL-2026-10498) that opens a backdoor for remote access (malicious versions 110.0.0, 110.0.1, 110.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in eslint-angular-react (npm)
What this malware does
package.json declares a preinstall lifecycle script that runs curl against the hardcoded bare IP http://109.71.252.153:8080/ at npm install time, sending the installer's OS (uname -s), username (whoami), working directory (pwd), and hostname as query-string parameters. The script fires automatically on npm install with no user interaction. The package ships only README and package.json — the declared main: index.js is absent and no ESLint functionality is provided — so the package's sole effect on the installer is the reconnaissance beacon. The name impersonates the ESLint plugin namespace (eslint-* / Angular / React), consistent with a typosquat/dependency-confusion lure aimed at developers searching for an ESLint plugin.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for eslint-angular-react (3 malicious versions).
If you installed it — respond
eslint-angular-react establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If eslint-angular-react was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- ReversingLabs · finder
Detect & block this
O3 blocks eslint-angular-react-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.