Large, coordinated software supply‑chain attack campaign and SOC Incident Response

-



Mini‑Shai Hulud refers to a large, coordinated software supply‑chain attack campaign attributed to the threat group TeamPCP, targeting major open‑source ecosystems including npm, PyPI, and Composer. It is a successor and scaled‑down variant of the earlier Shai‑Hulud worm, but still highly capable and dangerous.

Below is a clear, structured breakdown of what Mini‑Shai Hulud is, how it works, who it hit, and why it matters — all grounded in the latest reporting.

 What Mini‑Shai Hulud is

Mini‑Shai Hulud is a credential‑stealing, self‑propagating supply‑chain malware inserted into legitimate open‑source packages. It infects developer environments and then uses stolen tokens to publish malicious versions of any packages the victim has write access to.

It is part of a broader trend of automated supply‑chain attacks where attackers compromise CI/CD pipelines, GitHub Actions, and package registries to spread malware at scale.

 Who was affected

Across multiple registries, the campaign compromised:

  • 42 TanStack packages (React Router, Query, etc.)

  • 65 UiPath packages

  • Mistral AI PyPI packages

  • OpenSearch JavaScript client

  • Guardrails AI

  • Hundreds of additional npm packages, including antv visualization libraries heavily used in blockchain tooling

In total, researchers tracked over 1,000 compromised versions across 500+ packages.

 How the malware works

Mini‑Shai Hulud is engineered to:

  • Steal developer credentials (GitHub, npm, PyPI, cloud keys, CI/CD secrets)

  • Exfiltrate data to attacker‑controlled domains such as filev2.getsession[.]org

  • Propagate automatically by using stolen tokens to publish malicious package versions

  • Install persistence inside IDEs like VS Code and Claude Code

  • Inject malicious GitHub Actions workflows to serialize and exfiltrate repository secrets

Some variants also:

  • Avoid infecting Russian‑language systems

  • Run a daemon that polls GitHub every minute to check token revocation

 How the attackers compromised the packages

TeamPCP exploited multiple weaknesses in GitHub Actions and CI/CD pipelines, including:

  • pull_request_target “Pwn Request” misconfiguration

  • GitHub Actions cache poisoning

  • Runtime extraction of OIDC tokens from runner memory

In some cases, they used orphaned commits to trigger automated release pipelines and publish malicious artifacts with valid provenance signatures, making the malware appear legitimate.

 Example: TanStack compromise

The TanStack ecosystem was hit particularly hard:

  • 84 malicious versions across 42 packages

  • Malware hidden in a file named router_init.js

  • Optional dependency pointing to a GitHub repo with a prepare hook that executed the payload via Bun

  • Assigned CVE‑2026‑45321, CVSS 9.6 (critical)

 Why this matters

Mini‑Shai Hulud demonstrates:

  • CI/CD pipelines are now prime attack surfaces

  • Valid provenance signatures are not enough if the pipeline itself is compromised

  • Open‑source ecosystems remain highly vulnerable to automated, large‑scale supply‑chain attacks

Because these packages are downloaded millions of times per week, the blast radius is enormous.

 What developers should do

If you installed any affected packages during the attack windows:

  1. Rotate all credentials (GitHub, npm, PyPI, cloud providers).

  2. Audit your repositories for unauthorized commits or workflows.

  3. Check for persistence in VS Code or Claude Code.

  4. Rebuild CI/CD secrets and review GitHub Actions permissions.

SOC‑Ready Incident Response Checklist: Mini‑Shai Hulud / Supply‑Chain Compromise

1. Immediate Triage (0–30 minutes)

  • Activate incident bridge and assign roles (IR lead, comms, forensics, cloud lead).

  • Identify whether any affected packages were installed in the last 30 days.

  • Freeze all CI/CD pipelines, GitHub Actions, and automated publishing workflows.

  • Disable GitHub OIDC tokens, npm tokens, PyPI tokens, and any PATs with package‑publish rights.

  • Block known C2 domains (e.g., getsession[.]org variants) at firewall and DNS layers.

  • Snapshot impacted systems (developer workstations, CI runners, build servers).

