npm

The conventional-changelog Supply Chain Attack

Updated 5 Oct 2026 · Incident date 12 Feb 2018

conventional-changelog 1.2.0 on npm downloaded and ran a hidden Monero miner after attackers took a maintainer's logins in February 2018.

Attackers got the logins of a package maintainer and published version 1.2.0 in February 2018. Version 1.1.11 was the last clean release before it.

What happened

Attackers used stolen npm logins to publish a malicious conventional-changelog 1.2.0.

  • Sonatype wrote about it on 14 February 2018 and says the version allegedly included a Monero miner.
  • Anyone who installed it possibly ran a miner.
  • The record says the 1.2.0 tarball gained the ability to write a binary to disk and run it during install.
  • A user opened issue 282 on 13 February 2018 to ask what the version did.
  • The maintainers later unpublished the version.

Affected versions

  • conventional-changelog 1.2.0: malicious, later unpublished.
  • conventional-changelog 1.1.11: the last clean release before it.
  • Tools such as Lerna and standard-version use this package, so check them as well.

Indicators of compromise

  • conventional-changelog version 1.2.0 in a lockfile or node_modules.
  • An unexpected cryptocurrency mining process on a build machine.
  • High CPU use after an install of the package.

How to check

List the installed version in your dependency tree.

npm ls conventional-changelog

Search lockfiles for the bad version.

grep -rn -A1 '"conventional-changelog"' package-lock.json yarn.lock 2>/dev/null | grep 1.2.0

What to do now

  1. Update to a later release and reinstall from a clean lockfile.
  2. If a build machine installed 1.2.0, look for an unknown mining process and remove it.
  3. Change the passwords and keys that machine held, including npm tokens.
  4. If you publish packages, check if you shipped the bad version to your own users. Turn on two-factor authentication on your npm account.

What Vigilance would show

These examples show an install hold and the corresponding owner report.

Example install message

Vigilance blocked `conventional-changelog` 1.2.0. This version is too new or changed in a way Vigilance must check first.

Example owner report

Bad update

conventional-changelog 1.2.0

Using the library now downloaded a hidden coin-mining program onto the machine and ran it in the background.

See what to do now.

No security team? See who reads the alert.

Frequently asked questions

Which conventional-changelog version was malicious?

Version 1.2.0. The maintainers later unpublished it.

Did issue 282 explain what the version did?

No. The issue page holds the question and not the answer.

Sources

  1. sonatype.com/blog/malicious-intent-open-source-developers-please-protect-your-users
  2. github.com/conventional-changelog/conventional-changelog/issues/282

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