coa 2.0.3 and five later versions on npm started a hidden program that fetched a password-stealing file, after a hijack on 4 November 2021.
The same attacker also hijacked the rc package. The last good coa version is 2.0.2.
What happened
An attacker published malicious versions of coa after the maintainers lost control of the package.
- The first bad version went live on 4 November 2021 at 14:12 CET. npm removed it at 15:24 CET.
- It added a preinstall script that starts
compile.jsin the background at install. - Rapid7 reports that the malware steals credentials.
- Rapid7 says the
rcvariant targets Windows. - Dependent packages such as
@svgr/clifailed withCannot find module '/...coa/compile.js'.
Affected versions
coa: 2.0.3, 2.0.4, 2.1.1, 2.1.3, 3.0.1, 3.1.3.- Safe
coaversion: 2.0.2. rc: 1.2.9, 1.3.9, 2.3.9.- Safe
rcversion: 1.2.8.
Indicators of compromise
compile.js.compile.bat.sdd.dll.- A
preinstallscript incoathat runsnode compile.js.
How to check
Show which coa and rc versions your tree resolves, including transitive dependencies.
npm ls coa rc
Search lockfiles for the bad versions.
grep -rE '"(coa|rc)"' package-lock.json yarn.lock pnpm-lock.yaml 2>/dev/null
What to do now
- Pin
coato 2.0.2 andrcto 1.2.8 with resolutions or overrides. Deletenode_modulesand reinstall from a clean lockfile. - If a machine installed an affected version, treat it as fully compromised. Look for
compile.js,compile.batandsdd.dllon it. - Rotate all credentials, tokens and keys that the machine stored, from a different clean computer.
What Vigilance would show
These examples show an install hold and the corresponding owner report.
Example install message
Vigilance blocked `coa` 2.0.3. This version is too new or changed in a way Vigilance must check first.
Example owner report
Bad update
coa 2.0.3
Installing this library now started a hidden program that fetched and ran a password-stealing file from the internet.
No security team? See who reads the alert.
Frequently asked questions
Is there a CVE?
No. GitHub advisory GHSA-73qr-pfmq-6rp8 rates it critical under CWE-506 and tells users to downgrade to 2.0.2.
Is a clean file search enough?
No. A clean search does not prove that a machine is safe if it installed an affected version.
Sources
Send this page to the person who looks after AI at your company.