Open Source · · 1 day

DraftAuth npm packages carried Shai-Hulud

JFrog listed 2 DraftAuth npm packages in the May 2026 Shai-Hulud wave. This record scopes those artifacts to their own official distribution surface.

Part of Shai-Hulud hits npm and PyPI campaign

DraftAuth was a two-package slice of the May 2026 Shai-Hulud wave. JFrog listed malicious releases for @draftauth/client and @draftauth/core, giving the attacker both a client-facing package name and a core library surface inside the same npm namespace.

That namespace matters because authentication packages tend to live near secrets. Even when a package is only installed during build or test, the environment often contains npm tokens, GitHub credentials, cloud configuration, and service keys. Shai-Hulud's value came from harvesting that context and using any publisher access it found to continue the spread.

This page separates DraftAuth from the campaign aggregate so responders can answer a package-level question: did any system install the listed DraftAuth releases during the May 11-12 window? The broader campaign record explains TeamPCP's shared loader, infrastructure, and self-propagation behavior.

Cleanup should follow the installation path, not just the application dependency graph. Lockfiles, CI caches, local npm caches, and artifact mirrors can all prove exposure. Any matching environment should be treated as a potential credential source and reviewed before new packages are published from it.

Notes

  • The network and payload indicators are the campaign-level set JFrog published for this wave, not observations of this package's own bytes. They identify the wave's infrastructure and persistence, and are recorded here so each affected distribution surface carries them. Where a record also lists indicators read from an acquired sample, those are marked as such.
  • Minimal campaign-linked record created to keep Shai-Hulud package evidence scoped by vendor, organization, maintainer account, or package distribution surface.

Appendix · Affected releases

Indicators

  • file_sha256npm payload 29c729852fce5a53e30a1541d9fec79c915b2e13f1eda94a5978cf0aae0d88d9
  • file_sha256npm payload 2ec78d556d696e208927cc503d48e4b5eb56b31abc2870c2ed2e98d6be27fc96
  • file_sha256npm payload ab4fcadaec49c03278063dd269ea5eef82d24f2124a8e15d7b90f2fa8601266c
  • file_sha256npm payload d4a2086ea18f5e39cd867b8b06918a524eabb21d45ea98aad07357b98173458a
  • urlhttps://filev2.getsession.org/file/
  • domainseed1.getsession.org
  • domainseed2.getsession.org
  • domainseed3.getsession.org
  • domainapi.masscan.cloud
  • file~/.local/bin/gh-token-monitor.sh
  • file~/.config/systemd/user/gh-token-monitor.service
  • file~/Library/LaunchAgents/com.user.gh-token-monitor.plist
  • file~/.config/gh-token-monitor/
  • stringShai-Hulud: Here We Go Again
  • stringPUSH UR T3MPRR
  • stringFIRESCALE
  • commit_authorclaude@users.noreply.github.com

References

  1. Shai-Hulud: Here We Go Again - Worm by TeamPCP Hits NPM and PyPIresearch.jfrog.com
  2. TanStack npm Packages Compromised in Ongoing Mini Shai-Hulud Supply Chain Attack - Socketsocket.dev
  3. Mini Shai-Hulud Is Back: npm Worm Hits over 160 Packages, including Mistral and Tanstack - Aikidoaikido.dev
  4. Socket retained file listing for @draftauth/client 0.2.1socket.dev
  5. Socket retained file listing for @draftauth/client 0.2.2socket.dev
  6. Socket retained file listing for @draftauth/core 0.13.1socket.dev
  7. Socket retained file listing for @draftauth/core 0.13.2socket.dev

Source record: oss/attacks/shai-hulud-draftauth-npm/meta.yaml