Trigram Campaign Poses as 50 AI and Blockchain Brands to Trick Developers into Installing Infostealers
Stormshield has published a technical report on Trigram, a large-scale and industrialised campaign targeting the AI, blockchain and logistics sectors across Europe and the U.S. The campaign impersonates about 50 brands in the blockchain and AI sectors, with the aim of tricking developers into running an infostealer on their own machines.
According to the report, three social engineering scenarios (recruitment, conference and package tracking), a software supply-chain compromise and trojanized code repositories all lead to the same infrastructure and the same payload. The activity resembles intrusion sets linked to North Korea, including Kimsuky and UNK_DeadDrop, which in turn resembles the Contagious Interview campaign. SafeDep cautioned that the match rests on technique and does not prove who the operators are.
One delivery route involved a forged commit in the antd-img-crop GitHub repository. It installed malware through a prebuild hook as soon as a developer ran the "npm run build" command, although the npm package itself was not affected. The malware reportedly steals browser passwords, cookies, keychains, cryptocurrency wallets, SSH keys and .env files on macOS, Linux and Windows. It then installs a remote-access agent disguised as Google software. On macOS and Linux it also shows a fake dialog asking for the system password.
A related branch, tracked by Genians as Operation GitPower and attributed to Kimsuky, uses locally run LLM tools to generate decoy documents. Phishing emails carry LNK files that launch PowerShell, fetch a lure and quietly download payloads such as AsyncRAT. This branch has also targeted Ukrainian experts in diplomacy and security, though Genians said those efforts were mostly unsuccessful. Stormshield says the pieces form one infection chain adapted for three environments.
Why it matters
Developers are exposed because the attack relies on them running the code themselves, so many email and download controls never get a chance to stop it. A forged commit that runs through a build hook shows that trusting a repository, even when its published package is clean, is no guarantee of safety. The malware targets SSH keys, .env files and wallets, so one compromised developer laptop can lead to wider access to company systems.
What to do
- Review recent commits to the antd-img-crop GitHub repository and check for unexpected changes to prebuild.js before running npm run build.
- Rotate SSH keys, browser-stored passwords and secrets in .env files on any machine where suspicious code was run.
- Block or alert on LNK files inside ZIP archives received by email.
- Look for a LaunchAgent named com.zoom or a remote-access agent posing as Google software on macOS and Linux developer machines.