DependencyWatch.io
FeedSolutionsSubmitScan your lockfile
Highnpm0 affected versions

snapbuf

snapbuf has 0 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 snapbuf.

    The incident that flagged it

    High

    GitHub Advisory malware sweep - 2026-08-26 batch (PyPI `envprovision` Snow Stealer + PyPI `minecraft-ytreceiver` Telegram-C2 webcam/keylogger + PyPI `python-walletlibr-v` Windows install-time dropper + npm `twork-data-services-*` internal-scope dep-confusion + npm `wm-*` dep-confusion + npm Vue/Svelte/Vite lookalike cluster (15) + npm CWE-506 boilerplate (5))

    28 new GHSA CWE-506 advisories in the 48h window ending 2026-08-26. Highlights: PyPI envprovision drops "Snow Stealer" browser/wallet infostealer with sandbox evasion; PyPI minecraft-ytreceiver runs webcam/screenshot/keylogger over Telegram C2; PyPI python-walletlibr-v fires a Windows batch dropper at pip install; npm twork-data-services-* and wm-* clusters look like internal-namespace dep-confusion probes; a 15-package Vue/Svelte/Vite lookalike cluster and 5 CWE-506 boilerplate names round out the batch.

    Versions named here:

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

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