Tolka npm package carried Shai-Hulud

Tolka was represented in the May 2026 Shai-Hulud wave by @tolka/cli. JFrog listed five affected npm releases, making the package another command-line distribution path for TeamPCP's credential-stealing loader.

CLI packages are valuable because they run where developers and CI systems prepare work. The affected Tolka releases could execute in environments holding npm publish tokens, GitHub credentials, cloud secrets, SSH keys, and other material the worm could use to spread.

This record keeps the Tolka package scoped to its own trust boundary. The broader campaign page carries the shared TeamPCP tooling, infrastructure, and propagation behavior; this page preserves the exact package name, affected versions, registry locations, and May 11-12 exposure window.

The cleanup workflow is package-led: search lockfiles, caches, build images, and CI logs for the listed @tolka/cli versions, then rotate credentials for any environment that installed them and review whether that environment published packages afterward.

Motive

Credential Theft

Attribution

Group

Cause

Compromised Account Credentials

Transitive

Yes

Actor

TeamPCP

• Minimal campaign-linked record created to keep Shai-Hulud package evidence scoped by vendor, organization, maintainer account, or package distribution surface.

• Shai-Hulud: Here We Go Again - Worm by TeamPCP Hits NPM and PyPIresearch.jfrog.com