npm

The @zakir300408/wechat-companion npm Supply Chain Attack

Updated 18 Nov 2026 · Incident date 15 Nov 2026

GitHub advisory GHSA-gq2c-q5xr-rfpv lists version 0.1.0 of the npm package @zakir300408/wechat-companion as malware, and the registry no longer serves that version.

The npm registry describes the package as a "One-command installer for the private Windows WeChat Companion preview". The advisory gives no technical detail, and the code was unavailable for inspection.

What happened

GitHub marked version 0.1.0 as malware on 18 November 2026, three days after it appeared on npm.

  • The npm account zakir300408 maintains the package. It first appeared at 2026-11-15T14:13:55.245Z as a 0.0.0-stage placeholder.
  • Version 0.1.0 appeared on npm at 2026-11-15T14:30:10.522Z.
  • Versions 0.2.0 to 0.6.0-preview.2 followed the same day. The last appeared at 2026-11-15T18:18:02.455Z.
  • GitHub published and reviewed advisory GHSA-gq2c-q5xr-rfpv on 18 November 2026. It lists CWE-506, Embedded Malicious Code, for version 0.1.0.
  • The registry no longer lists 0.1.0 among the package versions.

Affected versions

  • @zakir300408/wechat-companion 0.1.0, per the advisory range = 0.1.0.
  • The advisory lists no patched version.
  • The advisory does not list 0.2.0, 0.3.0, 0.4.0, 0.5.0 or 0.6.0-preview.2. These versions stay on the registry.

Indicators of compromise

  • Package: @zakir300408/wechat-companion
  • Version: 0.1.0
  • Advisory: GHSA-gq2c-q5xr-rfpv

How to check

List the package in each project and look for version 0.1.0.

npm ls @zakir300408/wechat-companion --all

List a global install of the package and look for version 0.1.0.

npm ls -g @zakir300408/wechat-companion

What to do now

If a computer installed 0.1.0, the advisory says to treat it as fully compromised.

  1. Use a different, clean computer for the next steps.
  2. Rotate every secret and key that the affected computer held.
  3. Remove the package and its lockfile entry.
  4. Removal alone does not prove that the computer is clean. If you cannot prove it is clean, rebuild it.

What Vigilance would show

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

Example install message

Vigilance blocked `@zakir300408/wechat-companion` 0.1.0. This version is too new or changed in a way Vigilance must check first.

Example owner report

Bad update

@zakir300408/wechat-companion 0.1.0

GitHub lists version 0.1.0 of this npm package as malware and says that a computer that installed it is fully compromised.

See what to do now.

No security team? See who reads the alert.

Frequently asked questions

Is @zakir300408/wechat-companion safe to use?

GitHub lists version 0.1.0 as malware. The advisory does not name any other version.

What did @zakir300408/wechat-companion 0.1.0 do?

The GitHub advisory does not say. The registry no longer serves 0.1.0, so the code was unavailable for inspection.

Sources

  1. github.com/advisories/GHSA-gq2c-q5xr-rfpv
  2. registry.npmjs.org/@zakir300408%2fwechat-companion

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