@baanx/common 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. @baanx/common 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 @baanx/common.
GHSA 2026-09-23 (late) + 2026-09-24: ~25 new npm advisories + 1 pip + 1 rubygems. Day 7 of the oob.algamil7x.xyz DNS-OOB operator adds @baanx/common, @baanx/domain, and @insiderintelligence/componentlibrary. vite-dev-launcher@2.9.4 is a mall4cloud-react-RAT sibling of yesterdays @vitemirrorte. internallib_v657/v463` reverse shell to a new RFC1918 subnet.
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 @baanx/common 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.
A small amount of analytics helps us understand how the scanner gets used so we can make it better. Your lockfile scanning still runs entirely in your browser. We never sell or share your data. See our Privacy Policy for details.
You can change your choice later by clearing site data for dependencywatch.io.