Skip to main content
Mallory
Malware3 associated actors2 associated CVEs

ShadowRay 2.0

Tracked since Nov 25, 2025 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
Vulns2Associated
Actors3Associated
ATT&CK3Techniques
IOCs5Tracked
Type
Botnet
Capabilities
Credential theftExfiltrationPersistenceInitial accessLateral movementDefense evasionReconnaissanceScanningDDOS
Platforms
LinuxCloud
Also known asShadowRay

ShadowRay 2.0 is a self-propagating, multipurpose botnet operation targeting exposed Ray distributed-computing clusters, particularly Linux-based AI infrastructure with valuable CPU and NVIDIA GPU resources. Documented in November 2025, the operation has been active since at least September 2024. It was initially attributed to an operator tracked as IronErn440 and subsequently linked to TeamPCP.

The infection chain exploits unauthenticated job submission associated with CVE-2023-48022 to execute multistage Bash and Python payloads through exposed Ray dashboards. Ray's maintainers dispute the vulnerability classification because the framework assumes deployment in a trusted network. Malicious jobs enumerate available resources and abuse Ray's orchestration and node-affinity scheduling to execute across cluster nodes, including nodes not directly exposed to the internet. Compromised systems also scan for additional exposed Ray clusters and propagate autonomously.

The operation deploys cryptocurrency miners, including XMRig, and supports cloud and database credential theft, theft of AI models, datasets and source code, interactive control through Python reverse shells, and DDoS attacks using Sockstress. It targets organizations globally, emphasizing large clusters and GPU-rich environments rather than a single industry.

Payloads are distributed and updated through disposable GitLab and GitHub repositories. Persistence uses scheduled tasks and systemd modifications, including periodic retrieval of updated payloads. Defense-evasion measures include masquerading as legitimate system processes, concealing payloads, and limiting CPU consumption to approximately 60 percent. The malware also terminates competing miners and blocks access to competing mining pools to monopolize compromised computing resources.

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

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

CVE-2023-48022via stealthium blogUnauthenticated Remote Code Execution in Ray Jobs API (ShadowRay)The attack's first iteration was first reported in March 2024, and later in November 2025 as ShadowRay 2.0: a self-propagating, multi-purpose botnet that mines on GPUs, steals cloud credentials and models, worms across clusters, and launches DDoS from compromised nodes, all updated in real time from throwaway GitLab and GitHub repos.View vulnerability →Source ↗
CVE-2025-62593via the hacker newsExploited in the wildBrowser-guard bypass leading to remote code execution in RayThe vulnerability in question relates to CVE-2025-62593 (CVSS score: 9.4), which can result in remote code execution via web browsers like Mozilla Firefox and Apple Safari by means of a DNS rebinding attack. | unpatched Ray instances have also been at the receiving end of cyber attacks that aim to turn infected clusters with NVIDIA GPUs into a self-replicating cryptocurrency mining botnet as part of a campaign dubbed ShadowRay 2.0View vulnerability →Source ↗
Threat actors

Associated threat actors

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

View more details →
IronErn440

«Принципиальное отличие: ShadowRay 2.0 - самовоспроизводящийся ботнет. Скомпрометированные Ray-ноды автоматически ищут другие доступные кластеры и распространяют инфекцию.»

via codebycodeby.net
TeamPCP

The firm also assessed that TeamPCP ran ShadowRay 2.0, the campaign it documented in November 2025 against exposed Ray clusters, which it had attributed at the time to an actor called IronErn440.

via infosecurity magazine newsinfosecurity-magazine.com
TA-NATALSTATUS

The firm also assessed that TeamPCP ran ShadowRay 2.0, the campaign it documented in November 2025 against exposed Ray clusters, which it had attributed at the time to an actor called IronErn440.

via infosecurity magazine newsinfosecurity-magazine.com
MITRE ATT&CK

Techniques & procedures

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

Initial Access

1 technique
T1190Exploit Public-Facing ApplicationEvidence1

«Initial Access T1190 (Exploit Public-Facing Application) ... POST к /api/jobs/ на Ray Dashboard»

Impact

2 techniques
T1496.001Compute HijackingEvidence1

«Compute Hijacking (T1496.001, Impact) ... запуск XMRig и других майнеров на GPU»

T1498Network Denial of ServiceEvidence1

AI-Generated Malware Attacks 230,000 Exposed Ray AI Clusters in Massive ShadowRay 2.0 Botnet Campaign ... Ddos

Indicators of compromise

Observables

5 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
Activity feed

Recent activity

12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
codebyNews · Aug 23, 2026Ray Framework уязвимость: CVE-2023-48022 и RondoDoxThe article uses this name for an IronErn440 campaign and describes its operation as a self-propagating botnet targeting exposed Ray clusters. Compromised nodes discover and infect additional clusters, enabling cryptocurrency mining, DDoS, and data exfiltration. Reported evasion includes limiting CPU utilization to approximately 60%, impersonating legitimate Ray workers, and concealing GPU activity. Payload updates use GitLab and GitHub. The campaign is reported active since September 2024; that is not explicitly identified as its discovery date.Read more ↗stealthium blogNews · Aug 20, 2026ShadowRay 2.0: Turning Exposed Ray Clusters Into a GPU-Mining Botnet - and How Stealthium Catches It | StealthiumDescribed as a self-propagating botnet campaign that abuses internet-exposed Ray Jobs APIs to execute attacker-controlled jobs. It deploys miners, steals cloud credentials, model weights and datasets, spreads across nodes and exposed clusters, and launches DDoS attacks. Persistence uses recurring script downloads; evasion includes process-name spoofing, hidden binaries and throttled CPU mining. The original ShadowRay activity was reported in March 2024; ShadowRay 2.0 was documented in November 2025.Read more ↗the hacker newsNews · Aug 18, 2026CISA Flags Actively Exploited Ray Flaw That Can Trigger Browser-Based RCEA campaign targeting unpatched Ray instances to convert NVIDIA GPU-equipped clusters into a self-replicating cryptocurrency mining botnet.Read more ↗infosecurity magazine newsNews · Aug 6, 2026TeamPCP Traced Back to 2020 Cryptojacking Operation - Infosecurity MagazineAn operation against exposed Ray clusters linked by shared infrastructure and deployment paths to TeamPCP activity; later-stage Kubernetes payloads included a destructive branch that deleted filesystems and rebooted machines when systems were set to the Iran timezone.Read more ↗
+8 more in the timeline. Sign up to see them
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
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 matching5Match every observed IP, domain, and hash against your live telemetry.
Associated threat actors3Groups linked to this family, with evidence pinned to each claim.
Associated vulnerabilities2CVEs 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 mapping3Every documented technique, ranked by evidence weight.
Researcher chatterReddit, Mastodon, and CTI community discussion around this family.