Open Source · · 1 day

DraftLab npm packages carried Shai-Hulud

JFrog listed 3 DraftLab 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

DraftLab's Shai-Hulud exposure spanned three related npm packages: @draftlab/auth, @draftlab/auth-router, and @draftlab/db. JFrog listed six affected releases across that small package family during the May 11-12 TeamPCP wave.

The grouping is important. A developer who installed one DraftLab component could plausibly install the others in the same project or CI job, putting the malware inside an environment already handling authentication and database integration. Shai-Hulud used that kind of install-time access to harvest secrets and search for new package-publishing authority.

This record keeps the DraftLab namespace as its own trust boundary. The campaign page carries the shared TeamPCP mechanics; this page preserves the exact package names, affected releases, registry distribution paths, and response window needed for inventory searches.

Defenders should treat the listed packages as exposure indicators, not just vulnerable dependencies. A match in a build log, package cache, or lockfile means the install environment deserves credential rotation and a review of any packages it could publish during or after the compromise window.

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

@draftlab/auth npm
0.24.2 sha256 a1bf23cf…e7a96e94 download unavailable
0.24.1 sha256 1b0fbc82…685c3cb7 download unavailable
@draftlab/db npm
0.16.2 sha256 6e83cb32…f39725eb download unavailable
0.16.1 sha256 a12479a3…2d83c444 download unavailable

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 @draftlab/auth 0.24.1socket.dev
  5. Socket retained file listing for @draftlab/auth 0.24.2socket.dev
  6. Socket retained file listing for @draftlab/auth-router 0.5.1socket.dev
  7. Socket retained file listing for @draftlab/auth-router 0.5.2socket.dev
  8. Socket retained file listing for @draftlab/db 0.16.1socket.dev
  9. Socket retained file listing for @draftlab/db 0.16.2socket.dev

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