North Korean Group Targets Developers With Malicious Terraform Tool
TraderTraitor deployed a trojanized Terraform provider in July 2026 to deliver FLATROOF and ROOFDECK malware to developer systems.

Key points
- Zscaler ThreatLabz identified the campaign in July 2026.
- The attack uses a trojanized Terraform provider to bypass security.
- Malware targets macOS, Linux, and Windows environments.
Zscaler ThreatLabz reported in July 2026 that the North Korean-backed TraderTraitor group used a trojanized Terraform provider to infect developer environments. This advanced persistent threat actor, also known as Jade Sleet or UNC4899, has long targeted the cryptocurrency industry. The campaign overlaps with the previously analyzed KelpDAO incident, indicating a sustained effort to compromise infrastructure tools used by software engineers and system administrators for deployment automation.
The risk
The attackers embedded malicious code within a legitimate-looking Terraform provider, which executes immediately upon loading. This technique allows the malware to operate while preserving normal Terraform behavior, making detection difficult for users who trust the tool. The initial payload downloads a cross-platform Bash loader from a domain mimicking HashiCorp, the vendor behind Terraform. This loader then selects and delivers malware tailored to the victim's specific operating system and CPU architecture, ensuring broad compatibility across different development stacks.
Who is exposed
FLATROOF malware deploys Python scripts to steal sensitive data from compromised systems before dropping the ROOFDECK backdoor. This two-stage approach grants attackers full remote control over the victim's environment. According to GBHackers, the campaign specifically targets developer environments, where credentials and access keys are frequently stored. The trojanized provider affects macOS, Linux, and Windows systems, exposing any organization using Terraform for infrastructure management to potential breach if they download the compromised package.
Cost and compliance
Attribution to TraderTraitor remains provisional, as ThreatLabz noted similarities in targeting and tactics but lacked unique code matches or shared infrastructure evidence. The campaign’s focus on credential theft via FLATROOF poses significant financial and operational risks to businesses relying on cloud infrastructure. Compromised credentials can lead to unauthorized access to sensitive data and systems, potentially violating compliance requirements for data protection and security standards. Organizations must monitor for unusual activity in their Terraform workflows to mitigate these risks.
What happens next
Managers should audit their Terraform provider sources and verify package integrity before deployment. Monitoring for unexpected network connections or script executions can help detect early signs of compromise. Once the vendor provides an update or mitigation guidance, teams should apply it promptly to secure their infrastructure against this evolving threat.
What to do and how to stay safe: Terraform
- Verify the authenticity of all Terraform providers by checking official repositories and digital signatures.
- Monitor network traffic for connections to unknown or suspicious domains, especially those mimicking legitimate vendors.
- Implement strict access controls and least-privilege policies for developer environments to limit potential damage.
- Regularly update and patch infrastructure tools to protect against known vulnerabilities and malicious modifications.
General security guidance from the CloudSec Pulse newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What malware families were used in this campaign?
The campaign used FLATROOF for credential theft and ROOFDECK for remote access backdoors.
Which operating systems are targeted by this malware?
The malware targets macOS, Linux, and Windows systems based on CPU architecture.
Is there a confirmed fix for this vulnerability?
No fix has been confirmed yet; users should verify provider sources and monitor for updates.