2. Credential & Access Containment (30–90 minutes)

  • Force‑rotate all developer credentials:

    • GitHub PATs

    • npm / PyPI / Composer tokens

    • Cloud provider keys (AWS, Azure, GCP)

    • SSH keys

  • Revoke all GitHub Actions OIDC trust relationships temporarily.

  • Disable or quarantine service accounts used for publishing packages.

  • Audit GitHub org for:

    • Unauthorized OAuth apps

    • Suspicious PATs

    • New deploy keys

    • New GitHub Apps

3. Developer Workstation Forensics

Mini‑Shai Hulud often installs persistence in IDEs.

  • Inspect VS Code and Claude Code extensions directories for unknown modules.

  • Search for:

    • router_init.js

    • bun‑executed payloads

    • Obfuscated JS in node_modules/.cache

  • Check shell profiles (.bashrc, .zshrc, PowerShell profile) for injected commands.

  • Review browser credential stores for unauthorized access.

  • Run memory capture on any workstation that published packages recently.

4. Repository & CI/CD Forensics

  • Review all repositories with publish permissions.

  • Identify unauthorized:

    • Commits

    • Tags

    • Releases

    • GitHub Actions workflow changes

  • Look for:

    • pull_request_target misuse

    • Cache poisoning

    • Suspicious workflow artifacts

  • Validate provenance signatures — but do not trust them alone (pipeline compromise bypasses provenance).

5. Package Registry Audit

  • Enumerate all packages your org publishes to:

    • npm

    • PyPI

    • Composer

    • Internal registries

  • Check for:

    • Unauthorized versions

    • Modified tarballs

    • Unexpected dependencies

    • New maintainers or collaborators

  • Yank or deprecate any compromised versions immediately.

6. Network & Host Indicators

  • Block outbound traffic to known exfiltration endpoints.

  • Search logs for:

    • Repeated GitHub API calls from unusual IPs

    • npm or PyPI login attempts from foreign regions

    • Developer machines contacting unknown domains

  • Review EDR alerts for:

    • Node.js spawning network connections

    • Bun runtime execution

    • Suspicious PowerShell or bash activity

7. Eradication

  • Remove malicious packages from all systems.

  • Rebuild developer workstations from golden images if any persistence is found.

  • Recreate CI/CD runners from clean templates.

  • Re‑establish OIDC trust relationships with strict conditions:

    • Least privilege

    • Environment‑bound

    • No wildcard audiences

8. Recovery

  • Re‑publish clean versions of any affected packages.

  • Re‑enable CI/CD pipelines with:

    • Mandatory code review

    • Mandatory provenance

    • No pull_request_target unless absolutely required

  • Notify downstream consumers with:

    • Impact window

    • Affected versions

    • Required remediation steps

9. Post‑Incident Actions

  • Conduct a full root‑cause analysis.

  • Update secure‑publishing SOPs.

  • Implement:

    • Sigstore keyless signing

    • GitHub Actions hardened runners

    • Registry‑scoped tokens

    • Mandatory MFA for all developers

  • Schedule a red‑team simulation of CI/CD compromise.


Comments

Post a Comment

Popular posts from this blog

Entire List Leaked for Canvas Ransomware Attack

-
Image
  ( NOTE FROM REDDITOR: All attempts at requesting edit access will be denied. If something is needed, you may email me at: storeluxorsales@gmail.com ) I am not affiliated with this group in any way - so also, please do stop asking (looking at you random press sites). - If anyone wants to save this document, feel free to make a copy. I will be deleting this copy on 10/1/2026. File from link begins below this line. _____________________ This file has been downloaded from the ShinyHunters Data Leak Site (DLS). Our DLS is accessible at these locations:     - http://shnyhntww34phqoa6dcgnvps2yu7dlwzmy5lkvejwjdo6z7bmgshzayd.onion/     - http://shinypogk4jjniry5qi7247tznop6mxdrdte2k6pdu5cyo43vdzmrwid.onion/ > These files were leaked on the ShinyHunters DLS because the victim did not pay a ransom or cooperate and comply with the ShinyHunters group. src;refs;lnks; http://web.archive.org/web/20260322033123/https://shinyhunte.rs/ http://web.archive...
Read more

WSUS CVE-2025-59287 Mitigation

