npm

The @kropaku/baileys npm Malware

Updated 20 Nov 2026 · Incident date 16 Nov 2026

Five releases of the @kropaku/baileys WhatsApp library carry a hidden external host in outgoing message code.

GitHub reviewed and published the malware advisory on 20 November 2026. npm still serves every affected release.

What happened

A GitHub reviewed advisory, credited to the OpenSSF malicious packages project, marks @kropaku/baileys, a WhatsApp Web library, as malicious code.

  • The advisory flags 6.7.20, 6.7.21, 6.7.22, 6.7.23 and 6.7.24.
  • In the inspected versions, lib/Socket/messages-send.js sets the sourceUrl of rich image and video messages to a host built from character codes.
  • That byte array decodes to https://fiora.nixel.my.id/. Each rich image or video message the library sends carries this third-party host as its source link.
  • The same releases ship lib/Utils/license-guard.js, an obfuscated license check with mangled names such as _0x1e6253 and _0x5d89.
  • This page inspected 6.7.20, 6.7.23 and 6.7.24 and found the hidden host in all three. The advisory calls the setup a covert data relay or credential and session exfiltration.

Affected versions

  • 6.7.20 appeared on 16 November 2026 and is the first release the advisory flags.
  • The advisory flags 6.7.20 through 6.7.24.
  • npm still lists 6.7.24 as the latest release and has not removed the code.
  • 6.7.19 is the last release before the flagged run.

Indicators of compromise

  • https://fiora.nixel.my.id/
  • lib/Socket/messages-send.js
  • lib/Utils/license-guard.js

How to check

Run this in each project that uses the package.

npm ls @kropaku/baileys

The host string is not plain text in the file. The message code builds it from character codes, so search for the start of that array.

grep -c "String.fromCharCode(104, 116, 116, 112" node_modules/@kropaku/baileys/lib/Socket/messages-send.js

Check lockfile history and past build logs for any install of 6.7.20 through 6.7.24 since 16 November 2026. A clean install today cannot rule out earlier exposure.

What to do now

  1. Stop the WhatsApp bot runtime that runs the package.
  2. Treat the WhatsApp session credentials on that host as exposed and relink the session from a clean device.
  3. Remove the package and rebuild from a clean package set.
  4. Review network and message logs for fiora.nixel.my.id.

What Vigilance would show

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

Example install message

Vigilance blocked `@kropaku/baileys` 6.7.20. This version is too new or changed in a way Vigilance must check first.

Example owner report

Bad update

@kropaku/baileys 6.7.20

A WhatsApp bot library stamps outgoing rich messages with a hidden outside host and ships an obfuscated license module.

See what to do now.

No security team? See who reads the alert.

Frequently asked questions

Is @kropaku/baileys the official Baileys library?

No. It is a separate npm package that forks the Baileys code. The advisory covers @kropaku/baileys only.

Can I still install the affected versions?

Yes. npm has not removed them and still lists 6.7.24 as the latest release.

What did the code do with the hidden host?

The inspected code sets the sourceUrl of rich image and video messages to https://fiora.nixel.my.id/. The advisory describes the setup as covert data relay or credential and session exfiltration.

Sources

  1. github.com/advisories/GHSA-g4vg-qmwm-vh4c
  2. registry.npmjs.org/@kropaku/baileys
  3. registry.npmjs.org/@kropaku/baileys/6.7.20

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