{"id":8792,"date":"2025-11-28T10:03:47","date_gmt":"2025-11-28T10:03:47","guid":{"rendered":"https:\/\/serisec.com\/index.php\/2025\/11\/28\/shai-hulud-2-0-compromises-1200-organizations-exposing-critical-runtime-secrets\/"},"modified":"2025-11-28T10:03:47","modified_gmt":"2025-11-28T10:03:47","slug":"shai-hulud-2-0-compromises-1200-organizations-exposing-critical-runtime-secrets","status":"publish","type":"post","link":"https:\/\/serisec.com\/index.php\/2025\/11\/28\/shai-hulud-2-0-compromises-1200-organizations-exposing-critical-runtime-secrets\/","title":{"rendered":"Shai Hulud 2.0 Compromises 1,200+ Organizations, Exposing Critical Runtime Secrets"},"content":{"rendered":"

Shai Hulud 2.0 Compromises 1,200+ Organizations, Exposing Critical Runtime Secrets
\n \t

\n
<\/BR>
\n
\n \t

\n
<\/BR><\/p>\n

\n

The Shai Hulud 2.0<\/a> worm, first detected on November 24, 2025, has compromised nearly 1,200 organizations, including major banks, government bodies, and Fortune 500 technology firms.<\/p>\n

While initial reports described it as a simple npm supply chain attack that flooded GitHub with spam repositories, new analysis reveals a far more sophisticated operation. <\/p>\n

Entro Security researchers observed<\/a> that the malware did not just create noise; it successfully exfiltrated sensitive runtime memory and credentials from deep within corporate CI\/CD pipelines<\/a>.<\/p>\n

Early analysis focused on the thousands of attacker-controlled GitHub repositories generated by the worm. However, researchers at Entro Security have confirmed that these repositories were merely the \u201ccollection layer\u201d for a much larger heist.<\/p>\n

The true damage occurred inside the victim environments, developer endpoints, cloud build servers, and self-hosted GitHub runners, where the malware executed payload scripts during the \u201cpreinstall\u201d phase of compromised npm packages.<\/p>\n

Instead of just scraping static files, Shai Hulud 2.0 captured full runtime environments. Entro Security analysis found that the generated artifacts, like environment.json, contained double-base64-encoded memory snapshots.<\/p>\n

\n
\"Shai
Shai Hulud 2.0 Double-encoded memory Snapshots<\/figcaption><\/figure>\n<\/div>\n

These snapshots allowed attackers to reconstruct the exact state of compromised machines, granting them access to in-memory secrets that never appeared in code repositories.<\/p>\n

The scale of the compromise is staggering. Entro researchers identified 1,195 distinct organizations by analyzing email domains, internal hostnames, and tenant identifiers found in the exfiltrated data.<\/p>\n

\n
\"organizations
organizations Impacted (Credits: Entro)<\/figcaption><\/figure>\n<\/div>\n

Technology and SaaS companies suffered the most from the attack, representing over half of the identified victims.<\/p>\n

\n\n\n\n\n\n\n\n\n\n\n\n
Industry Sector<\/th>\nNumber of Compromised Orgs<\/th>\n<\/tr>\n<\/thead>\n
Technology \/ SaaS<\/strong><\/td>\n647<\/strong><\/td>\n<\/tr>\n
Financial Services & Banking<\/td>\n53<\/td>\n<\/tr>\n
Healthcare<\/td>\n38<\/td>\n<\/tr>\n
Insurance<\/td>\n26<\/td>\n<\/tr>\n
Media<\/td>\n21<\/td>\n<\/tr>\n
Telecom<\/td>\n20<\/td>\n<\/tr>\n
Logistics<\/td>\n15<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

Two specific examples highlight the severity of the breach. The first involved one of the world\u2019s largest semiconductor companies, where a self-hosted GitHub Actions runner was compromised.<\/p>\n

The decoded memory dump exposed active GitHub Personal Access Tokens<\/a> and internal hostnames, proving the attackers had valid entry points into the company\u2019s internal infrastructure.<\/p>\n

The second victim was a Tier-1 digital asset custody provider. In this case, the malware struck a GitLab CI pipeline. The exfiltrated data included live AWS secret keys<\/a>, blockchain production tokens, and Slack API keys.<\/p>\n

Critically, scans conducted on November 27, three days after the initial disclosure, revealed that some of these high-value credentials, including Google Cloud Service Account keys, were still valid and had not been revoked.<\/p>\n

The GitHub repositories associated with Shai Hulud 2.0 are being removed, but the stolen credentials remain in the attacker\u2019s hands. The campaign demonstrates that any environment where code is executed, whether a local laptop or a cloud-based CI runner, is a potential target for memory scraping.<\/p>\n

With valid secrets circulating days after the attack, organizations are urged to rotate all non-human identities and treat their runtime environments as fully compromised.<\/p>\n

Follow us on Google News<\/a>, LinkedIn<\/a>, and X<\/a> for daily cybersecurity updates. Contact us<\/a> to feature your stories.<\/strong><\/p>\n

The post Shai Hulud 2.0 Compromises 1,200+ Organizations, Exposing Critical Runtime Secrets<\/a> appeared first on Cyber Security News<\/a>.<\/p>\n<\/div>\n

\t

\n
<\/BR>
\n Guru Baran
\n \t

\n
<\/BR>
\nGo to cyber-security-news<\/a>
\n \t

\n
<\/BR><\/p>\n","protected":false},"excerpt":{"rendered":"

Shai Hulud 2.0 Compromises 1,200+ Organizations, Exposing Critical Runtime Secrets The Shai Hulud 2.0 worm, first detected on November 24, 2025, has compromised nearly 1,200 organizations, including major banks, government bodies, and Fortune 500 technology firms. While initial reports described it as a simple npm supply chain attack that flooded GitHub with spam repositories, new […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[129,63],"tags":[130],"class_list":["post-8792","post","type-post","status-publish","format-standard","hentry","category-cyber-security","category-cyber-security-news","tag-cyber-security-news"],"_links":{"self":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/8792"}],"collection":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/comments?post=8792"}],"version-history":[{"count":0,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/8792\/revisions"}],"wp:attachment":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/media?parent=8792"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/categories?post=8792"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/tags?post=8792"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}