Unauthorized npm publish of [email protected] with modified postinstall script
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · GHSA-9ppg-jx86-fqw7
Published### Description On February 17, 2026 at 3:26 AM PT, an unauthorized party used a compromised npm publish token to publish an update to Cline CLI on the NPM registry: [email protected]. The published package contains a modified package.json with an added postinstall script: `"postinstall": "npm install -g openclaw@latest"` This causes openclaw (an unrelated, non-malicious open source package) to be globally installed when [email protected] is installed. No other files were modified -- the CLI binary (dist/cli.mjs) and all other package contents are identical to the legitimate [email protected] release. A corrected version (2.4.0) was published at 11:23 AM PT and 2.3.0 was deprecated at 11:30 AM PT. The compromised token has been revoked and npm publishing now uses OIDC provenance via GitHub Actions. ### Impact Users who installed Cline CLI [email protected] during the approximately 8-hour window between 3:26 AM PT and 11:30 AM PT on February 17 will have openclaw globally installed. The openclaw package is a legitimate open source project and is not malicious, but its installation was not authorized or intended. The Cline VS Code extension and JetBrains plugin were not affected. This advisory applies only to the Cline CLI package published on npm. ### Patches Versions 2.4.0 and higher are fixed ### Workarounds If you installed Cline CLI [email protected]: 1. Update to the latest version of the Cline CLI `cline update` or `npm installl -g cline@latest` 2. Verify that you have a fixed version (2.4.0 or higher) `cline --version` 3. Review your environment for any unexpected installation of OpenClaw and remove it if not intended `npm uninstall -g openclaw`
- Source published
- 19 Feb 2026 15:17:10 UTC
- Source modified
- 9 Sep 2026 05:30:03 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
Publisher rating · LOW
osv · MAL-2026-1380
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (38d7531f4d4af07fee607e1d2985d0ea5b41dbf28cca5bc16c8457934e372f86) The package cline was found to contain malicious code. ## Source: ghsa-malware (3c16746b2d863d4c24bbc2297611c642a02942b47d12b675c4a3120911c72eec) ### Description On February 17, 2026 at 3:26 AM PT, an unauthorized party used a compromised npm publish token to publish an update to Cline CLI on the NPM registry: [email protected]. The published package contains a modified package.json with an added postinstall script: `"postinstall": "npm install -g openclaw@latest"` This causes openclaw (an unrelated, non-malicious open source package) to be globally installed when [email protected] is installed. No other files were modified -- the CLI binary (dist/cli.mjs) and all other package contents are identical to the legitimate [email protected] release. A corrected version (2.4.0) was published at 11:23 AM PT and 2.3.0 was deprecated at 11:30 AM PT. The compromised token has been revoked and npm publishing now uses OIDC provenance via GitHub Actions. ### Impact Users who installed Cline CLI [email protected] during the approximately 8-hour window between 3:26 AM PT and 11:30 AM PT on February 17 will have openclaw globally installed. The openclaw package is a legitimate open source project and is not malicious, but its installation was not authorized or intended. The Cline VS Code extension and JetBrains plugin were not affected. This advisory applies only to the Cline CLI package published on npm. ### Patches Versions 2.4.0 and higher are fixed ### Workarounds If you installed Cline CLI [email protected]: 1. Update to the latest version of the Cline CLI `cline update` or `npm installl -g cline@latest` 2. Verify that you have a fixed version (2.4.0 or higher) `cline --version` 3. Review your environment for any unexpected installation of OpenClaw and remove it if not intended `npm uninstall -g openclaw` ## Source: google-open-source-security (ba9952611b2aa348b1b5cc0349d7b905e32d34effa53081994388c37d0d3462a) An unauthorized party used a compromised npm publish token to publish v2.3.0 of the Cline CLI on the NPM. The compromise added a postinstall script that globally installed openclaw.
- Source published
- 19 Feb 2026 15:17:10 UTC
- Source modified
- 7 Sep 2026 02:15:13 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.