Skip to main content
Mallory
Malware1 associated actor1 associated CVE

JDY botnet

Tracked since Feb 17, 2026 · Updated 9 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
Vulns1Associated
Actors1Associated
ATT&CK13Techniques
IOCs2Tracked

JDY botnet is a botnet observed by Dragos being used in a Volt Typhoon–correlated activity cluster tracked as Voltzite. In the reported campaign, the JDY botnet was used to scan public-facing IP address ranges and VPN appliances, targeting organizations in the energy, oil, gas, and defense sectors. Dragos reported no confirmed exploitation during this scanning phase and assessed with moderate confidence that the activity was intended for pre-staging future intrusions and potential operational-data exfiltration.

Is this in your environment?See whether this family's indicators match your telemetry and which of your assets are exposed to the CVEs associated with it.
Check your exposure
Associated CVEs

Associated vulnerabilities

1 CVE Mallory has correlated with this family across public research and vendor advisories. Each card links to the full Mallory page for that vulnerability.

CVE-2026-35616via security online infoAuthentication Bypass and Remote Code Execution in Fortinet FortiClient EMSBlack Lotus Labs found a clear focus on military-related networks, with U.S. military entities the most prominent targets. Most strikingly, the operators ramped up scans of Fortinet devices right after a new flaw, CVE-2026-35616, went public.View vulnerability →Source ↗
Threat actors

Associated threat actors

1 distinct threat actor Mallory has associated with this family across public reporting. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details →
Volt Typhoon

Another campaign involved Voltzite using the JDY botnet to scan for public-facing IP addresses and VPN appliances across energy, oil, gas, and defense sectors.

via scworldscworld.com
MITRE ATT&CK

Techniques & procedures

13 distinct techniques documented for this family, organized by ATT&CK tactic.

Reconnaissance

4 techniques
T1590Gather Victim Network InformationEvidence1

“JDY malware doesn’t directly attack systems. Instead, it collects detailed information about infrastructure to map potential targets. This data is then likely used by other tools to plan exploits, discover vulnerabilities, and carry out actual attacks.”

T1595Active ScanningEvidence1

the botnet now scans the internet for fresh vulnerabilities almost as soon as they are disclosed

T1595.001Scanning IP BlocksEvidence1

Most strikingly, the operators ramped up scans of Fortinet devices right after a new flaw, CVE-2026-35616, went public.

T1595.002Vulnerability ScanningEvidence1

“Black Lotus Labs found a sharp spike in scans of Fortinet devices hours after CVE-2026-35616 was publicly disclosed on April 5, 2026. The botnet didn’t wait for a patch window. It started looking for unpatched devices the same day the flaw became public.”

Execution

1 technique
T1059Command and Scripting InterpreterEvidence1

Some devices are also managed with Platypus, an open-source reverse-shell tool

Stealth

1 technique
T1070.004File DeletionEvidence1

A lightweight dropper script checks the device architecture, fetches the matching payload, and launches it before wiping itself from disk.

Discovery

1 technique
T1046Network Service DiscoveryEvidence3

the bots perform multiprotocol scans that grab service banners, TLS certificates, and other fingerprints

Command and Control

6 techniques
T1071Application Layer ProtocolEvidence1

Once running, the malware beacons to a central “dispatch service” and pulls scanning tasks on demand.

T1071.001Web ProtocolsEvidence1

“The malware itself identifies its host, checks in to the dispatch service via HTTPS with a structured JSON packet describing the system’s OS, architecture, uptime, memory, and malware version, then waits for scanning tasks.”

T1090.002External ProxyEvidence2

Operators run it through hidden Tor services that mask both the control and payload servers.

T1090.003Multi-hop ProxyEvidence2

Because so many bots are legitimate U.S. devices, the JDY botnet blends into normal traffic. Consequently, geofencing, IP reputation filters, and static blocklists struggle to catch it.

T1105Ingress Tool TransferEvidence2

A lightweight dropper script checks the device architecture, fetches the matching payload, and launches it before wiping itself from disk.

T1573Encrypted ChannelEvidence2

it receives encrypted instructions and updated fingerprinting rules

Indicators of compromise

Observables

2 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Values are masked here and available in full in Mallory.

View all in app →
Indicator values are available in Mallory. Pivot on every hash, domain, URL, and IP, or pipe them straight into your SIEM.View all in Mallory
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching2Match every observed IP, domain, and hash against your live telemetry.
Associated threat actors1Groups linked to this family, with evidence pinned to each claim.
Associated vulnerabilities1CVEs linked to this family, with the reporting behind each link.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
MITRE ATT&CK mapping13Every documented technique, ranked by evidence weight.
Researcher chatterReddit, Mastodon, and CTI community discussion around this family.