Trigram Campaign: 50 AI and Blockchain Brands Impersonated to Deliver Infostealers to Developers
A large-scale, industrialized operation is targeting software developers across Europe and the United States by impersonating roughly 50 brands in the artificial intelligence, blockchain, and logistics sectors. Dubbed Trigram, the campaign was detailed in a deep-dive technical report by security firm Stormshield, as reported by The Hacker News.
The core of the scheme is simple but effective: trick developers into running malicious code themselves, resulting in the installation of an infostealer that harvests credentials, session tokens, and other sensitive data.
A Brand-Impersonation Machine
Trigram's defining characteristic is its scale. Rather than focusing on a single company or product, the operators have built what appears to be a repeatable, templated process for cloning the identities of dozens of legitimate brands. According to Stormshield, the campaign impersonates approximately 50 brands tied to the blockchain and AI sectors, with logistics also appearing among the targeted verticals.
The choice of victims is deliberate. Developers working with AI and blockchain tooling are accustomed to pulling down SDKs, libraries, and command-line utilities from the internet, often from sources that are not always carefully vetted. They frequently hold high-value credentials — cloud keys, repository access, crypto wallets, API tokens — that make them attractive targets for infostealer operators.
How the Infection Chain Works
The attack follows a familiar supply-chain-adjacent pattern. Victims are lured to fraudulent websites or repositories that closely mimic legitimate developer resources. These may take the form of fake project pages, spoofed documentation portals, or counterfeit package listings offering what appear to be official SDKs or tools.
Once a developer downloads and executes the offered software, the payload runs with the user's own privileges — a technique that sidesteps many perimeter defenses, since the malicious action originates from the victim's machine rather than an external intrusion. The infostealer then goes to work collecting browser-stored passwords, cookies, cryptocurrency wallet data, and potentially development-environment secrets.
Stormshield's analysis describes Trigram as "industrialized," reflecting the degree of automation behind the brand impersonations and infrastructure. The operators appear to maintain a pipeline for standing up convincing lookalike assets across many brands simultaneously, rather than hand-crafting each lure.
Why Developers Are the Prize
Developers have become a favored entry point for financially motivated threat actors. A single compromised developer workstation can yield access to source code repositories, CI/CD pipelines, cloud environments, and production systems. Infostealers are particularly well suited to this goal because they are lightweight, fast, and designed to exfiltrate credentials quietly before defenders can respond.
The AI and blockchain angles add further incentive. Blockchain developers often manage wallets and keys directly on their work machines, while AI practitioners may hold access to expensive compute resources and proprietary model assets. Both communities also tend to adopt new tools rapidly — a behavior attackers exploit through typosquatting and lookalike branding.
Defensive Guidance
Organizations and individual developers can reduce exposure with several practical measures:
- Verify before you run. Download SDKs and tools only from official, verified sources. Cross-check domains and repository owners rather than relying on search results or advertisements.
- Treat credentials as crown jewels. Store secrets in dedicated vaults, avoid keeping wallet keys or long-lived API tokens on development workstations, and rotate credentials regularly.
- Monitor for infostealer indicators. Endpoint detection should flag unusual access to browser credential stores and cryptocurrency wallet files, which are common infostealer targets.
- Enforce least privilege. Developers should not routinely operate with administrative rights, and access to production systems should be tightly scoped.
- Educate on brand impersonation. Awareness training should cover the specific tactic of counterfeit developer tools and documentation sites, not just phishing emails.
The Bigger Picture
Trigram fits a broader trend of attackers industrializing the impersonation of trusted software brands to reach technical audiences. As AI and blockchain continue to attract investment and talent, the pool of developers holding valuable credentials will only grow — and so will the incentive for campaigns like this one.
The Stormshield report underscores that the weakest link in many development workflows is not the code itself, but the trust developers place in the tools they download. Verifying provenance, limiting credential exposure, and monitoring endpoints for stealer behavior remain the most reliable defenses against this class of attack.
For the full technical analysis, see the original reporting from The Hacker News.