Shai-Hulud Clone 'Miasma' Compromises 32 Red Hat npm Packages, Targeting CI/CD Pipelines

A significant security alert has been raised within the DevOps community following the discovery of a new offensive framework, 'Miasma,' which has successfully compromised 32 npm packages associated with Red Hat. The threat group, identified as TeamPCP, has deployed a modular framework designed for a range of malicious activities, including credential harvesting, supply chain poisoning, and the exfiltration of encrypted data. The primary targets for these attacks are developer workstations and, critically, continuous integration/continuous delivery (CI/CD) pipelines, which are becoming increasingly attractive to malicious actors. Security researchers have noted the unusual nature of this incident, particularly the public release of the 'Miasma' framework's source code while it is still part of an active campaign. This public availability grants other threat actors access to the same techniques, potentially enabling them to replicate or adapt these sophisticated attacks. The framework also showcases advanced capabilities, such as integrating AI agents for persistence and utilizing Sigstore provenance for data theft. The attack vector involved the compromise of CI/CD pipelines through GitHub Actions OIDC (OpenID Connect), rather than the exploitation of traditional npm tokens. This indicates a shift in attack methodologies, where the CI/CD pipeline itself becomes the vulnerable surface, and OIDC-based trusted publishing, intended to enhance security by eliminating long-lived tokens, is being manipulated as a misleading trust signal. While Red Hat engineers prevented product contamination through version pinning, the primary risk extends to downstream open-source consumers and organizations directly using these compromised packages in their frontend applications, CI/CD pipelines, and build systems. Security experts recommend that any organization that installed affected versions should conduct a thorough audit of their dependencies, treat all CI secrets, cloud credentials, and npm tokens as potentially compromised, and rotate them immediately. Furthermore, removing the compromised packages or pinning to known safe versions is crucial to mitigate ongoing risks.