This threat involves malicious code injected into specific versions (6.11.3, 6.11.4, 6.11.6) of the @redhat-cloud-services/frontend-components-config npm package, part of a broader supply chain worm campaign targeting Red Hat Cloud Services npm packages. The attacker inserted a preinstall hook that executes a multi-layer obfuscated payload, which downloads a Bun runtime to run the worm independently of the victim's Node.js environment. The malware harvests extensive credentials and tokens from various cloud providers (AWS, Azure, GCP), CI platforms, password managers, and local configuration files, exfiltrating data to public GitHub repositories. It escalates privileges by exploiting Docker socket access to modify sudoers files, enabling passwordless sudo for CI runner accounts. The worm self-propagates by republishing malicious npm packages using stolen credentials, injecting malicious CodeQL workflows into GitHub repositories, and signing artifacts with Sigstore to appear legitimate. Persistence is maintained through daemon installation and hijacking of AI and editor configuration files. The malware includes sandbox and EDR detection capabilities to evade analysis and detection. Systems with this package installed should be treated as fully compromised.

Systems with affected versions of the package installed are fully compromised. The attacker gains access to a wide range of sensitive credentials and tokens across multiple cloud platforms, CI environments, and local secrets, enabling extensive unauthorized access and potential lateral movement. Privilege escalation via Docker socket access allows the attacker to gain passwordless sudo rights, increasing control over the system. The worm self-propagates by republishing malicious packages and injecting malicious workflows, potentially compromising additional repositories and systems. Persistence and evasion mechanisms reduce the likelihood of detection and removal. The compromise poses a severe risk to confidentiality, integrity, and availability of affected systems and associated cloud and CI environments.

No official patch or fix is currently documented for this malicious package compromise. Immediate mitigation requires removing the affected package versions (6.11.3, 6.11.4, 6.11.6) from all systems. Because the malware grants full system compromise, all secrets and credentials stored on affected systems must be considered compromised and rotated immediately from a secure, uncompromised environment. Monitor for signs of persistence such as daemons in /tmp/kitty-*, hijacked AI agent and editor configurations, and unusual GitHub workflow commits. Review and revoke any suspicious npm publish tokens and GitHub PATs. Due to the complexity and persistence of the malware, consider full system rebuilds where feasible. Check vendor advisories and trusted security sources for updates or official remediation guidance.