STRATEGY
DDoD
Distributed Denial of Detection
LANGUAGES
5+
Nim, Zig, Crystal, Rust, Go
C2 SERVICES
6+
Slack, Discord, Sheets, Supabase
PACE
DAILY
New variants generated every day
THE STORY
Bitdefender published research this week disclosing a fundamental shift in how APT36 (Transparent Tribe) develops and deploys malware. Instead of investing in a small number of carefully engineered tools, the Pakistan-aligned state-sponsored group has pivoted to what Bitdefender calls "vibeware": AI-assisted, rapidly produced malware that trades sophistication for scale.
The concept is deceptively simple. Using large language models, APT36 operators are generating functional malware in programming languages they likely don't know well, including Nim, Zig, Crystal, Rust, and Go, at a pace of roughly one new variant per day. The code is not elegant. Researchers found tools with placeholder C2 addresses that would never actually exfiltrate data. They found backdoors that reset their own tracking timestamps. They found logic errors that would make a junior developer cringe. Some of the code even contained emojis, which is a telltale sign of LLM-assisted generation.
But the quality doesn't matter. The strategy does.
Bitdefender has named the approach "Distributed Denial of Detection," or DDoD. The logic mirrors a DDoS attack: instead of overwhelming a server with traffic, you overwhelm a detection engine with variants. If five malware samples hit a target simultaneously, one in Nim, one in Crystal, one in Rust, one in Go, one in .NET, and even one gets through because the AV engine hasn't seen Crystal malware before, the attacker wins. The other four were expendable.
The campaign targets the Indian government, its embassies across multiple countries, and entities in Afghanistan and the broader South Asian region. APT36 uses LinkedIn to identify high-value targets and delivers initial access through fake resume PDFs and modified browser shortcuts. Once on a system, the malware fleet communicates through Slack, Discord, Google Sheets, Supabase, and Firebase. All of these are trusted cloud services that most organizations cannot block without disrupting business.
The specific tools identified include CreepDropper (a .NET loader), SHEETCREEP (a Go-based infostealer using Microsoft Graph API for C2), MAILCREEP (a C# backdoor using Google Sheets), SupaServ (a Rust backdoor using Supabase with Firebase fallback), LuminousStealer (a Rust-based file exfiltrator using Firebase and Google Drive), CrystalShell (a cross-platform backdoor in Crystal using Discord for C2), and LuminousCookies (a credential stealer that bypasses Chrome's App-Bound Encryption by injecting directly into the browser's memory).
THE ADVERSARY PERSPECTIVE
The Economics of Malware Just Changed
From an offensive security standpoint, vibeware represents a structural shift in the attacker-defender cost equation. For decades, building effective malware required real skill. You had to understand target architectures, write reliable shellcode, engineer persistence mechanisms, and test against AV engines. The cost of production was high, which meant attackers were selective and defenders could focus on detecting known tool families.
AI collapses that cost to near zero. APT36 can now produce a functional implant in a new language in minutes, not weeks. The tool doesn't need to be perfect. It needs to work once, on one machine, for long enough to establish a foothold. If it gets burned, they generate another one tomorrow in a different language.
This fundamentally breaks signature-based detection. Every new language, every new binary, every slight variation in how the same logic gets expressed resets the detection baseline. And by using niche languages that most security engines have limited visibility into, the attacker gets a bonus advantage: the AV has never seen a Crystal binary before, so it has no behavioral models for what "normal" Crystal execution looks like.
Figure 01
- 01
TARGETING
LinkedIn recon to identify govt and diplomatic targets - 02
INITIAL ACCESS
Fake PDF resumes, modified browser shortcuts - 03
AI GENERATION
LLM produces polyglot implants in Nim, Zig, Crystal, Rust - 04
MASS DEPLOY
Multiple simultaneous implants per target, different languages - 05
CLOUD C2
Slack, Discord, Sheets, Supabase, Firebase - 06
EXFILTRATE
Credential theft, file exfil via trusted cloud APIs
The cloud C2 layer compounds the problem. Blocking Slack, Discord, or Google Sheets is impractical in most enterprises. The attacker's command traffic looks identical to an employee checking a shared spreadsheet. Defenders are forced to do behavioral analysis on API-level telemetry from trusted services, and that is a capability most SOCs simply do not have.
Here's what most security teams are missing: this is not just an APT36 story. Bitdefender's telemetry shows AI-generated malware samples increasing across multiple nation-state groups. Russia, China, North Korea, and Iran have all been observed using LLMs for code generation. The vibeware model is going to spread because it works, it's cheap, and the AI tools that enable it are getting better every quarter.
DEFENSIVE TAKEAWAYS
- 1
Move Past Signatures to Behavioral Detection
Vibeware is engineered to defeat signature-based detection. If your endpoint protection strategy depends on recognizing known malware hashes or patterns, it will fail against AI-generated polyglot variants. Invest in behavioral detection that alerts on anomalous process execution, unsigned binaries running from unexpected paths, and uncommon runtime interpreters appearing on endpoints. The behavior of the malware is more consistent than its code will ever be.
- 2
Monitor Cloud API Traffic From Endpoints
APT36 uses Slack, Discord, Google Sheets, Supabase, and Firebase for C2. You cannot block these services without breaking business workflows. Instead, alert on unexpected outbound API connections from non-developer subnets, processes making cloud storage API calls that are not part of sanctioned workflows, and unusual data upload patterns to cloud platforms. Endpoint telemetry and process lineage are your detection layer here, not network destination blocking.
- 3
Baseline and Alert on Unusual Binary Languages
Most enterprise environments do not run Nim, Zig, or Crystal binaries. Establish a software baseline and alert when executables compiled from these languages appear on endpoints. Look for uncommon runtime installations, unfamiliar compiler artifacts, and executables that do not match your approved software inventory. The presence of exotic language binaries is itself a strong detection signal in most environments.
- 4
Architect for the Assumption That Something Gets Through
The DDoD model explicitly assumes some variants will bypass your perimeter. Your architecture needs to account for that reality. Segment networks so a compromised endpoint cannot reach high-value assets. Enforce least privilege so a foothold does not automatically become domain access. Deploy active SOC monitoring or MDR to catch post-exploitation behavior that vibeware cannot hide, including lateral movement, credential access, and data staging.
- 5
Test Your Stack Against AI-Assisted TTPs
If nation-state actors are using AI to generate malware, your penetration testing should simulate the same approach. Test whether your detection stack can identify implants written in Nim or Crystal. Test whether your SOC alerts on Discord or Google Sheets C2 traffic from an endpoint. If you are not testing against these TTPs, you do not know whether your defenses actually work against them.