- Joined
- Jan 20, 2026
- Messages
- 345
- Reaction score
- 2,220
Immediately 95 official packages suddenly turned into spies.
Developers are accustomed to trust packages from the usual namespaces, especially when it comes to the components of large vendors. But a new incident with npm has shown that even such dependence can become the entry point to steal secrets. This time, malicious versions appeared among the Npm-components of the Red Hat Cloud Services space, and the attack itself reminded a reduced copy of the Shai-Hulud campaign.
The Socket team reported a malicious campaign against @redhat-cloud-services packages in npm. According to experts, the infected versions ran the hidden load through preinvesting huk, so the code was triggered automatically during the installation of dependence, even before its import into the project.
Dozens of Red Hat Cloud Services packages hit, including chrome, frontend-components, insights-client, rbac-client, host-inventory-client, compliance-client, questionnaires-client and others. In total, Socket tracks 95 affected artifacts published on June 1, 2026.
The analysis showed that index.js in the infected packages was disguised as an ordinary entry point, but actually ran a ostecasted bootloader. The code deciphered the built-in fragments via AES-GM, recorded the main load into the temporary file, ran it through Bun, and then deleted the traces. If Bun was absent, the malware itself tried to download the execution environment from GitHub.
The load collected the secrets of GitHub Actions, npm tokens, SSH keys, Git data, AWS, Azure and GCP cloud accounts, Kubernetes configurations, Vault secrets, Docker data and other sensitive files. The individual modules were aimed at the GitHub CLI and the memory of the GitHub Actions runners, where automation tokens could be located.
Socket also found an encrypted shipment of stolen data through HTTPS and a backup channel via the GitHub API. If there is a suitable malware token, could record in the JSON repository with collection results. The code found signs of possible further distribution through the change of repositories and workflow-files.
The authors of the report associate the attack technique with the approaches of Shai-Hulud, but do not call a specific operator. The appearance of TeamPCP’s open tools associated with Shai-Hulud reduces the entry threshold and allows different groups to repeat similar operations.
Organizations that have installed the affected versions are advised to consider such systems potentially compromised. Simply removing node_modules is not enough, since the malware could work in the background, change the configurations and steal secrets already during installation.
First of all, you need to check lock-files, CI/CD magazines, packages, developer workstations and assembly environments, and then re-released GitHub, npm tokens, cloud providers, Kubernetes, Vault, Docker, PyPI and SSH keys.
Developers are accustomed to trust packages from the usual namespaces, especially when it comes to the components of large vendors. But a new incident with npm has shown that even such dependence can become the entry point to steal secrets. This time, malicious versions appeared among the Npm-components of the Red Hat Cloud Services space, and the attack itself reminded a reduced copy of the Shai-Hulud campaign.
The Socket team reported a malicious campaign against @redhat-cloud-services packages in npm. According to experts, the infected versions ran the hidden load through preinvesting huk, so the code was triggered automatically during the installation of dependence, even before its import into the project.
Dozens of Red Hat Cloud Services packages hit, including chrome, frontend-components, insights-client, rbac-client, host-inventory-client, compliance-client, questionnaires-client and others. In total, Socket tracks 95 affected artifacts published on June 1, 2026.
The analysis showed that index.js in the infected packages was disguised as an ordinary entry point, but actually ran a ostecasted bootloader. The code deciphered the built-in fragments via AES-GM, recorded the main load into the temporary file, ran it through Bun, and then deleted the traces. If Bun was absent, the malware itself tried to download the execution environment from GitHub.
The load collected the secrets of GitHub Actions, npm tokens, SSH keys, Git data, AWS, Azure and GCP cloud accounts, Kubernetes configurations, Vault secrets, Docker data and other sensitive files. The individual modules were aimed at the GitHub CLI and the memory of the GitHub Actions runners, where automation tokens could be located.
Socket also found an encrypted shipment of stolen data through HTTPS and a backup channel via the GitHub API. If there is a suitable malware token, could record in the JSON repository with collection results. The code found signs of possible further distribution through the change of repositories and workflow-files.
The authors of the report associate the attack technique with the approaches of Shai-Hulud, but do not call a specific operator. The appearance of TeamPCP’s open tools associated with Shai-Hulud reduces the entry threshold and allows different groups to repeat similar operations.
Organizations that have installed the affected versions are advised to consider such systems potentially compromised. Simply removing node_modules is not enough, since the malware could work in the background, change the configurations and steal secrets already during installation.
First of all, you need to check lock-files, CI/CD magazines, packages, developer workstations and assembly environments, and then re-released GitHub, npm tokens, cloud providers, Kubernetes, Vault, Docker, PyPI and SSH keys.
