npm

The @zetagoaurum-socket/wasocket npm Malware

Updated 20 Nov 2026 · Incident date 29 Jan 2026

All 16 releases of the @zetagoaurum-socket/wasocket WhatsApp library are malware, and npm has removed the code.

GitHub reviewed and published the malware advisory on 20 November 2026. npm replaced the package with a security holding release the same day.

What happened

A GitHub reviewed advisory marks every release of @zetagoaurum-socket/wasocket, a WhatsApp API library, as malicious code.

  • The advisory covers 16 versions, from 2.1.0 to 3.2.7.
  • It gives no payload details. Its guidance says every computer that ran the package is fully compromised.
  • npm replaced the package with a 0.0.1-security holding release on 20 November 2026 and removed the original code.
  • The code was unavailable for inspection, so this page reports only advisory and registry facts.

Affected versions

  • The advisory flags 2.1.0 through 3.2.7. All 16 releases appeared on 29 and 30 January 2026.
  • The registry now serves 0.0.1-security, a placeholder held by npm support.

Indicators of compromise

  • The advisory lists no hashes, domains, addresses or file names.
  • The removed code was unavailable for inspection, so no indicators can be added here.

How to check

Run this in each project that uses the package.

npm ls @zetagoaurum-socket/wasocket

Check lockfile history and past build logs for any install of @zetagoaurum-socket/wasocket between 29 January 2026 and 20 November 2026. A clean install today cannot rule out earlier exposure.

What to do now

  1. Treat every computer that installed or ran the package as fully compromised.
  2. Rotate all secrets and keys stored on it, from a different computer.
  3. Remove the package and rebuild from a clean package set.
  4. Review account and cloud logs for use of the exposed credentials.

What Vigilance would show

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

Example install message

Vigilance blocked `@zetagoaurum-socket/wasocket` 3.2.7. This version is too new or changed in a way Vigilance must check first.

Example owner report

Bad update

@zetagoaurum-socket/wasocket 3.2.7

A WhatsApp bot library carried malware. GitHub says every computer that ran it must be treated as fully compromised.

See what to do now.

No security team? See who reads the alert.

Frequently asked questions

Is @zetagoaurum-socket/wasocket the real WhatsApp Baileys library?

No. It is a separate npm package that builds on Baileys code. The advisory covers @zetagoaurum-socket/wasocket only.

Can I still install the malicious versions?

No. npm replaced the package with a security holding release and removed the original code.

What did the malware do?

The advisory gives no technical detail. npm removed the code, so it cannot be inspected. The advisory guidance treats affected computers as fully compromised.

Sources

  1. github.com/advisories/GHSA-wqcq-qg5g-jm7r
  2. registry.npmjs.org/@zetagoaurum-socket/wasocket

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