Highnpm1 affected version

kit-hydration-vim

kit-hydration-vim has 1 version 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 kit-hydration-vim.

kit-hydration-vim@1.0.0

The incident that flagged it

High15 Aug 2026

GitHub Advisory npm CWE-506 sweep - 2026-08-15 batch (`@velliajs/discord` `discord.js` impersonator with hardcoded GitHub PAT + hidden `_verifyAuthorization` kill-switch, `akamai(js)-sensor` Google-Calendar invisible-Unicode C2 trio, HackerOne/Twilio `-probe`/`-poc` bug-bounty-canary droppers with live payloads, `depcruise-` + `gunzip-js` `99.9.1` dependency-confusion canary, `@wololasod/tiny-id` RC4 Windows/Linux dropper, `@finaxis/common-js` Xelis miner, `-vim` naming-canary pair, plus IP/webhook exfiltrators)

22 npm CWE-506 advisories published 2026-08-15 - the day's headline is @velliajs/discord@1.0.3..1.0.7, a discord.js impersonator with two live hardcoded GitHub PATs, an unpinned private-repo sysframe dependency the operator can hot-swap, and a hidden Client.login() _verifyAuthorization allowlist kill-switch. Same-day clusters include a 3-package akamai(js)-sensor Google-Calendar-dead-drop trio using invisible-Unicode payloads, HackerOne/Twilio *-probe/*-poc bug-bounty-canary droppers with real credential exfil, a depcruise-* + gunzip-js 99.9.1 OpenSSF-domain-flagged canary group, @wololasod/tiny-id RC4 dropper, @finaxis/common-js Xelis miner, adxaa WordPress account-takeover, and a matching *-vim naming-canary pair.

Versions named here: 1.0.0

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

kit-hydration-vim 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 kit-hydration-vim 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.