# @ikanngeming/blubub - compromised npm versions

> @ikanngeming/blubub on the npm registry has 1 version flagged in 1 tracked supply-chain incident. Only the exact versions listed below were named by the source advisories. @ikanngeming/blubub 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.

- Package: @ikanngeming/blubub
- Ecosystem: npm
- Highest severity: high
- Kind: Advisory sweep
- Compromised versions: *
- Check what you have installed: `npm ls @ikanngeming/blubub`

## The incident that flagged it

| Date | Severity | Kind | Incident | Versions named |
|---|---|---|---|---|
| 2026-10-13 | high | Advisory sweep | [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)](https://dependencywatch.io/incident/multi-2026-10-13-ghsa-malware-sweep) | * |

## What to do if you installed one of these

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

## Check your whole project

A compromised package is often a transitive dependency rather than one you installed directly. Paste your package-lock.json to check every dependency at once: https://dependencywatch.io/check/package-lock-json

All flagged npm packages: https://dependencywatch.io/package/npm

## Other packages in the same incident

If @ikanngeming/blubub is in your tree, these are worth checking too - they were published by the same campaign.

- [@airbnb-extended/typescript-config](https://dependencywatch.io/package/npm/@airbnb-extended/typescript-config) (npm)
- [@alipclutch/libsignal-node](https://dependencywatch.io/package/npm/@alipclutch/libsignal-node) (npm)
- [@astracode/byles-new](https://dependencywatch.io/package/npm/@astracode/byles-new) (npm)
- [@badzz88/baileys](https://dependencywatch.io/package/npm/@badzz88/baileys) (npm)
- [@badzz88/eslint-config](https://dependencywatch.io/package/npm/@badzz88/eslint-config) (npm)
- [@chatunity/baileys](https://dependencywatch.io/package/npm/@chatunity/baileys) (npm)
- [@dransay/api](https://dependencywatch.io/package/npm/@dransay/api) (npm)
- [@fazzcodestudio/baileys](https://dependencywatch.io/package/npm/@fazzcodestudio/baileys) (npm)
- [@fazzcodestudio/fbot](https://dependencywatch.io/package/npm/@fazzcodestudio/fbot) (npm)
- [@fazzcodestudio/mediaformater](https://dependencywatch.io/package/npm/@fazzcodestudio/mediaformater) (npm)
- [@fazzcodestudio/wa-web](https://dependencywatch.io/package/npm/@fazzcodestudio/wa-web) (npm)
- [@fhkryxv/baileys](https://dependencywatch.io/package/npm/@fhkryxv/baileys) (npm)

Full incident: https://dependencywatch.io/incident/multi-2026-10-13-ghsa-malware-sweep

## Sourcing

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. Corrections: https://dependencywatch.io/submit

---

Canonical page: https://dependencywatch.io/package/npm/@ikanngeming/blubub
Markdown version: https://dependencywatch.io/package/npm/@ikanngeming/blubub.md
Site index for agents: https://dependencywatch.io/llms.txt
DependencyWatch.io is operated by Precursor Security (https://precursorsecurity.com).