A GitHub credential-theft campaign, attacks on Check Point gateways and an exploited Outlook flaw call for immediate credential checks, patching and incident review.
Three threats deserve attention from IT teams: stolen GitHub credentials used to reach developer workflows and cloud accounts, attacks on Check Point security gateways that in some cases led to VMware ESXi data destruction, and an actively exploited Microsoft Outlook vulnerability. Each calls for a focused check of access, software updates and logs.
The GitHub campaign, known as wfx-loot, relied on valid stolen credentials rather than a vulnerability in GitHub Actions, according to SecurityWeek and SailPoint. Attackers reportedly used credentials from 4,837 GitHub accounts to probe 61,764 repositories. Researchers confirmed that a malicious script ran in at least 1,835 repositories, where it sought GitHub Actions secrets and credentials for AWS, Azure and Google Cloud.
The operation reached beyond cloud keys. GitGuardian reported an earlier phase from October 24 to 29, before a larger wave began November 10. The malware searched for credentials associated with package registries, Terraform Cloud, Vault, databases, SSH and GnuPG. Attackers reportedly removed workflow runs and logs within about a minute. The payload could create long-lived AWS access keys, change an AWS role’s trust policy to accept any AWS account, and add Microsoft Entra federated credentials named with the prefix `wfx-ci-`.
For developers and small IT teams, removing a suspicious commit is not enough. Review GitHub audit and workflow records, identify potentially exposed repositories and accounts, then revoke and rotate affected credentials. Check AWS role trust policies and access keys, Microsoft Entra federated credentials, and other cloud and developer tokens for unexpected entries. Investigate from a clean system. Since attackers may have deleted evidence, compare available logs and repository history; a missing workflow record does not prove that nothing ran.
A separate campaign targeted internet-facing Check Point Mobile Access portals using PHP2Shell vulnerabilities CVE-2026-109618 and CVE-2026-109619, according to BleepingComputer. Attackers then used CVE-2026-123039 to gain root privileges. Activity began October 30, first targeting Israeli organizations; a second wave on November 2 reached organizations in multiple countries and sectors.
Some incidents involved a backdoor and a wiper targeting VMware ESXi. The `destroy_v6` malware attempts to overwrite files before deleting them, although a fast mode skips the overwrite. It left notes referencing “Dream Security Ltd.” BleepingComputer reported that the second wave did not include destructive activity, while subsequent actions were unclear. The reporting documents destructive attacks, but does not establish that every affected gateway—or the later wave—resulted in ESXi wiping.
Administrators should inventory internet-facing Mobile Access portals, check Check Point guidance for applicable fixes, and review gateway and virtualization logs for unexpected access or changes. If compromise is suspected, isolate affected systems and preserve evidence before rebuilding. Patching closes a vulnerability; it does not remove an attacker who already obtained root access.
Microsoft Outlook also needs prompt attention. CVE-2026-124194 is an actively exploited spoofing flaw listed in CISA’s Known Exploited Vulnerabilities catalog. A specially crafted message file can cause Outlook to connect to an attacker-controlled network location without the usual external-content warning, potentially exposing an NTLMv2 authentication hash. Microsoft addressed the flaw in its November 10 Patch Tuesday release. Organizations using affected Microsoft 365 Apps for Enterprise or Office LTSC versions should confirm that the update is installed and prioritize systems that remain unpatched.
These incidents show how stolen credentials and exposed management services can be as consequential as software bugs. Teams with limited staff should first confirm Outlook updates, review internet-facing Check Point gateways, and audit developer and cloud credentials tied to GitHub. If logs or identities look suspicious, contain the exposure and revoke access before routine cleanup.

