The threat actor behind the GhostAction supply chain attack has expanded its operations beyond injecting malicious GitHub Actions workflows into compromised repositories to targeting open-source developers through phishing emails and deploying credential-stealing malware disguised as a font file. According to OpenSourceMalware, the attackers registered the domain my-github\[.\]com on October 9, 2026, and linked it to IP address 193.32.204\[.\]199, previously identified as an exfiltration endpoint for stolen data. The domain was used to send a fake GitHub security alert warning of a suspicious login from Moscow, Russia, and urging the recipient to secure their account. The phishing page reportedly operated as a reverse proxy to capture victims passwords and two-factor authentication codes. It also automated GitHub OAuth device authorization, enabling attackers to obtain reusable access tokens with permissions to read and modify repositories, change workflows, and access organizational information. These capabilities could allow the threat actor to enumerate repositories and introduce malicious workflow files, extending the impact of the GhostAction campaign. Researchers noted that although the domain follows a naming pattern similar to my-gitlab\[.\]com, there is currently insufficient evidence to link the two domains to the same operator. The campaign has also introduced a second-stage infection mechanism designed to persist even after malicious GitHub Actions workflows are removed. Researchers identified 94 compromised repositories containing a VS Code tasks.json file configured to execute automatically when a project folder opens. The task launches a stealer hidden inside public/fonts/fa-solid-400.woff2, which targets AWS keys, npm and PyPI tokens, Git credentials, Kubernetes credentials, SSH keys, and AI provider credentials. The malware also installs a cron job that executes attacker-supplied code every five minutes and sends stolen information over HTTP on port 8080. A fallback GitHub Actions workflow can collect additional secrets and upload findings to a secret gist. OpenSourceMalware identified 94 affected repositories belonging to 66 owners, with many repositories largely abandoned. To mitigate the threat, developers should revoke compromised GitHub sessions and tokens using a clean device, change passwords, audit repositories and workflows, rotate all potentially exposed credentials, and notify users who cloned affected projects.
The U.S. Department of Homeland Security (DHS) has directed federal civilian agencies to eliminate DeepSeek AI tools and related services from their IT environments due to concerns...
Cybercriminals are abusing legitimate financial technology (fintech) platforms to conduct phishing attacks and validate stolen banking credentials, according to research by Group-I...
OVHcloud disclosed a software supply-chain attack on its command-line interface (CLI) repository after an attacker compromised a developer’s GitHub account and distributed malici...