Weekly Threat Intel
June 6–12, 2026
- Block the APT36 "Operation TrustTrap" infrastructure pattern, not just the domains — the operation runs 16,800+ lookalike domains impersonating government services, and the naming convention is the durable detection. The 221 indicators extracted from this single report follow a structural pattern: a legitimate-looking host label followed by a hyphenated three-letter random suffix on a cheap TLD, e.g.
www[.]mass[.]gov-suc[.]cc,www[.]az[.]gov-lzk[.]cc, and dozens moregov-XXX[.]ccpermutations. A curated blocklist of today's domains will be stale tomorrow at this scale; instead, build a detection for the registration template —*gov-???.cc-style patterns, bulk registrations on.cc/cheap TLDs spoofing government-service keywords — and feed it to DNS filtering and brand-monitoring. Warn staff that credential and payment-data harvesting pages will mimic state government and tax portals. - Patch the WinRAR path-traversal flaw CVE-2025-8088 now if you haven't — it is being actively exploited against Ukrainian organizations to deliver the GIFTEDCROOK stealer, and it is being chained with older WinRAR bugs (CVE-2025-6218, CVE-2018-20250). The infection drops a malicious
.lnkand stages a PowerShell-in-PowerShell loader that reads a payload fromC:\ProgramData\KKN(iex (gc 'C:\ProgramData\KKN' -raw)) and beacons to hardcoded IP:port C2 such as166[.]0[.]132[.]237:7044and136[.]0[.]141[.]41:9580. Archive-extraction utilities are an under-managed attack surface; inventory WinRAR versions across the fleet, force-update to a patched build, and alert on PowerShell launched from extracted archive contents. - If you run Cisco Secure Firewall / ASA, assume firmware upgrades alone do not evict UAT-4356 — the FIRESTARTER backdoor (via CVE-2025-20333 and CVE-2025-20362) survives reboots and firmware updates. Hunt for the implant directly: check for the
lina_csprocess and/usr/bin/lina_cson disk (show kernel process | include lina_cs), and inspect/opt/cisco/config/platform/rmdb/CSP_MOUNT_LISTandsvc_samcore.logfor tampering. Patching closes the door; it does not clean a device that was already compromised. Treat any previously-exposed ASA/FTD appliance as needing active backdoor hunting, not just a version bump. - Audit your OAuth device-authorization-grant and AiTM exposure across every identity provider — this week produced an AiTM credential-harvesting kit (84 IOCs) targeting Microsoft 365 / Entra ID, a device-code phishing forensics writeup, and Storm-2755 chaining AiTM with CVE-2025-27152 to hijack sessions and redirect payroll. The AiTM kit uses CAPTCHA gating and recruitment/RFQ lures across domains like
documentfiles-rfq[.]comandaccounts-recruitmentportal[.]com, even spoofing Amazon Midway SSO. Push-based MFA does not stop token theft. Restrict device-code grants to managed devices, deploy phishing-resistant MFA (FIDO2/passkeys), and add Conditional Access that binds tokens to compliant devices — at Entra, Okta, and every IdP you operate. - Treat destructive wipers as a live, geopolitically-triggered risk to operational technology — this week saw Handala claim a wiper attack on GCC critical infrastructure (destroying 6 PB, exfiltrating 149 TB) and a separate "Lotus Wiper" campaign against Venezuelan energy and utilities. Both used the same playbook: batch scripts to weaken defenses, then a data-destroying payload. Wiper resilience is a backup-and-recovery problem, not only a prevention problem. Verify offline, immutable backups for OT and critical systems; test restoration; segment IT from OT; and alert on mass-deletion / batch-driven defense-weakening behavior (Defender tampering, shadow-copy deletion) as a pre-wipe signal.
- Extend supply-chain vigilance beyond npm/PyPI to the Rust ecosystem — the
oneringcrate (v1.4.1) was trojanized with a maliciousbuild.rsthat exfiltrates git metadata and source-code diffs to an attacker-controlled Sentry ingest endpoint. The build script runsgit logandgit diff HEAD^ HEADat compile time and ships the output too4511539639222272.ingest.de.sentry[.]io. Build-time code execution (build.rs, npm install scripts, setup.py) is a blind spot for most CI pipelines. Pin and vet dependency versions, run builds in egress-restricted sandboxes, and alert on build steps making outbound network calls — especially to telemetry/ingest endpoints that have no business in your toolchain.
- Operation TrustTrap: APT36's 16,800-Domain Credential-Harvesting Machine
- The Espionage Wave: GREYVIBE, Dragon Weave, SideCopy, Mustang Panda, and Iran
- Destructive Operations: Handala on the GCC and the Lotus Wiper in Venezuela
- Ransomware at Scale: Qilin, The Gentlemen, CMD Organization, and MLTBackdoor
- Identity & the Edge: AiTM Kits, Device-Code Phishing, WinRAR, and a Firmware Backdoor
- Also Worth Tracking: Poisoned Rust Crate, PhaaS, and World Cup Scams
Operation TrustTrap: APT36 Weaponizes 16,800+ Spoofed Government Domains
The week's largest single submission — 221 indicators, the most of any report — documented Operation TrustTrap, a Pakistan-nexus APT36 (Transparent Tribe) campaign that registered more than 16,800 spoofed domains impersonating government services to harvest credentials and payment-card data. What distinguishes this operation is not a novel technique but raw scale: an infrastructure footprint large enough that any conventional, enumerate-and-block response is obsolete before it ships.
16,800+ Government-Service Lookalikes Built on a Repeating Domain Template
The campaign impersonates government and state-service portals to collect login credentials and payment data from victims. The 221 IOCs extracted are overwhelmingly domains following a single algorithmic template: a legitimate-looking government host label followed by a hyphenated three-letter random suffix on the cheap .cc TLD. Representative examples include www[.]mass[.]gov-suc[.]cc, www[.]mass[.]gov-ypk[.]cc, www[.]az[.]gov-lzk[.]cc, www[.]az[.]gov-cgt[.]cc, and www[.]gov-lzk[.]cc — with thousands of additional permutations cycling the suffix. At 16,800+ domains, this is a generation-and-rotation operation: blocking today's set leaves tomorrow's untouched. The defensive value of the report is the pattern, not the list.
*gov-???.cc on cheap TLDsUNC3753 Vishes US Law Firms, Deploys RMM Tools, and Extorts on Stolen Data
Google's Threat Intelligence Group tracked UNC3753 targeting US law firms through vishing and social engineering to obtain remote access, then deploying legitimate RMM tooling for hands-on-keyboard data theft and extortion. The chain abuses SuperOps.msi (pulled via curl ... && msiexec /i "SuperOps.msi" /quiet) and Windows365.exe, with privnote[.]com for ephemeral comms and a leak threat staged at business-data-leaks[.]com (192[.]236[.]147[.]131 / .138). Law firms hold privileged, high-leverage data, and the human-voice initial access bypasses email controls entirely — the detectable artifact is unsanctioned RMM software appearing in the environment.
business-data-leaks[.]com · Hunt: unsanctioned RMM installsOperation TrustTrap is a case study in why indicator scale has broken the enumerate-and-block model for cheap-infrastructure campaigns. When an actor can generate 16,800 domains from a template and rotate them faster than a blocklist can be curated and distributed, the indicators themselves are nearly disposable — their value is in revealing the generation algorithm. The durable defense is a pattern-based detection: a regex or DNS-filter rule for government-keyword-plus-random-suffix domains on low-cost TLDs, paired with brand-protection monitoring for newly-registered lookalikes of your portals. Pair this with user education that government and tax services will never be reached through a hyphenated .cc domain. The same logic applies to the SniperDz PhaaS ecosystem (Section 06): when phishing infrastructure is industrially generated, defenders must detect the factory, not catalogue the products.
The Espionage Wave: Six Campaigns, Six Theaters
The defining feature of this week was the concentration of nation-state espionage reporting. Six distinct campaigns surfaced in iocget submissions, each tied to an active geopolitical fault line and each illustrating a different tradecraft choice — from cloud-native C2 to fileless loader chains to repurposed commodity RATs.
| Campaign / Actor | Targeting | Notable Technique | Malware |
|---|---|---|---|
| GREYVIBE (Russia-nexus) | Ukraine and related entities | Dynamic-DNS C2 (linkpc[.]net, work[.]gd); themed lure domains |
PhantomRelay, FallSpy |
| Operation Dragon Weave | Taiwan and the Czech Republic | Azure Blob Storage as C2 (*.blob.core.windows[.]net); DLL sideloading |
AZUREVEIL, RUSTCLOAK |
| Operation XENOFISCAL (SideCopy) | Afghan Ministry of Finance | Spear-phishing → fileless loader chain (mshta.exe → .hta → .bat); Run-key persistence |
XenoRAT |
| Iranian-nexus intrusion | Omani government ministries | DotNetNuke + ProxyShell exploitation → webshells & C2 frameworks | Webshells / C2 implants |
| Mustang Panda | India and South Korea | Banking-themed CHM files; DLL sideloading; dynamic API resolution | LOTUSLITE v1.1 |
| Lotus Wiper operator | Venezuela (energy/utilities) | Batch scripts to weaken defenses → data-wiping payload | Lotus Wiper (destructive) |
GREYVIBE Targets Ukraine With PhantomRelay and FallSpy via Dynamic-DNS C2
The week's second-largest report (180 IOCs) profiled GREYVIBE, a Russia-nexus group targeting Ukraine and related entities for information theft and espionage using the PhantomRelay and FallSpy malware families. The infrastructure leans heavily on free dynamic-DNS providers — dsszzi[.]linkpc[.]net, declaration[.]linkpc[.]net, edbo[.]work[.]gd — alongside themed lure domains (doct0rsim[.]com, routinesyscheckup[.]com). Dynamic-DNS C2 is cheap and fast to rotate but leaves a clear hunt opportunity: enterprise hosts resolving linkpc[.]net / work[.]gd subdomains are anomalous in almost every environment.
linkpc[.]net, work[.]gd) · Hunt: DDNS resolution from corporate hostsDragon Weave Hides C2 in Azure Blob Storage to Spy on Taiwan and the Czech Republic
Operation Dragon Weave (18 IOCs) used the AZUREVEIL and RUSTCLOAK malware families with command-and-control fronted through Azure Blob Storage (e.g. note1ggbbhggdwa1[.]blob[.]core[.]windows[.]net), delivered via DLL sideloading using a renamed UnityPlayer.dll and loaders such as RuntimeBroker_update.exe and BrowserViewUtility.exe. Living-off-trusted-cloud C2 is the recurring espionage pattern of 2026: blocking *.blob.core.windows.net wholesale is infeasible, so detection must shift to the host sideloading chain and to anomalous blob-storage access from endpoints with no legitimate Azure workload.
UnityPlayer.dll sideloading · Targets: Taiwan, Czech RepublicThe clustering of six espionage campaigns in a single week is itself the signal — and the shared tradecraft thread is the abuse of trusted, free, or cloud-native infrastructure to evade reputation-based controls. Dragon Weave uses Azure Blob Storage; GREYVIBE uses free dynamic-DNS; SideCopy's XENOFISCAL chains native Windows binaries (mshta.exe) for a fileless loader; the Iranian Oman intrusion rode known exploits (ProxyShell, DotNetNuke) into webshells. None of these are blockable by domain or IP reputation alone. The durable detections are behavioral and host-based: DLL sideloading from renamed signed binaries, mshta.exe spawning scripts, Run-key persistence writes, and outbound calls to cloud-storage or dynamic-DNS endpoints that have no business justification on the originating host. For organizations with any nexus to Ukraine, Taiwan, the Gulf, or South Asia, this week is a prompt to validate that these behavioral detections are deployed and tuned.
Wipers Return: Handala on the GCC and the Lotus Wiper in Venezuela
Two destructive wiper operations surfaced this week, both tied to active geopolitical conflict and both following the same operational arc: degrade defenses with scripting, then destroy data. After a period dominated by data-theft extortion, the re-emergence of pure destruction as an objective is a notable shift in adversary intent.
Handala Claims 6 PB Destroyed and 149 TB Exfiltrated From GCC Critical Infrastructure
The pro-Palestinian Handala Hack Team claimed a destructive wiper attack against Gulf Cooperation Council (GCC) critical infrastructure, asserting the destruction of 6 petabytes of data and exfiltration of 149 terabytes. The 23 IOCs include the group's own infrastructure — handala[.]to, handala-hack[.]to, handala-alert[.]to, handala-redwanted[.]to — and operational endpoints including api.telegram[.]org for exfiltration/notification and IP 107[.]189[.]19[.]52. Whether or not the headline volumes are fully accurate, the targeting of regional critical infrastructure for destruction (not ransom) is the strategically significant element.
Lotus Wiper Hits Venezuelan Energy and Utilities via Batch-Script Defense Degradation
A separate destructive campaign dubbed Lotus Wiper (13 IOCs) targeted energy and utilities organizations in Venezuela, using batch scripts to weaken defenses before deploying a data-wiping payload. The two-stage arc — scripted defense degradation followed by destruction — mirrors the Handala operation and is the recurring wiper signature: the pre-wipe phase (Defender tampering, service disabling, shadow-copy deletion) is where defenders have a detection window before irreversible damage occurs. Energy and utilities targeting underscores that OT-adjacent environments are squarely in scope.
The return of wipers reframes the recovery question: against a destruction-motivated adversary, your last line of defense is not prevention but restoration. Both campaigns this week front-loaded a scripted defense-degradation phase — disabling security tooling and clearing recovery options — before the destructive payload, which is precisely the detection opportunity: mass shadow-copy deletion, batch-driven Defender/AV tampering, and rapid service-stopping are high-fidelity pre-wipe signals that warrant an immediate, automated response (isolate the host before the second stage runs). Beyond detection, the controlling defense is recovery architecture: offline, immutable, tested backups for critical and OT-adjacent systems, with documented and rehearsed restoration procedures. Organizations in regions exposed to current conflicts (the Gulf, Venezuela, and the broader Russia–Ukraine and Iran-aligned theaters) should treat wiper resilience as a near-term, board-level priority rather than a tabletop hypothetical.
Ransomware at Scale: Qilin, The Gentlemen, CMD Organization, and MLTBackdoor
The criminal ransomware economy continued its relentless throughput, with Qilin reaffirming its position as the top global operation, a fast-scaling new RaaS brand (The Gentlemen), a new healthcare-focused operator (CMD Organization), and a fresh ransomware-adjacent malware family (MLTBackdoor).
Qilin Holds the Top Global Ransomware Spot With Triple Extortion and Edge-Device Zero-Days
The week's third-largest report (152 IOCs) assessed Qilin as the top global ransomware threat, operating a triple-extortion model (encryption + data leak + DDoS/pressure), exploiting zero-days and known edge-device CVEs for entry, and embedding PsExec for lateral movement. The exploited CVE set includes CVE-2025-31324 (SAP NetWeaver), CVE-2024-55591 (Fortinet), CVE-2024-21762 (FortiOS), and CVE-2023-27532 (Veeam) — a reminder that ransomware initial access remains anchored in unpatched perimeter and backup infrastructure. The IOC set provides current C2 IPs (e.g. 184[.]174[.]96[.]74, 184[.]174[.]96[.]67) for hunting.
The Gentlemen: A New RaaS Brand Scaling Fast via Edge-Device Exploitation
The Gentlemen (59 IOCs) is a rapidly scaling ransomware-as-a-service operation targeting multiple platforms, gaining entry through edge-device exploitation and using SystemBC and Cobalt Strike for C2 and lateral movement. The toolset is conventional commodity-RaaS — which is exactly the point: a new brand reaching scale this quickly on off-the-shelf tradecraft shows the RaaS supply chain is mature enough that operational velocity, not novel capability, is the differentiator. SystemBC and Cobalt Strike beacons remain among the highest-value hunt targets in any environment.
CMD Organization Targets US Healthcare With a Novel Crypto-Bidding Extortion Platform
CMD Organization (37 IOCs) is a new ransomware operator focused on US healthcare, running double extortion with a novel cryptocurrency-bidding platform for monetizing stolen data, and using StealC and the Meow backdoor in its toolkit. The crypto-bidding monetization twist signals continued innovation in the extortion business model, while the healthcare focus continues the sector's grim run as a preferred target. Separately, Zscaler's MLTBackdoor (19 IOCs) — a new, heavily-obfuscated family with DGA and a BOF loader for post-exploitation — was assessed as likely tied to ransomware operations.
Identity and the Edge: AiTM Kits, Device-Code Phishing, WinRAR, and a Firmware Backdoor
Two perennial pressure points — identity (token theft, MFA bypass) and the network edge (exposed appliances, archive utilities) — each produced significant reporting this week, including an actively-exploited WinRAR flaw and a Cisco firewall backdoor engineered to survive the very firmware updates meant to evict it.
AiTM Kit Harvests M365 Sessions Behind CAPTCHA Gates and Recruitment Lures
DomainTools dissected an Adversary-in-the-Middle credential-harvesting kit (84 IOCs) targeting Microsoft 365 and Entra ID identities, using CAPTCHA gating and corporate-email-filter evasion. The lure infrastructure leans on RFQ/recruitment themes — documentfiles-rfq[.]com, rfq-quotationportal[.]com, accounts-recruitmentportal[.]com, filedocx[.]homes — and the kit even reverse-proxies Amazon's Midway SSO flow. Because the victim authenticates against the real login.microsoftonline[.]com while the proxy steals the resulting session token, push-MFA offers no protection; only phishing-resistant (FIDO2) MFA and device-bound tokens break the chain.
FIRESTARTER Backdoor Survives Cisco Firmware Upgrades and Reboots
UAT-4356 exploits CVE-2025-20333 and CVE-2025-20362 in Cisco Secure Firewall appliances to deploy FIRESTARTER, a backdoor engineered to persist across firmware upgrades and reboots (11 IOCs). The implant manifests as a lina_cs process and the file /usr/bin/lina_cs, and tampers with /opt/cisco/config/platform/rmdb/CSP_MOUNT_LIST and svc_samcore.log. The operational lesson is stark: patching the CVEs closes the entry vector but does not remove an already-installed FIRESTARTER. Previously-exposed appliances require active on-box hunting (show kernel process | include lina_cs), not just a version check.
lina_cs implant · Survives firmware upgrade + reboot · Hunt on-box, don't just patchOld WinRAR Path-Traversal Flaw Fuels GIFTEDCROOK Attacks on Ukraine
Trend Micro reported SHADOW-EARTH-066 and Earth Dahu exploiting the WinRAR vulnerability CVE-2025-8088 (chained with CVE-2025-6218 and the 2018-era CVE-2018-20250) to target Ukrainian organizations with the GIFTEDCROOK stealer and espionage tooling (57 IOCs). The chain drops a crafted .lnk, runs a nested PowerShell loader (iex (gc 'C:\ProgramData\KKN' -raw)), and beacons to hardcoded C2 such as 166[.]0[.]132[.]237:7044 and 136[.]0[.]141[.]138:8406. Archive utilities are a soft, under-patched target — inventory and force-update WinRAR fleet-wide.
C:\ProgramData\KKN · Target: UkraineThe week's identity and edge stories share one uncomfortable theme: the control you trust to fix the problem isn't the control that solves it. Push-MFA does not stop AiTM token theft (you need phishing-resistant MFA and device-bound tokens); a firmware upgrade does not evict FIRESTARTER (you need on-box backdoor hunting); and patching WinRAR going forward does not undo a compromise that already arrived through a malicious archive. In each case the assumed remediation addresses the entry vector while leaving the established foothold or the bypassed control intact. The corrective posture is to pair every patch-or-policy fix with an explicit "assume-breach" verification step: after patching exposed appliances, hunt for implants; after deploying MFA, confirm it's the phishing-resistant kind and that legacy/device-code flows are constrained; after blocking a delivery vector, hunt for the payloads it may have already delivered.
Also Worth Tracking
onering
Trojanized onering Crate Exfiltrates Source-Code Diffs at Build Time
The Rust crate onering v1.4.1 was compromised with a malicious build.rs that runs at compile time, harvesting git commit metadata (git log -n 1 ...) and source-code diffs (git diff HEAD^ HEAD) and exfiltrating them to an attacker-controlled Sentry ingest endpoint (o4511539639222272.ingest.de.sentry[.]io). Build-script code execution is a CI blind spot across ecosystems — run builds in egress-restricted sandboxes and alert on toolchain steps making outbound calls to telemetry/ingest endpoints.
onering v1.4.1 · Malicious build.rs · Exfil to Sentry ingest · Source-code diff theftSniperDz: A Centralized PhaaS Platform Monetizing Traffic Multiple Ways
Group-IB profiled SniperDz, a centralized phishing-as-a-service platform offering ready-made templates and monetizing victim traffic through browser-notification abuse, premium-SMS subscriptions, and investment scams. Like APT36's domain factory (Section 01), SniperDz is industrial-scale phishing infrastructure where the defensive priority is detecting the platform's templates and traffic-monetization patterns rather than chasing individual landing pages. Also tracked: SilabRAT, a MaaS RAT (HVNC, browser-profile cloning, crypto theft) sold on dark-web forums, and a fresh wave of 2026 FIFA World Cup phishing and fake-store scams.
Taken together, this week describes a threat landscape moving in lockstep with geopolitics — and scaling past the limits of indicator-by-indicator defense. A single actor running 16,800 domains, six espionage campaigns mapped to active conflicts, two infrastructure wipers, a fast-scaling RaaS ecosystem, and a centralized PhaaS platform all point to the same operational reality: adversary infrastructure is now generated and rotated industrially, and trusted/cloud-native services (Azure Blob, dynamic-DNS, Sentry, native Windows binaries) are the preferred evasion layer. The controls that map to this model are pattern-based and behavioral: detect the domain-generation template rather than the domains; hunt for sideloading, fileless loader chains, and pre-wipe defense degradation rather than for static C2; and verify remediation with assume-breach hunting rather than trusting a patch or a push-MFA toggle. For any organization with exposure to the week's geographies — Ukraine, the Gulf, Taiwan, South Asia, Latin America — the conflict map is now a credible part of the threat model.
Analyst Assessment: June 6–12 in Context
The week's signal is the geopoliticization of the threat landscape: the calendar's conflicts are now a reliable predictor of the week's campaigns. Russia-nexus GREYVIBE and WinRAR-borne GIFTEDCROOK against Ukraine; Iranian-aligned intrusion against Oman; SideCopy against Afghanistan; Mustang Panda against India and South Korea; Dragon Weave against Taiwan and the Czech Republic; Handala's destructive operation against the GCC; and a wiper against Venezuela's energy sector — this is not a coincidental cluster but a direct mapping of active geopolitical fault lines onto cyber operations. For threat-intel and SOC teams, the practical consequence is that geographic and sectoral exposure should now feed prioritization explicitly: an organization with operations or partners in a current conflict zone faces a materially elevated, attributable threat this week, not a hypothetical one.
The scale of APT36's Operation TrustTrap is the structural milestone, and it confirms that the enumerate-and-block model has broken for cheap-infrastructure campaigns. 16,800+ template-generated domains cannot be defended against by curating blocklists; they can only be defended against by detecting the generation algorithm and the registration pattern. This is the same lesson the SniperDz PhaaS ecosystem teaches from the criminal side. The shift required is from indicator catalogues to pattern detection — regex-based DNS filtering, registration-anomaly monitoring, and brand-protection tooling that flags newly-registered lookalikes of an organization's own properties. Teams still measuring threat-intel value by raw indicator volume should recalibrate toward pattern and behavior coverage.
FIRESTARTER's firmware persistence and the return of wipers together underline that remediation must assume breach, not assume the fix worked. A backdoor that survives the firmware upgrade meant to remove it, and destructive operations that front-load defense-degradation before an irreversible wipe, both punish organizations that treat a single corrective action (patch, reboot, AV alert) as closure. The durable posture is verification: hunt on-box after patching exposed appliances; treat pre-wipe behaviors (mass shadow-copy deletion, scripted Defender tampering) as immediate-isolation triggers; and ensure offline, immutable, tested backups exist for the critical and OT-adjacent systems that wipers target. Recovery capability is now a primary control, not a fallback.
What to do this week: (1) Deploy a pattern-based detection for APT36-style government-lookalike domains (government keyword + hyphenated random suffix on cheap TLDs such as .cc) to DNS filtering and brand monitoring. (2) Inventory and force-update WinRAR fleet-wide to patch CVE-2025-8088, and alert on PowerShell launched from extracted archive contents. (3) Hunt previously-exposed Cisco Secure Firewall / ASA appliances for FIRESTARTER (lina_cs process, /usr/bin/lina_cs, tampered CSP_MOUNT_LIST) — do not assume a firmware update cleaned them. (4) Verify offline, immutable, tested backups for critical and OT-adjacent systems, and alert on pre-wipe defense-degradation behavior (shadow-copy deletion, batch-driven AV tampering). (5) Move identity from push-MFA to phishing-resistant (FIDO2) MFA with device-bound tokens, and constrain OAuth device-code grants at every IdP, given the AiTM kit, device-code phishing, and Storm-2755 reporting. (6) Run builds in egress-restricted sandboxes and alert on build-time outbound calls (the onering Rust crate lesson). (7) Hunt for state-espionage behavioral signatures — DLL sideloading from renamed signed binaries, mshta.exe launching scripts, and outbound calls to Azure Blob Storage or dynamic-DNS endpoints from hosts with no business justification.
Sources
- CYFIRMA / Threat Intelligence — Operation TrustTrap: APT36 Weaponizes 16,800 Spoofed Domains
- Threat Intelligence (TA2026153) — GREYVIBE: Russia-Nexus Campaign Targeting Ukraine (PhantomRelay, FallSpy)
- Threat Intelligence (TA2026155) — Qilin Ransomware: Global Dominance and Triple Extortion
- Threat Intelligence (TA2026152) — Operation Dragon Weave: AZUREVEIL & RUSTCLOAK Against Taiwan and the Czech Republic
- Threat Intelligence (TA2026150) — Operation XENOFISCAL: SideCopy Adopts XenoRAT Against the Afghan Ministry of Finance
- Threat Intelligence (TA2026151) — Iranian-Nexus Espionage Intrusion Targeting Omani Government Ministries
- Threat Intelligence — Mustang Panda LOTUSLITE v1.1: Banking-Themed CHM Campaign Against India and South Korea
- Threat Intelligence (TA2026157) — CMD Organization: New Healthcare-Focused Ransomware With Crypto-Bidding Extortion
- The Gentlemen Ransomware — The Gentlemen Ransomware: A Rapidly Scaling RaaS Threat
- Handala Hack Team Analysis — Handala Claims Destructive Wiper Attack on GCC Critical Infrastructure
- Lotus Wiper Analysis — Lotus Wiper Targets Venezuelan Energy and Utilities
- Trend Micro — Old WinRAR Flaw (CVE-2025-8088) Fuels Attacks on Ukraine
- Cisco / UAT-4356 Analysis — Patched but Not Cured: FIRESTARTER Backdoor Survives Cisco Firewall Upgrades
- DomainTools — Security Snacks: Hijacking Corporate Sessions With an AiTM Kit
- Eye Security — Device Code Phishing Forensics
- Storm-2755 Analysis — Storm-2755 Payroll Heist: AiTM + CVE-2025-27152 Session Hijacking
- Google Threat Intelligence — UNC3753: Targeted Vishing Campaign Against US Law Firms
- Zscaler ThreatLabz — Technical Analysis of MLTBackdoor
-
Aikido Security —
Compromised Rust Crate
oneringPerforms Code Exfiltration - Group-IB — Inside the SniperDz PhaaS Ecosystem
- Group-IB — SilabRAT: HijackLoader Trojan Sold as Malware-as-a-Service
- Huntress — Malspam to Fileless .NET Loader: Delivery Chain Analysis
- SANS Internet Storm Center — Evil MSI: Background-Image Payload via WeTransfer
- CyberPress — 2026 FIFA World Cup Scam Surge
This post was generated with Claude by Anthropic, based on source reporting from the publications listed above and analysis of 27 IOC submissions to iocget.com between June 6–12, 2026.