-
Image
CVE-2025-59287 is a critical Remote Code Execution (RCE) vulnerability affecting Windows Server Update Services (WSUS) . Here's a detailed breakdown of what it is, how it works, and what you should do about it: Overview Disclosed: October 2025 Patch Tuesday CVSS Score: 9.8 (Critical) Affected Systems: Windows Server 2012 through 2025 (including Server Core installations) Exploitability: Microsoft rates it as “Exploitation More Likely” Technical Details The vulnerability arises from unsafe deserialization of untrusted data in WSUS. Specifically, the GetCookie() endpoint in WSUS processes encrypted AuthorizationCookie objects without proper type validation. The deserialization occurs via .NET BinaryFormatter , which is known to be insecure when handling untrusted input. Attackers can send a crafted SOAP request to WSUS over port 8530 , containing a malicious AuthorizationCookie . The cookie is decrypted using a hardcoded AES key and then deserialized, allow...
Read more

Cloud Infrastructures are Having a Bad Week

-
Image
  Today’s disruptions across Microsoft Azure and Amazon Web Services (AWS) were significant, but they’re not signs of cloud computing’s demise. Instead, they underscore the risks of centralization and the importance of designing systems that can withstand provider-level failures. What happened today? • Microsoft Azure outage: Azure’s Front Door service suffered a major disruption due to a misconfiguration, impacting services like Outlook, Xbox, Microsoft 365, and even third-party platforms like Starbucks and Alaska Airlines. The Azure website states a little more than disruption. "Azure Front Door - Connectivity issues - Observing recovery Starting at approximately 16:00 UTC on 29 October 2025, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. We have confirmed that an inadvertent configuration change was the trigger event for this issue. Affected Azure services may have included, but were not limited to: App S...
Read more

CVE-2025-58034 Fortinet Warnings and Mitigation

-
Image
Type: OS Command Injection vulnerability (CWE-78) Affected Product: Fortinet FortiWeb (Web Application Firewall) Affected Versions: 8.0.0 – 8.0.1 7.6.0 – 7.6.5 7.4.0 – 7.4.10 7.2.0 – 7.2.11 7.0.0 – 7.0.11 [nvd.nist.gov] , [cvedetails.com] Description The vulnerability is caused by improper neutralization of special elements used in OS commands . An authenticated attacker can exploit this flaw by sending crafted HTTP requests or CLI commands , allowing them to execute arbitrary code on the underlying system. This can compromise the integrity, confidentiality, and availability of the device. [nvd.nist.gov] , [cvedetails.com] Severity CVSS v3.1 Base Score: 7.2 (High) Vector: AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Attack Vector: Network Attack Complexity: Low Privileges Required: High User Interaction: None Impact: High on Confidentiality, Integrity, and Availability [cvedetails.com] Exploitation Status Actively Exploited: Yes. Fortinet confirmed expl...
Read more

Broadcom is dismantling of VMware Cloud Service Providers (VCSPs)

-
Image
  What Broadcom Is Doing to the VCSP Program 1. Broadcom is shutting down the existing VCSP program Multiple sources confirm that Broadcom issued formal non‑renewal notices to many VMware Cloud Service Providers, ending contracts as of January 26, 2026 . Partners may finish existing commitments but cannot renew or create new long‑term contract commitments . 2. Moving to an invite‑only VCSP ecosystem Broadcom is replacing the open VCSP model with a highly selective, invite‑only program , keeping only a small fraction of providers . For example: • Only 19 providers in the U.S. were retained out of thousands. • Hundreds of European providers are being cut loose. 3. White Label program sunset (critical for smaller providers) The White Label model—previously the path for smaller CSPs—has been terminated (or will be phased out depending on region). This effectively eliminates market access for many small providers. 4. Providers that are cut must hand off customers Broadcom directs ...
Read more

FBI Seizes RAMP Cybercrime Forum

