Threat reportCampaignTL-2026-1597
ASEC June 2026 Financial Sector Threat Roundup: Phishing-to-Infostealer Chains and Ransomware Dark Web Sales (LAPSUS$, MORPHEUS, Qilin)
AhnLab ASEC's June 2026 financial-sector threat report documents a three-stage attack pattern — phishing, dropper/downloader delivery, then infostealer deployment — targeting Korean and global financial institutions, alongside dark web sales of stolen data attributed to LAPSUS$ (AYA Bank, ~120GB), MORPHEUS (HDFC Asset Management, ~680GB), and Qilin ransomware (Central Bank of Libya).
Key facts
| Identifiers | TL-2026-1597 |
|---|---|
| Also known as | ASEC June 2026 Financial Sector Threat Roundup |
| Severity | MEDIUM |
| Affected products | Multiple Financial sector organizations (email/endpoint users) |
| Weaknesses (CWE) | CWE-1021, CWE-451, CWE-522, CWE-311 |
| Attribution | LAPSUS, MORPHEUS, Qilin (medium confidence) |
| Malware | MORPHEUS ransomware/extortion tooling, Qilin ransomware |
| Tools | Generic HTML-smuggling dropper/downloader, Telegram Bot API |
| MITRE ATT&CK techniques | T1003 OS Credential Dumping, T1005 Data from Local System, T1021 Remote Services, T1027 Obfuscated Files or Information, T1027.006 HTML Smuggling, T1041 Exfiltration Over C2 Channel, T1059.005 Visual Basic, T1059.007 JavaScript, T1078 Valid Accounts, T1082 System Information Discovery, T1087 Account Discovery, T1102 Web Service and 26 more in the attack flow |
| Motivation | FINANCIAL |
| Target sectors | financial services, banking, asset management, insurance, fintech, central banking |
| Target regions | south korea, myanmar, india, libya, canada, united states of america, brazil, North America, Southeast Asia, Africa |
| Detection rules | 9 (1 shown free) |
| Sources | 12 cited sources |
Detection coverage
As of 2026-07-21, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1597 across Splunk SPL, Microsoft KQL and Sigma, covering 24 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: HTML Smuggling Email Attachment — Suspicious Financial-Lure Filenames
Detects inbound email with HTML/JS/EXE/VBE attachments referencing financial-transaction pretexts (wire transfer, receipt, voicemail) consistent with the ASEC-documented Stage 1 phishing vector, where the malicious payload is HTML-smuggled and reconstructed client-side to evade gateway inspection.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1566, T1566.001, T1204.002
- Data sources: email_gateway, o365_message_trace, mimecast, proofpoint
- Severity: high
- Confidence: high
Splunk SPL
index=email sourcetype="ms:o365:message-trace" OR sourcetype="mimecast" OR sourcetype="proofpoint"
| eval attachment_ext=lower(mvindex(split(attachment_name, "."), -1))
| where attachment_ext IN ("html", "htm", "js", "exe", "vbe")
| where match(lower(subject), "transfer|receipt|voicemail|invoice|payment")
| stats count min(_time) as first_seen max(_time) as last_seen values(attachment_name) as attachments by sender, recipient, subject
| where count > 0
| table first_seen, last_seen, sender, recipient, subject, attachments, countMicrosoft KQL
EmailAttachmentInfo
| where TimeGenerated > ago(24h)
| extend Ext = tolower(tostring(split(FileName, ".")[-1]))
| where Ext in ("html", "htm", "js", "exe", "vbe")
| join kind=inner (EmailEvents | where Subject matches regex "(?i)transfer|receipt|voicemail|invoice|payment") on NetworkMessageId
| project TimeGenerated, SenderFromAddress, RecipientEmailAddress, Subject, FileName, Ext, ThreatTypes
| order by TimeGenerated descSigma
title: HTML Smuggling Email Attachment With Financial Lure Subject
id: 7e1c9a2e-1f4b-4c3d-9a6e-8f0c1d2e3a01
status: experimental
description: Detects inbound email attachments (html/js/exe/vbe) paired with financial-transaction lure subjects, consistent with ASEC June 2026 financial-sector HTML smuggling campaign
references:
- https://asec.ahnlab.com/en/94543/
author: Threadlinqs Team
date: 2026-07-21
tags:
- attack.initial-access
- attack.t1566.001
- attack.t1027.006
- attack.defense-evasion
logsource:
category: email
product: any
detection:
selection_ext:
FileName|endswith:
- '.html'
- '.htm'
- '.js'
- '.exe'
- '.vbe'
selection_lure:
Subject|contains:
- 'transfer'
- 'receipt'
- 'voicemail'
- 'invoice'
- 'payment'
condition: selection_ext and selection_lure
falsepositives:
- Legitimate finance-department correspondence with HTML/JS attachments (rare)
level: highKnown false positives:
- Legitimate finance-department correspondence that naturally includes HTML/JS attachments and transaction-related subject lines
Tuning notes: Tune the lure-keyword list per organization language/locale; add a sender-reputation/DMARC-fail join to reduce noise from legitimate internal finance senders.
- LOLBin Child Process of Mail Client/Browser Following Attachment Open · unlock with TL Creds
- Registry Run Key Persistence Written by Uncommon/User-Writable-Path Process · unlock with TL Creds
- Browser Credential Store / Session Cookie File Access by Non-Browser Process · unlock with TL Creds
- Archive Utility Invocation on Harvested Credential Directory Preceding Egress · unlock with TL Creds
- Beacon-Interval HTTP POST to api.telegram.org sendDocument/sendMessage from Non-Bot Host · unlock with TL Creds
- New Egress to api.telegram.org From Host With No Prior Telegram Baseline · unlock with TL Creds
- Embedded JavaScript Blob in HTML Attachment (HTML Smuggling Payload Reconstruction) · unlock with TL Creds
- Suspicious Login-Page Phishing Link Click Followed by Credential Prompt · unlock with TL Creds
Indicators of compromise
As of 2026-07-21, Threadlinqs Intelligence tracks 24 indicators of compromise for TL-2026-1597.
Technical analysis
AhnLab Security Emergency Response Center's (ASEC) June 2026 financial-sector threat roundup consolidates observed intrusion activity against Korean and global financial institutions into a recurring three-stage attack chain. Stage 1 is initial access via phishing — the most prevalent vector — using malicious email attachments (HTML, JS, EXE, VBE file types) and login-page phishing links referencing pretexts such as 'money transfer,' 'receipt,' and 'voicemail' to entice victims. A notable technique observed is HTML smuggling, where the malicious payload is encoded/embedded inside an HTML attachment and reconstructed client-side in the victim's browser to evade network-layer content inspection and email gateway attachment scanning. Stage 2 involves dropper/downloader delivery, frequently leveraging living-off-the-land binaries (LOLBins) already present on the host to fetch and stage the next payload while blending into normal system activity and evading signature-based endpoint defenses. Stage 3 is infostealer deployment, with observed exfiltration of credentials and session/API tokens via the Telegram Bot API — using Telegram channels as a low-cost, hard-to-block C2/exfiltration channel that blends with legitimate encrypted messaging traffic.
In parallel with the intrusion-chain activity, ASEC tracked dark web monetization of stolen financial-sector data across three named threat actor/group brands: LAPSUS$ claimed responsibility for an approximately 120GB data dump from AYA Bank Public Company Limited (Myanmar), encompassing finance, credit card, and payment records. The MORPHEUS ransomware/extortion group claimed exfiltration of approximately 680GB of data from HDFC Asset Management Company (India) — consistent with Morpheus's broader 2026 operating pattern of privately brokering stolen datasets rather than exclusively posting to a public leak site. Qilin ransomware activity was linked to targeting of the Central Bank of Libya. Additional named victim organizations referenced in the report's financial-sector threat landscape include Canada Life, Robinhood, Prudential Financial, an unspecified Brazilian fintech, OneFly, and Bridgepay, alongside compromised access credentials (WordPress, GitHub admin, MSSQL, cloud infrastructure logins) being traded on dark web forums. The primary marketplace for these listings was identified as DarkForums, a database-sharing and stolen-credential forum that emerged as a successor destination after repeated law-enforcement seizures of BreachForums iterations; ASEC noted that accounts tied to the Korean financial sector accounted for roughly 5% of total June 2026 leak listings distributed via Telegram-adjacent channels.
No specific CVE or software vulnerability was disclosed in the ASEC source reporting — the campaign activity is social-engineering and post-exploitation-tooling driven rather than exploit driven. Sensitive data types exposed across the documented breaches include customer names, Social Security Numbers/national ID equivalents, bank account numbers, insurance policy information, and KYC (Know Your Customer) documentation, creating downstream identity-theft, account-takeover, and business-email-compromise risk for affected financial institutions and their customers.
MITRE ATT&CK techniques by tactic:
Credential Access
T1003 OS Credential Dumping; T1539 Steal Web Session Cookie; T1552.001 Credentials In Files; T1555 Credentials from Password Stores; T1621 Multi-Factor Authentication Request Generation
Collection
T1005 Data from Local System; T1119 Automated Collection; T1560 Archive Collected Data
Lateral Movement
Defense Evasion
T1027 Obfuscated Files or Information; T1027.006 HTML Smuggling; T1140 Deobfuscate/Decode Files or Information; T1218 System Binary Proxy Execution
Exfiltration
T1041 Exfiltration Over C2 Channel; T1567 Exfiltration Over Web Service
Execution
T1059.005 Visual Basic; T1059.007 JavaScript; T1204.001 Malicious Link; T1204.002 Malicious File
Initial Access
T1078 Valid Accounts; T1190 Exploit Public-Facing Application; T1566 Phishing; T1566.001 Spearphishing Attachment; T1566.002 Spearphishing Link
Discovery
T1082 System Information Discovery; T1087 Account Discovery
Command and Control
T1102 Web Service; T1102.002 Bidirectional Communication; T1105 Ingress Tool Transfer; T1573 Encrypted Channel
Impact
T1485 Data Destruction; T1486 Data Encrypted for Impact
Persistence
T1547.001 Registry Run Keys / Startup Folder
Resource Development
T1583.001 Domains; T1585.001 Social Media Accounts; T1588.001 Malware
Reconnaissance
T1598 Phishing for Information
defense-impairment
Remediation
Immediate actions
- Block or quarantine inbound emails containing HTML, JS, EXE, and VBE attachments from unauthenticated/external senders
- Enable HTML smuggling detection in email gateway / sandbox (inspect embedded JavaScript blob reconstruction inside .html/.htm attachments)
- Block outbound traffic to api.telegram.org from endpoints/servers with no legitimate Telegram Bot integration business need, or restrict via allow-listed bot tokens
- Force credential rotation and enable MFA (phishing-resistant, e.g. FIDO2) for all financial-sector employee and admin accounts, especially WordPress, GitHub, MSSQL, and cloud console admin logins
- Monitor DarkForums and Telegram leak channels for exposure of organizational credentials and customer PII
Workarounds
- Disable HTML rendering / auto-open for email attachments where feasible; require explicit user action with warning banners for external HTML attachments
Longer-term hardening
- Deploy behavioral/EDR detection tuned to LOLBin abuse chains (e.g. mshta, certutil, regsvr32, rundll32 spawning network connections or writing to user-writable paths)
- Implement DMARC/DKIM/SPF enforcement (p=reject) to reduce phishing-email deliverability
- Deploy data-loss-prevention (DLP) and outbound proxy inspection capable of decrypting/inspecting Telegram API exfiltration channels
- Conduct regular phishing-simulation and security-awareness training focused on financial-transaction pretexts (wire transfer, receipt, voicemail lures)
- Establish dark-web/leak-site monitoring as a standing SOC function for early breach detection
Affected and fixed versions
- Multiple — Financial sector organizations (email/endpoint users)
Vulnerable versions: Organizations without HTML-smuggling-aware email security and LOLBin behavioral detection
Timeline
- Start of the June 2026 reporting window in which ASEC observed elevated phishing-to-infostealer chain activity against financial-sector targets.
- MORPHEUS ransomware/extortion group claims exfiltration of approximately 680GB of data from HDFC Asset Management Company (India).
- LAPSUS$ claims responsibility for an approximately 120GB data dump from AYA Bank Public Company Limited (Myanmar), including finance, credit card, and payment data.
- Qilin ransomware activity linked to targeting of the Central Bank of Libya.
- ASEC observes continued listing of stolen financial-sector credentials (WordPress, GitHub admin, MSSQL, cloud infrastructure) on DarkForums throughout June 2026.
- End of the June 2026 ASEC reporting window; Korean financial-sector accounts found to represent approximately 5% of total June leak listings distributed via Telegram-adjacent channels.
- AhnLab ASEC publishes 'Security Issues in the Korean & Global Financial Sector in June 2026', consolidating the phishing/dropper/infostealer chain and dark web sale findings.
- TL-Intel Harness ingests the ASEC report via RSS-driven hunt phase and opens threat TL-2026-1597 for research.
Sources cited
- Qilin, Software S1242 | MITRE ATT&CK MITRE · Research · 2026-01-01
- LAPSUS$, DEV-0537, Strawberry Tempest, Group G1004 | MITRE ATT&CK MITRE · Research · 2026-01-01
- Qilin Ransomware 2026: TTPs, Victims and Defense Guide moxfive.com · Vendor report · 2026-01-01
- Qilin Ransomware: Group Profile, TTPs, IOCs & Defense (2026) dexpose.io · Vendor report · 2026-01-01
- Scattered LAPSUS$ Hunters: 2025's Most Dangerous Cybercrime Supergroup picussecurity.com · Vendor report · 2025-01-01
- Resecurity Honeypot Incident: Analysis of Scattered Lapsus$ Hunters' Claimed Breach rescana.com · Vendor report · 2026-01-01
- Morpheus Ransomware Strikes HDFC Fund in India dexpose.io · Vendor report · 2026-06-10
- Morpheus Unmasked: Big Game Hunting and Private Data Sales ankura.com · Vendor report · 2026-01-01
- DarkForums › Searchlight Cyber slcyber.io · Vendor report · 2026-01-01
- Threat Brief: Lapsus$ Group Unit 42 · Research · 2025-01-01
- 12 Questions and Answers About darkforums marketplace securityscientist.net · Blog · 2026-01-01
- Security Issues in the Korean & Global Financial Sector in June 2026 asec.ahnlab.com · Report · 2026-07-16
More from LAPSUS
Further reading
Drafted by the Threadlinqs research pipeline from 12 sources; published ; last updated —.