Open Source · · 1 day
BeProduct npm package carried Shai-Hulud
JFrog listed 1 BeProduct npm package 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
BeProduct entered the May 2026 Shai-Hulud wave through one package with a long version trail. JFrog listed eighteen affected releases of @beproduct/nestjs-auth, all under the BeProduct npm namespace, making the package a compact but high-friction cleanup problem for teams that pinned older 0.1.x builds.
The value of the compromise was proximity. Authentication helper packages run in projects that already handle secrets, identity flows, and deployment credentials. In the Shai-Hulud model, an install on a developer machine or CI runner gave the payload a chance to harvest tokens and use any available publishing authority to seed more packages.
This record keeps the BeProduct artifact separate from the campaign rollup because exposure is package-specific. The campaign page carries TeamPCP's shared loader, credential-theft behavior, and propagation logic; this page preserves the exact package name, release list, registry paths, and May 11-12 window.
The practical response is to look for every affected @beproduct/nestjs-auth version in lockfiles, package caches, CI images, and artifact mirrors. Any environment that installed one of those releases should be treated as a credential-exposure point, even if the application using the package never reached production.
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
10 more versions
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
- Shai-Hulud: Here We Go Again - Worm by TeamPCP Hits NPM and PyPIresearch.jfrog.com
- TanStack npm Packages Compromised in Ongoing Mini Shai-Hulud Supply Chain Attack - Socketsocket.dev
- Mini Shai-Hulud Is Back: npm Worm Hits over 160 Packages, including Mistral and Tanstack - Aikidoaikido.dev
- Retained jsDelivr flat member manifest for @beproduct/nestjs-auth 0.1.16data.jsdelivr.com
- Retained jsDelivr flat member manifest for @beproduct/nestjs-auth 0.1.17data.jsdelivr.com
- Retained jsDelivr flat member manifest for @beproduct/nestjs-auth 0.1.18data.jsdelivr.com
- Triage report for the exact 0.1.16 router_init.js payloadtria.ge
Source record: oss/attacks/shai-hulud-beproduct-npm/meta.yaml