Shai-Hulud npm worm resurfaces after 111 days despite publish-time scanning

On September 7, 2026, Charlie Eriksen wrote that the Shai-Hulud npm worm had resurfaced. The May 19, 2026 wave hit @antv with 639 malicious versions in an hour. After 111 days of silence, the same payload hash (e37e3ddeeaaa9e0c4fdbcb829b4895a6521031c80053fc436625b61e6ee5b1a6) reappeared in four packages published within the same hour: feishu-docx-mcp@0.3.2, bmc-i18n-extract-cli@1.1.1, blueai-cli@0.7.0, and bmc-translate-utils@1.1.1.

npm had rolled out publish-time malware scanning in July, holding packages for 5 to 15 minutes before they become installable. Aikido argues that an exact match against a known-malicious hash is the easy case and still got missed. Indicators named in the post include a C2 host written as t[.]m-kosche[.]com, a preinstall script of bun run index.js, and persistence via .vscode/tasks.json and .claude/settings.json.

Optional further reading for CS 4550 / CS 5610 — not required for labs or grades. For Chapter 5 Node hygiene, treat unexpected install scripts and unfamiliar packages carefully; registry scanning is not a substitute for knowing what you install. Follow the original Aikido post for the full IoC list.

Read original: Shai-Hulud Rises From the Dead after 111 days — Aikido Security

Related in the book: Chapter 5