@xatancchii/natabaileys 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. @xatancchii/natabaileys 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.
If one is in your tree, treat the machine as compromised, not just out of date.
Version data comes from the public advisories cited on each incident page.
Check what you actually have installed with npm ls @xatancchii/natabaileys.
GHSA 2026-10-16/17 batch (19 advisories). Legacy itsa-react-* maintainer compromise finally indexed. conx3993 operator wave 2 adds 4 realwbx.com beacon packages. @flexmr dep-confusion wave 2 pivots to artifacts.creditslib.com bare-URL deps. 7-package @beloved-lenora/opencode-* AI-coding-tool lure. PyPI marocolor Telegram-bot stealer + fromthehotel-poems LLM-threat.
Treat the machine as compromisedUpgrading is not enough. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.
If @xatancchii/natabaileys is in your tree, these are worth checking too. They were published by the same campaign.
Version data comes from the public advisories cited on each incident page. We list only versions those advisories name and do not infer additional ones. Think this is wrong or incomplete? Tell us.
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.