npm

The coa npm Supply Chain Attack

Updated 5 Oct 2026 · Incident date 4 Nov 2021

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.js in the background at install.
  • Rapid7 reports that the malware steals credentials.
  • Rapid7 says the rc variant targets Windows.
  • Dependent packages such as @svgr/cli failed with Cannot 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 coa version: 2.0.2.
  • rc: 1.2.9, 1.3.9, 2.3.9.
  • Safe rc version: 1.2.8.

Indicators of compromise

  • compile.js.
  • compile.bat.
  • sdd.dll.
  • A preinstall script in coa that runs node 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

  1. Pin coa to 2.0.2 and rc to 1.2.8 with resolutions or overrides. Delete node_modules and reinstall from a clean lockfile.
  2. If a machine installed an affected version, treat it as fully compromised. Look for compile.js, compile.bat and sdd.dll on it.
  3. 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.

See what to do now.

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

  1. github.com/advisories/GHSA-73qr-pfmq-6rp8
  2. github.com/veged/coa/issues/99
  3. rapid7.com/blog/post/2021/11/05/new-npm-library-hijacks-coa-and-rc/

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · npm supply chain attacks · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library