1-minute read
What a defender needs to know
Unit 42 says XCSSET v40 has spread through poisoned Xcode projects since early April 2026. Building an infected project starts a four-stage loader that moves its core logic into memory and deletes temporary staging files. The malware can then modify every Xcode project it finds, add payloads to Git pre-commit hooks, and infect project ZIP archives.
V40 also stores a re-infection payload in a randomly named macOS defaults domain. Other modules disable security-update settings, interfere with cloud telemetry, lock the XProtect signature database, and reset AppleEvents consent decisions. Unit 42 observed infected projects associated with dozens of legitimate applications and thousands of active users. The report does not name those applications or establish how many downstream builds shipped contaminated code.
Disconnect a suspected developer Mac before another build or repository synchronization. Preserve process, network, project, shell, launch, Git-hook, and preferences evidence. Inspect every reachable Xcode project, local repository, and project archive against trusted source, then review remote history and build output for unexplained changes. From a clean system, invalidate browser sessions and rotate developer credentials, SSH keys, and API tokens.
Verify that the Mac is clean and all reachable project copies match trusted source. Reconcile repository and release history, replace credentials, and test that macOS security updates work. Missing endpoint history or untracked project archives leaves propagation unresolved and documented.