-
Image
The FBI has taken down RAMP (Russian Anonymous Marketplace) , one of the most active cybercrime forums used by ransomware gangs, initial access brokers, malware sellers, and extortion groups . The takedown affected both the clearnet and dark‑web (Tor) domains, which now display official FBI/DOJ seizure notices. Why RAMP Was Significant RAMP was: Known as “the only place ransomware allowed.” A major hub for groups including LockBit, ALPHV/BlackCat, Conti, DragonForce, Qilin, RansomHub , and more. A high‑trust marketplace offering malware, exploits, tutorials, and escrow services . Home to 14,000+ vetted users , some paying fees for anonymity. Impact of the Seizure 1. Major Disruption to Criminal Infrastructure The takedown is seen as a meaningful blow against ransomware‑as‑a‑service communities. 2. Forced Migration to Other Forums Criminal groups are already shifting activity to alternative platforms like Rehub . These migrations are chaotic and risky for criminals due to: Loss of rep...
Read more

CodeRED emergency alert system is currently down across many regions!

-
Image
  CodeRED emergency alert system is currently down across many regions in the U.S. following a ransomware attack on its vendor, Crisis24. The incident has disrupted critical emergency communications and exposed user data. What Happened Attack Type : Ransomware Threat Actor : INC ransomware group Target : OnSolve CodeRED platform (owned by Crisis24) Impact : Emergency alerts (weather, missing persons, terror threats) are unavailable in many municipalities. Personal data compromised : names, addresses, emails, phone numbers, and passwords used to create CodeRED accounts. Key Details Date of Outage : Began in early November 2025, publicly confirmed Nov 26 Scope : Hundreds of municipalities affected nationwide Response : Crisis24 is migrating customers to a new CodeRED platform hosted in a separate, hardened environment. Some cities (e.g., Douglas County, CO) have terminated their CodeRED contracts and are seeking replacements. Others are using social media, door-...
Read more

Notepad++ update service was compromised

-
Image
  Notepad++ update service was compromised Multiple independent security investigations confirm that Notepad++’s update infrastructure was hijacked between June and December 2025 . This was a supply-chain attack originating from a compromise at the hosting‑provider level , not from Notepad++’s code. What exactly was compromised? 1. Update traffic was intercepted and redirected Attackers manipulated the update endpoint ( getDownloadUrl.php ) so that some users requesting updates were silently redirected to malicious servers serving tampered executables . 2. It was targeted , not widespread All sources emphasize that only specific users were affected, likely in an espionage‑focused campaign , not a mass malware distribution effort. 3. Hosting provider compromise, not a Notepad++ bug The attackers gained access to the shared hosting environment , losing direct access in September 2025 but maintaining stolen internal service credentials through December 2, 2025. Attribution: Likely...
Read more

SitusAMC Breached!

-
Image
  What Happened? On November 12, 2025 , SitusAMC detected unauthorized access to its systems. Hackers exfiltrated sensitive corporate and client-related data. The attack did not involve ransomware or encrypting malware , suggesting the goal was data theft rather than disruption. [techcrunch.com] Data Impacted Corporate data : Accounting records, legal agreements, and internal contracts. Client-related data : Information tied to residential mortgage loans, which may include personally identifiable information (PII) such as Social Security numbers and financial details. The exact scope and number of affected individuals is still under investigation. [ibtimes.co.uk] Who Is Affected Major U.S. banks including JPMorgan Chase, Citigroup, and Morgan Stanley were notified that their data may have been exposed. SitusAMC works with hundreds of lenders, so the potential ripple effect across the financial sector is significant. [webpronews.com] SitusAMC has contained the breach,...
Read more

Cyber Monday Fraud Alert

-
Image
Cyber Monday brings incredible deals—but it also attracts cybercriminals looking to exploit shoppers . Fraudsters use fake websites, phishing emails, and misleading ads to steal money, personal information, or identities. Common Scams Fake retailer sites : Look-alike domains with odd spellings or missing security (no HTTPS). Phishing emails & texts : “Exclusive deals” or “delivery issues” that link to malicious sites. Too-good-to-be-true offers : Deep discounts on electronics, gift cards, or luxury items. Charity scams : Fraudulent donation sites targeting Giving Tuesday generosity. How to Stay Safe Shop only on trusted, secure websites (look for HTTPS). Type retailer URLs directly— don’t click links in emails or ads. Use credit cards for stronger fraud protection. Compare prices across trusted platforms to spot fake “discounts.” Verify charities before donating. Report Fraud If you suspect a scam: Contact your bank or credit card provider immediately . Report ...
Read more