Taskflow Corp npm package carried Shai-Hulud

Taskflow Corp appeared in the May 2026 Shai-Hulud wave through @taskflow-corp/cli. JFrog listed six affected npm releases, all within the campaign's May 11-12 package-publishing window.

A CLI package is a direct route into developer and automation environments. It can be installed globally, pulled into CI images, or run during build setup, which puts it near npm tokens, GitHub credentials, cloud configuration, and local secrets. That is the environment Shai-Hulud was built to mine.

This record keeps the Taskflow Corp package separate from the aggregate campaign count. The campaign page explains the shared loader and self-propagation machinery; this page preserves the package name, version set, registry URLs, and dates for inventory and cleanup.

A matching install should be handled as an install-time compromise, not merely a vulnerable library import. Any host or runner that resolved the affected @taskflow-corp/cli versions should have its credentials rotated and its subsequent package-publishing activity reviewed.

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