HighAdvisory sweepnpm1 affected version

whalibmob

whalibmob has 1 version on the npm registry flagged in 1 incident we track. Only the exact versions listed below were named by the source advisories.

whalibmob 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 whalibmob.

whalibmob@>=5.24.0 <=5.33.5

The incident that flagged it

High2 Oct 2026

GitHub Advisory malware sweep - 2026-10-01 (late) + 2026-10-02 (npm Baileys silent WhatsApp follow mass batch, 15 siblings sharing query ID `7871414976211147`: `@xayz/baileys`, `xvinleys`, `yonzoffic-baileys`, `xzbails`, `xzvexpzcbailey`, `yonzofficial`, `kiyoramarkets`, `kasabaileys`, `my-baileys`, `lilys-baileys`, `noxleyss`, `syncxbails`, `whalibmob`, `ishumdz-bail`, `eliteprotech-baileys`; pip `spo365-graph` NEW campaign - AWS Lambda deploy + AWS Secrets Manager credential theft; pip `friendly-tools` Snowflake credential-theft `friendly-greeting-tools` family continuation; pip `shortneer` Chrome-extension crypto-wallet + Telegram infostealer (`sherpy` campaign continuation); npm `future-scripts` browser DoS `boom()` time-bomb detonating 2026-10-10; npm `online-header@99.0.0` sentinel-version malicious-domain beacon; 5 npm CWE-506 boilerplate takedowns `illusion-datalab`, `homestack-cheer`, `kartykgithub-ph-f`, `kartykgithub-ph-e`, `kartykgithub-ph-b`)

GHSA 2026-10-01 (late) + 2026-10-02: 26 new advisories (23 npm + 3 pip). Confirmed payloads: 15 npm Baileys silent-WhatsApp-follow siblings (jexkcode/noverojs family); pip spo365-graph AWS Lambda + Secrets Manager credential theft (new); pip friendly-tools Snowflake exfil; pip shortneer Chrome-wallet stealer; npm future-scripts browser DoS time-bomb set for 2026-10-10.

Versions named here: >=5.24.0 <=5.33.5

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.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
2.Pin to a version not listed above, then reinstall from a clean lockfile.
3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
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

whalibmob 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.

Check my package-lock.json All flagged npm packages

Other packages in the same incident

If whalibmob 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.