Criticalnpm2 affected versions

@cats-cdf/authentication

@cats-cdf/authentication has 2 versions on the npm registry flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with npm ls @cats-cdf/authentication.

@cats-cdf/authentication@3.1.1
@cats-cdf/authentication@2.17.1

The incident that flagged it

Critical7 Aug 2026

GitHub Advisory npm CWE-506 sweep - 33+ package 2026-08-07 batch (`remote-claude-daemon` full-desktop RAT via WebSocket relay + baileys-clone WhatsApp bot cluster + `@cats-cdf/*` OAST recon pair + `internallib_v514` internal LAN reverse-shell + `wormgpt-cli` LLM-branded RAT + `@united-airlines-org/atmos-design-system` dep-confusion + `@ks-video/kwai-player-web` telemetry beacon + `@avi892nash/aegis-grid-runner` Juspay-leaked internal RCE tool + `@junyoung-kim/reins` PTY-reverse-shell with systemd persistence + `noviembrenacional.com` WordPress-CSRF nuke pair + long tail)

GHSA published 33+ npm CWE-506 advisories dated 2026-08-07 spanning several clusters: remote-claude-daemon (Claude Code full-desktop RAT with screen + mic capture via WebSocket relay, 20 versions), a 4-package baileys-clone WhatsApp bot cluster (@prototypevip/baileys, diezyclutch-baileys, ynastore-baileys, and more), @cats-cdf/* OAST dep-confusion recon, internallib_v514 reverse-shell to hardcoded 10.0.70.90 (continuation of internallib_v<NNN> campaign), wormgpt-cli (LLM-branded RAT with clipboard theft), @united-airlines-org/atmos-design-system dep-confusion, @ks-video/kwai-player-web telemetry beacon, @avi892nash/aegis-grid-runner (leaked-internal-Juspay RCE tool), @junyoung-kim/reins (PTY reverse-shell with systemd persistence), and xxdxax+xdaxx (targeted WordPress CSRF/account-nuke against noviembrenacional.com).

Versions named here: 2.17.1, 3.1.1

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

@cats-cdf/authentication 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 @cats-cdf/authentication 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.