HighAdvisory sweepnpm2 affected versions

alipclutch-baileys

alipclutch-baileys has 2 versions on the npm registry flagged in 2 incidents we track. Only the exact versions listed below were named by the source advisories.

alipclutch-baileys was recorded in a daily advisory sweep. The write-up groups it into a cluster with the evidence available at the time; check the cluster note before treating it as a confirmed compromise.

Affected versions

Check what you actually have installed with npm ls alipclutch-baileys.

  • alipclutch-baileys@1.0.0
  • alipclutch-baileys@*

The 2 incidents that flagged it

High

GitHub Advisory malware sweep - 2026-10-13 (**Baileys/libsignal lure operator wave 3** - 60+ npm packages across `@revizahoshii/*`, `@fazzcodestudio/*`, `@sanzoffc/*`, `@wanzlonely/*`, `@mikudeveloper/*`, `@modss/*`, `@ikanngeming/*`, `@fhkryxv/*`, `@saazkira/*`, `@badzz88/*`, `@alipclutch/*`, `@mivesensei/*`, `@kanaraa/*`, `@chatunity/*`, `@zanta/*`, `@yudzxml/*`, `@zeronexcode/*`, plus `baileys-xbats`/`bailslonely`/`nakkinpm`/`amprem` unscoped - all CWE-506 boilerplate takedowns against `@WhiskeySockets/Baileys` WhatsApp-automation lures; **confirmed-payload carve-outs within the sweep**: PyPI `npp-ml` Notepad++ impersonator deploying ADExplorer AD-recon tool, PyPI `minecraftaccfinder` Gmail/Roblox/Discord/Minecraft infostealer+RAT with keylogger/screenshots/browser-creds, RubyGems `wallet-balance-scanner` fake-native-extension reverse-shell to hardcoded endpoint; **s4yhii wave 3 continuation** `@s4yhiitestpoc/r2-https-b` on `collector.oob.s4yhii.com`; plus 25+ dep-confusion probes at `99.x`/`100.x`/`101.x` sentinels: `@myorder-frontend-commons/*`, `risk-detection`, `unified-platform`, `@pinecone-experience/*`, `@airbnb-extended/*`, `@tesla-insurance/*`, `@user-services/*`, `app-sca-info-banking`, `com.apple.unityplugin.storekit` Apple-brand impersonator, and more)

GHSA 2026-10-12 batch (ingested 2026-10-13): ~90 fresh malware advisories, dominated by a Baileys/libsignal lure operator wave 3 of 60+ WhatsApp-automation-brand typosquats (continuation of 2026-10-10 Cluster C). Confirmed payloads: PyPI npp-ml Notepad++ impersonator deploying ADExplorer, PyPI minecraftaccfinder multi-platform infostealer+RAT, RubyGems wallet-balance-scanner fake-native-extension reverse shell. Plus @s4yhiitestpoc/r2-https-b continuing s4yhii wave 3 and 25+ dep-confusion sentinel probes.

Versions named here: *

High

GitHub Advisory npm CWE-506 sweep - 50+ package 2026-08-06 batch (Sui-blockchain `sui-migration-audit-*` + `move-bcs-codec` cluster, `@activepieces/piece-*` typosquat sweep, `@ccfly/setup-*` platform-binary quartet, `@addai/*` cluster, `claude-remote-agent` RAT, `diezyyasha-baileys` + `alipclutch-baileys` WhatsApp cluster, `@holocronlab/botruntime-runtime` bot-framework masquerade, `helmet-pro` + `agenttunnels` + `agenthub-multiagent-mcp` + `typst-resume-cli` misc)

GHSA published 50+ npm CWE-506 advisories dated 2026-08-06 spanning several clusters: Sui blockchain tooling (sui-migration-audit-cli, sui-graphql-client, sui-migration-audit-rules, move-bcs-codec), an @activepieces/piece-* typosquat sweep (piece-google-contacts, piece-google-bigquery, piece-google-forms, piece-base44), a @ccfly/setup-* platform-binary quartet (darwin-arm64, darwin-x64, linux-arm64, linux-x64), an @addai/* cluster (ainode, node, entity-runtime), claude-remote-agent RAT, WhatsApp diezyyasha-baileys + alipclutch-baileys sibling clones, @holocronlab/botruntime-runtime bot framework masquerade, and a long tail of enterprise-scope dep-confusion probes.

Versions named here: 1.0.0

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

  1. 1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
  2. 2.Pin to a version not listed above, then reinstall from a clean lockfile.
  3. 3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
  4. 4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

alipclutch-baileys is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. Paste your package-lock.json to check every dependency at once - it runs in your browser and nothing is uploaded.

Other packages in the same incident

If alipclutch-baileys is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.