Trigram Infostealer: Hackers Impersonate 50 Brands to Steal Passwords Through Fake Job Offers
A promising remote job opportunity from a recognizable technology company could be the start of a credential theft attack. Cybersecurity researchers have uncovered a campaign called Trigram, in which attackers impersonate roughly 50 legitimate brands to trick developers and technology professionals into installing information-stealing malware.
The campaign uses fraudulent recruitment websites, conference invitations, and package-delivery notifications to lure victims into completing what looks like a routine verification process. But that process is designed to make victims execute malicious commands on their own computers. Once the malware runs, attackers can attempt to collect browser passwords, cryptocurrency wallet information, sensitive files, and other valuable data.
On November 17, 2026, Stormshield's Cyber Threat Intelligence team published a detailed investigation into the campaign, revealing the infrastructure and techniques used to manage the attacks. The finding carries an important lesson: a professional-looking website can be used to convince someone to install malware without realizing it.
What is the Trigram infostealer campaign?
Trigram is a coordinated campaign targeting professionals in artificial intelligence, blockchain, cryptocurrency, and logistics across the United States and Europe. Researchers identified about 50 brands being impersonated through fraudulent websites and communications. The attackers use three primary methods to attract victims:
- Fake recruitment opportunities advertising remote technology jobs.
- Fraudulent conference invitations that appear to come from legitimate organizations.
- Counterfeit package-tracking websites that imitate delivery services.
These different approaches all funnel victims toward malicious software. Stormshield also uncovered a centralized management platform the attackers used to coordinate phishing messages, manage fraudulent websites, and track victims. That makes Trigram more than a scatter of isolated phishing attempts; it is an organized campaign with infrastructure built to support repeated attacks. One clarification matters: the legitimate companies whose identities are being misused are not necessarily compromised. Their names and branding are being impersonated without authorization.
How the Trigram attack works
One of Trigram's most distinctive techniques is a fake recruitment process. The attackers make a malicious website look like an ordinary job-application portal, and the process is designed to build trust before asking the victim to run a dangerous command. This is a close cousin of the fake-meeting trick behind the FaceStealer campaign: the surface looks routine, and the danger is in one instruction.
Step 1: A convincing job offer arrives
The attack begins with an email advertising a remote software development position. The message appears to come from a recruiter at a legitimate technology company and may include an attractive salary, a job description, and a link to an application website, often with a referral code to use. Because it resembles an ordinary recruitment opportunity, the victim may not immediately sense danger.
Step 2: The victim visits a fake careers website
The site includes familiar elements such as a company overview, job responsibilities, salary information, and an application form. The victim may be asked for their name, email address, portfolio, and other details. It is carefully designed to feel legitimate, and after submitting the application the victim is directed to a verification page.
Step 3: The website requests a terminal command
The verification page asks the victim to prove they are not a robot. Instead of an ordinary CAPTCHA, it instructs the user to copy a command and run it on their computer, using PowerShell, Command Prompt, or Terminal depending on the operating system. It presents this as routine. In reality, legitimate recruitment websites should never require applicants to execute unfamiliar system commands just to apply.
Step 4: The first command appears harmless
Stormshield found that the first command is designed to send a verification value back to the attacker's server. It does not initially download the malware, which helps the process appear credible. After the command runs, the website deliberately shows a timeout error and asks the victim to repeat the verification.
Step 5: The website secretly changes the copied command
This is the most dangerous stage. Although the page looks almost identical, the behavior of its copy function has changed. When the victim copies the command again, the website places a different command into the clipboard, one designed to download and execute malicious software. Researchers observed that the command could include a trailing newline, causing it to run immediately when pasted into a terminal. This is a variation of ClickFix, a social-engineering method that tricks users into executing malicious commands under the pretense of fixing an error or completing a verification. The victim believes they are repeating a harmless step while actually installing malware.
Step 6: Malware is installed
Once the malicious command runs, it retrieves additional components from attacker-controlled infrastructure. The infection chain can install a JavaScript-based payload that collects sensitive information from the computer, and researchers documented versions targeting Windows, macOS, and Linux. The attackers can then use the stolen information for further unauthorized activity.
What information does Trigram attempt to steal?
Trigram's infection chain is associated with information-stealing malware designed to collect sensitive data from infected computers. The targeted information can include:
- Saved browser usernames and passwords.
- Browser cookies and other authentication information.
- Cryptocurrency wallet data.
- Sensitive files stored on the computer.
- SSH keys and development-environment secrets.
- System information that helps attackers evaluate the compromised device.
Related research also identified the use of the OverLord remote access framework, which can give attackers additional control over an infected system. These capabilities are especially concerning for developers and technology professionals who use their computers to reach business applications, source-code repositories, and cloud services. That said, the research does not establish that every targeted individual was successfully infected or that all of the listed information was stolen from every victim. The browser-cookie piece is why a password reset alone can fall short, the same session-cookie risk that lets attackers skip the login entirely.
Why are developers being targeted?
Software developers frequently have access to valuable systems and sensitive information. Their computers may hold saved login credentials, development tools, source code, and access to business infrastructure, so an attacker who compromises a developer's machine may gain a path to additional systems, depending on the permissions available. Trigram exploits this by using recruitment opportunities and technical-verification steps that feel familiar to developers, and by building parts of its infrastructure on legitimate development platforms and online services, which makes the campaign harder to recognize because not every component looks obviously malicious. It is the same lesson as the Binance developer-laptop compromise: a single developer's device can be a doorway into much more.
Trigram is also linked to a GitHub repository compromise
The investigation connects Trigram to previously reported activity involving the antd-img-crop open source JavaScript project. On October 31, 2026, attackers introduced a malicious change into the project's GitHub repository, adding a build step capable of downloading and executing malicious code when a developer ran the affected build process. This created another possible infection route for people working directly with the compromised repository.
Importantly, researchers reported that the published npm package itself was not affected by this particular compromise. The identified risk involved the altered repository content and its build instructions, which matters because organizations should not assume that every user of the library was infected. The incident shows how malicious changes to development workflows can create opportunities for credential theft, and why businesses should review unexpected changes to build scripts and avoid executing unfamiliar code without appropriate safeguards. The same pattern drove the Microsoft Agent Framework PyPI compromise, where malicious package versions stole cloud credentials through a Python startup hook.
Is Trigram connected to North Korean hackers?
Stormshield identified technical overlaps between Trigram and activity previously tracked as UNK_DeadDrop, and other researchers have linked related activity to North Korean threat clusters including Kimsuky. Stormshield assessed with high confidence that Trigram represents a continuation of the UNK_DeadDrop cluster. Attribution here is based on technical evidence and research assessments rather than a public identification of every individual responsible. For businesses, the immediate concern is the documented infection technique and the possibility of sensitive information being stolen, not the attribution label.
Why small businesses should pay attention
Trigram's confirmed targeting focuses on technology professionals, but its social-engineering methods have broader implications. Employees routinely receive emails about jobs, events, software updates, and deliveries, and attackers can exploit those ordinary activities to steer people to fraudulent websites. For example, an employee at a small software company might receive a fake recruitment invitation on a computer that also holds business credentials. If they run the malicious command, sensitive login information stored on that computer could be exposed. The same risk applies to a fraudulent conference invitation or delivery notification. The key lesson is simple: a website should not be trusted to provide executable commands merely because it looks professional or displays a familiar company logo.
What healthcare organizations can learn
Healthcare practices depend on business applications, technology vendors, and external contractors, and some employees and service providers access sensitive systems through browsers and cloud applications. If an infostealer compromises one of those computers, saved login information could be exposed. The reviewed Trigram research does not establish that a particular healthcare organization was affected, but healthcare organizations should still weigh the broader risks of malicious downloads, exposed credentials, and compromised contractor accounts. Practical protections include strong authentication, managed endpoint security, limited administrative privileges, and procedures for investigating suspicious software execution, as we discuss in our guide to dark web monitoring for healthcare and HIPAA.
Seven ways businesses can protect themselves from Trigram
- Never execute commands from unfamiliar websites. A job application, conference registration page, or package-tracking service should not require employees to run PowerShell or terminal commands as a verification step. Treat such requests as suspicious.
- Verify recruitment opportunities independently. Visit the company's official careers website directly, and confirm the position exists and the recruiter is authorized. A realistic website or recognizable logo does not prove legitimacy. Our guide on spotting phishing emails helps.
- Protect employee and developer computers. Use managed endpoint protection, keep operating systems and applications updated, avoid unnecessary administrative privileges, and evaluate unfamiliar code in isolated environments where possible.
- Review software build processes. Developers should inspect unexpected changes to build scripts, package instructions, and repository permissions, and use code reviews and repository protections to reduce the risk of malicious modifications.
- Use unique passwords and strong MFA. Require unique passwords for important accounts and enable multifactor authentication, preferably phishing-resistant methods such as passkeys or hardware keys. MFA reduces account-takeover risk but does not prevent every attack involving infected devices.
- Monitor known credential exposures. Review known exposed logins tied to business accounts, and when an exposure is identified, determine whether the account is still active and whether its credentials need replacing. This complements endpoint protection and authentication monitoring.
- Train employees to report suspicious activity. Staff should know how to report unexpected verification commands, suspicious recruitment messages, and unusual software-installation requests, so the organization can investigate a potential compromise early.
What should you do if an employee executed the malicious command?
If an employee followed instructions from a suspected Trigram website, treat the computer as potentially compromised. A qualified IT or security professional should assess whether the device needs isolation and determine what executed. Identify the sensitive accounts and applications that were reachable from the computer, replace potentially compromised passwords from a trusted device, and where appropriate revoke suspicious sessions, rotate affected development secrets, and review account activity. For developers, the investigation may need to extend to source-code repositories, cloud environments, and software-publishing permissions.
Two points are easy to miss: changing a password alone does not remove malware, and removing malware does not automatically invalidate credentials attackers may already have stolen. Both the device and the potentially exposed accounts need attention, as our malware incident response steps explain.
How GuardPilot helps businesses identify exposed credentials
Trigram shows how infostealer malware can collect login credentials that attackers may later try to misuse. GuardPilot helps individuals and small businesses identify known exposed login credentials appearing in supported breach records, infostealer data, and dark-web sources. When relevant findings are available, its AI explains the exposure, provides context about potential risks, and recommends practical remediation steps, rather than just handing you a list of leaked logins.
The boundary matters. GuardPilot does not detect Trigram malware running on a computer, inspect source-code repositories, monitor live sessions, identify stolen session tokens, or perform endpoint and server forensics. It also does not monitor API keys, SSH keys, or cloud development secrets, and it cannot guarantee that credentials stolen during the Trigram campaign will appear in its supported intelligence sources. A clean credential-exposure check does not prove a device or account is secure. Combine credential-exposure awareness with endpoint protection, strong authentication, and incident response. Concerned about known exposed business login credentials? Check your credential exposure.
Frequently asked questions
What is Trigram malware?
Trigram is a cyberattack campaign that impersonates legitimate brands through fake recruitment, conference, and package-delivery websites to trick people into executing information-stealing malware.
What does the Trigram infostealer steal?
The malware targets browser credentials, cryptocurrency wallet information, sensitive files, and other accessible data. Related attack chains also target development secrets.
Does Trigram affect Windows and Mac computers?
Yes. Researchers identified infection chains targeting Windows, macOS, and Linux.
What is ClickFix phishing?
ClickFix is a social-engineering technique that tricks people into executing malicious commands by presenting them as troubleshooting or verification instructions.
Were the impersonated companies hacked?
Not necessarily. The use of a company's name or logo does not establish that the legitimate organization was compromised.
Can MFA prevent Trigram malware?
No. MFA helps protect accounts, but it does not prevent malicious software from executing on a computer.
Can GuardPilot detect Trigram infections?
No. GuardPilot monitors supported known credential exposures. It does not detect malware infections or perform device investigations.
What should I do if I ran a suspicious verification command?
Stop using the affected computer for sensitive activities and contact your organization's IT or security team. The device and potentially exposed accounts should be investigated.
The takeaway
The Trigram campaign shows how cybercriminals combine recognizable brands, convincing recruitment websites, and deceptive verification steps to steal sensitive information. Its most distinctive move is changing the clipboard contents after a fake verification error, so victims execute malware without realizing the copied command has changed. For small businesses, the lesson is practical: verify unexpected requests, avoid executing commands from unfamiliar websites, protect important accounts, and investigate suspected malware infections promptly. Credential exposure monitoring can help identify certain known compromised logins, but it is only one component of effective cybersecurity.