Skip to content

Security Sense

AI Threat Intelligence

  • About
  • Blog
  • Privacy Policy

Tag: phishing

Blinder Tunnel Campaign Targets Iraqi Infrastructure

Posted on October 6, 2026 by Kyle

Overview

The Blinder Tunnel campaign is an Iran-nexus advanced persistent threat (APT) operation primarily targeting critical infrastructure entities within Iraq. This campaign utilizes social engineering tactics, specifically fake recruitment lures, to gain initial access and deploy custom malware that leverages GitHub for command and control (C2). The focus on critical infrastructure highlights the potential for significant operational disruption.

Technical Analysis

Based on the limited public information, the Blinder Tunnel campaign operates as follows:
* Initial Access: Attackers employ spearphishing, using fake recruitment lures purportedly from ‘Dubai Airports’ to entice targets. These lures likely contain malicious attachments or links designed to execute the initial payload.
* Payload Delivery: The specific initial payload mechanism is not detailed, but it leads to the deployment of custom malware.
* Command and Control (C2): The deployed malware utilizes GitHub as its C2 channel. This method can help blend C2 traffic with legitimate network activity, making detection more challenging.
* Targeting: The primary targets are critical infrastructure organizations in Iraq.
Specific malware capabilities, persistence mechanisms, and post-exploitation activities are not publicly detailed at this time.

Detection

Defenders should focus on identifying anomalous activity related to initial access and C2 communications:
* Email Gateway Logs: Monitor for emails with suspicious sender domains, subject lines related to ‘Dubai Airports’ recruitment, or unusual attachment types (e.g., .zip, .iso, .img, .docm).
* Endpoint Detection and Response (EDR) Logs: Look for processes spawned by email clients or document readers that execute unusual commands (e.g., powershell.exe, cmd.exe, script interpreters) or make outbound network connections to non-standard ports or suspicious domains.
* Network Proxy/Firewall Logs: Monitor for outbound connections to github.com or raw.githubusercontent.com from systems not typically involved in software development or IT operations. Look for unusual data transfer volumes or patterns.
* DNS Logs: Identify frequent or unusual DNS queries for GitHub-related domains from non-developer workstations.
* Behavioral Analysis: Hunt for processes attempting to download or execute content directly from GitHub URLs using tools like curl.exe, wget.exe, or Invoke-WebRequest.

Sigma Detection Rules

⚠️ AI-generated detection rules. These are experimental starting points. Review field names, EventIDs, and logic against your environment’s schema before deploying. Tune to reduce false positives.

Suspicious Process Creation from Email or Document Application

title: Suspicious Process Creation from Email or Document Application
id: d7e0f1b2-c3d4-5e6f-7a8b-9c0d1e2f3a4b
status: experimental
description: Detects suspicious processes spawned by common email clients or document viewers, indicative of initial access via malicious attachments or links.
logsource:
  product: windows
  service: sysmon
detection:
  selection:
    ParentImage|endswith:
      - '\outlook.exe'
      - '\word.exe'
      - '\excel.exe'
      - '\powerpnt.exe'
      - '\acrord32.exe'
    Image|endswith:
      - '\powershell.exe'
      - '\cmd.exe'
      - '\wscript.exe'
      - '\cscript.exe'
      - '\mshta.exe'
      - '\rundll32.exe'
      - '\regsvr32.exe'
  condition: selection
level: high

Outbound Connection to GitHub from Suspicious Process

title: Outbound Connection to GitHub from Suspicious Process
id: e8f9a0b1-c2d3-4e5f-6a7b-8c9d0e1f2a3b
status: experimental
description: Detects network connections to GitHub domains from processes not typically associated with web browsing or development, potentially indicating GitHub-based C2.
logsource:
  product: windows
  service: sysmon
  definition: 'The Sysmon event ID 3 (Network connection) should be enabled.'
detection:
  selection_github_domains:
    DestinationHostname|contains:
      - 'github.com'
      - 'raw.githubusercontent.com'
  filter_legitimate_processes:
    Image|endswith:
      - '\chrome.exe'
      - '\firefox.exe'
      - '\msedge.exe'
      - '\iexplore.exe'
      - '\git.exe'
      - '\code.exe' # VS Code
  condition: selection_github_domains and not filter_legitimate_processes
level: medium

Mitigations

  1. User Awareness Training: Educate employees, especially those in critical roles, about spearphishing tactics, fake recruitment lures, and the risks of opening unsolicited attachments or clicking suspicious links.
  2. Email Security Gateway: Implement and configure robust email security solutions to filter malicious emails, identify spoofed sender domains, and scan attachments for known threats.
  3. Endpoint Protection: Deploy EDR solutions capable of detecting and blocking malicious process execution, suspicious child processes, and unusual network connections.
  4. Network Segmentation and Monitoring: Segment critical infrastructure networks to limit lateral movement. Monitor outbound network traffic for connections to known malicious C2 infrastructure and suspicious legitimate services like GitHub from non-standard hosts.
  5. Application Whitelisting: Restrict the execution of unauthorized applications and scripts to prevent the initial payload from running or the C2 malware from executing.

References

  • https://unit42.paloaltonetworks.com/blinder-tunnel-targets-critical-infrastructure/

Indicators of Compromise

No public IOCs available at time of writing.

MITRE ATT&CK

  • T1566.001 — Spearphishing Attachment
  • T1102.001 — Dead Drop Resolver
🤖 AI Attribution
Generated by gemini-2.5-flash ·
1,547 input / 1,476 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in aptTagged apt, critical infrastructure, github, high, iran, malware, phishingLeave a comment

TA419 Impersonates US Officials for AI Cyber Espionage

Posted on October 5, 2026 by Kyle

Overview

TA419, a Chinese state-sponsored threat group, is conducting cyber espionage operations focused on US AI policy. The group’s primary tactic involves sophisticated social engineering, where operatives impersonate US government officials to build trust and establish professional relationships with key individuals. Targets include experts working in US think tanks, universities, and legal organizations involved in AI policy development.

Technical Analysis

TA419’s operations are characterized by advanced social engineering rather than immediate technical exploitation. The core mechanism involves:
* Impersonation: Threat actors create convincing personas of US officials to initiate contact and build rapport with targets.
* Relationship Building: Over time, TA419 establishes seemingly legitimate professional relationships, likely through email correspondence, virtual meetings, and other communication channels.
* Target Selection: The focus is on individuals with access to or influence over AI policy, including researchers, academics, and legal professionals.
* Information Gathering: The ultimate goal is to gather sensitive information, insights, and potentially classified data related to AI policy, research, and development through these established relationships. The source does not specify any particular malware or exploit used post-impersonation, suggesting the primary vector is human interaction and trust exploitation.

Detection

Direct technical detection of the initial impersonation and relationship-building phase is challenging due to its social engineering nature. Detection efforts should focus on behavioral anomalies and user reporting:
* Email Anomaly Detection: Monitor for emails from external senders impersonating known government officials or organizations, especially those with unusual domains or slight misspellings.
* User Reporting: Encourage users to report any suspicious or unsolicited communications, particularly those from individuals claiming to be government officials, even if they appear legitimate.
* Communication Channel Monitoring: Look for unusual or unauthorized communication patterns between employees and external entities, especially those involving sensitive topics.
* Identity Verification: Implement policies requiring verification of identity for new professional contacts, especially those claiming government affiliations, through independent channels.

Mitigations

  1. Security Awareness Training: Conduct regular, targeted training for employees, especially those in sensitive roles or working with critical technologies like AI, on social engineering tactics, impersonation, and the importance of verifying identities.
  2. Email Security Gateway Configuration: Implement and tune email security solutions to detect and flag emails from suspicious domains, those with impersonation attempts (e.g., display name spoofing), and emails containing unusual requests.
  3. Multi-Factor Authentication (MFA): Enforce MFA across all organizational accounts to mitigate the impact of potential credential compromise, should the social engineering escalate to phishing for credentials.
  4. Strict Verification Protocols: Establish and enforce protocols for verifying the identity of new external contacts, particularly those claiming government or high-profile affiliations, through independent means (e.g., official government directories, direct calls to known public numbers).
  5. Information Sharing: Encourage internal and external information sharing regarding observed impersonation attempts and social engineering campaigns to raise collective awareness.

References

  • https://www.darkreading.com/cyberattacks-data-breaches/chinese-actor-impersonates-us-officials-cyber-espionage

Indicators of Compromise

No public IOCs available at time of writing.

MITRE ATT&CK

  • T1566 — Phishing
  • T1589 — Gather Victim Identity Information
🤖 AI Attribution
Generated by gemini-2.5-flash ·
1,486 input / 895 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in aptTagged apt, china, espionage, high, phishing, social engineeringLeave a comment

TA419 Targets U.S. AI Policy Experts with Microsoft AitM Phishing

Posted on October 5, 2026 by Kyle

Overview

TA419, a cyber espionage group linked to China, is actively targeting artificial intelligence (AI) policy experts within U.S. think tanks, universities, and legal organizations. The campaigns utilize sophisticated credential phishing, specifically employing Microsoft AitM techniques, to compromise high-value targets. This activity aims to gain unauthorized access to sensitive information related to U.S. AI policy and research.

Technical Analysis

TA419’s campaigns involve highly tailored spearphishing emails designed to impersonate trusted individuals, including prominent economists, AI policymakers, and employees of AI companies like Anthropic. The primary attack vector is credential phishing, enhanced by Adversary-in-the-Middle (AitM) techniques. This method typically involves:
* Impersonation: Emails sent from spoofed or look-alike domains, or compromised accounts, impersonating known contacts or authoritative figures.
* Phishing Lure: The emails contain links directing targets to malicious login pages that mimic legitimate Microsoft authentication portals.
* AitM Proxy: These malicious pages act as a proxy, forwarding the victim’s credentials to the legitimate service while simultaneously capturing them. This technique can also capture session cookies, potentially bypassing multi-factor authentication (MFA).
* Targeted Individuals: Focus on AI policy experts, suggesting an intelligence gathering objective related to AI development and strategy.

Detection

  • Email Gateway Logs: Monitor for emails originating from external senders with suspicious URLs, particularly those mimicking Microsoft login pages (e.g., login.microsoftonline.com variants, outlook.office365.com variants).
  • Web Proxy/Firewall Logs: Look for connections to newly observed or suspicious domains that resolve to known phishing infrastructure, especially those accessed after clicking links in emails.
  • Authentication Logs (Azure AD, Okta, etc.): Identify successful logins from unusual IP addresses, geographic locations, or devices immediately following a potential phishing attempt. Look for rapid authentication attempts from different locations.
  • Endpoint Detection and Response (EDR): Monitor for suspicious process creation or network connections initiated by web browsers that might indicate interaction with malicious sites or post-compromise activity.
  • User Reporting: Encourage users to report suspicious emails, as they are often the first line of defense against highly targeted phishing.

Sigma Detection Rules

⚠️ AI-generated detection rules. These are experimental starting points. Review field names, EventIDs, and logic against your environment’s schema before deploying. Tune to reduce false positives.

Email Phishing Link Detection – Microsoft Login Impersonation

title: Email Phishing Link Detection - Microsoft Login Impersonation
id: 9a7b6c5d-4e3f-2a1b-0c9d-8e7f6a5b4c3d
status: experimental
description: Detects suspicious URLs in emails that attempt to impersonate Microsoft login pages, a common tactic in AitM phishing.
logsource:
  product: email
detection:
  selection:
    - Subject|contains|all:
        - 'Action Required'
        - 'Microsoft'
        - 'Account'
    - Body|contains|all:
        - 'click here'
        - 'verify'
        - 'update'
    - Url|contains:
        - 'microsoft-login.com'
        - 'office365-verify.net'
        - 'login.live-secure.com'
        - 'portal.office.com.cn'
        - 'login.microsoftonline.com.secure'
  condition: selection
level: high

Suspicious Azure AD Login from New Geolocation

title: Suspicious Azure AD Login from New Geolocation
id: 1a2b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d
status: experimental
description: Detects successful Azure AD logins from a country or region not previously associated with the user, potentially indicating compromised credentials or session hijacking via AitM.
logsource:
  product: azuread
  service: signins
detection:
  selection:
    ResultType: 0 # Successful login
    Status: 'Success'
  filter:
    UserPrincipalName|endswith: '@yourdomain.com' # Adjust to your organization's domain(s)
  # This rule requires historical context for 'new geolocation'.
  # In a real SIEM, this would be a behavioral alert based on baselining user activity.
  # For Sigma, we can look for logins from known high-risk countries or multiple countries in a short period.
  # As a basic example, we'll look for logins from specific high-risk countries.
  condition: selection and not filter
level: high

Mitigations

  1. Implement and Enforce Multi-Factor Authentication (MFA): While AitM can bypass some MFA, it significantly raises the bar for attackers. Prioritize FIDO2/hardware-based MFA where possible, as these are more resistant to AitM attacks.
  2. Advanced Email Security Solutions: Deploy and configure email gateways to detect and block spoofed emails, malicious URLs, and suspicious attachments. Implement DMARC, DKIM, and SPF for organizational domains.
  3. Security Awareness Training: Conduct regular, targeted training for employees, especially high-value targets, on identifying sophisticated phishing attempts, including those impersonating known individuals or services. Emphasize checking URL legitimacy.
  4. Conditional Access Policies: Implement policies that restrict access to sensitive applications based on device health, location, IP address, and other contextual factors.
  5. Monitor Authentication Logs: Actively monitor and alert on suspicious login patterns, such as logins from new geolocations, multiple failed login attempts, or logins from unusual user agents.

References

  • https://thehackernews.com/2026/10/china-aligned-ta419-targets-us-ai.html

Indicators of Compromise

No public IOCs available at time of writing.

MITRE ATT&CK

  • T1566.002 — Spearphishing Link
  • T1078 — Valid Accounts
  • T1539 — Steal Web Session Cookie
🤖 AI Attribution
Generated by gemini-2.5-flash ·
1,540 input / 1,557 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in phishingTagged aitm, apt, china, credential-theft, espionage, high, phishing, ta419Leave a comment

Phishing Abuses RMM Tools for Persistent Access

Posted on September 30, 2026 by Kyle

Overview

This report details recent phishing campaigns observed by Microsoft that exploit legitimate Remote Monitoring and Management (RMM) tools. Attackers are using MSP360 RMM to deploy ScreenConnect, creating redundant and persistent remote access channels. This strategy allows threat actors to maintain control over compromised environments for follow-on activities, posing a significant risk to organizations utilizing or exposed to these tools.

Technical Analysis

  • Initial Access: Phishing campaigns serve as the initial vector, compromising user credentials or tricking users into executing malicious payloads.
  • Tool Deployment: Upon successful initial compromise, attackers deploy MSP360 RMM (formerly CloudBerry Remote Assistant) to gain initial remote control.
  • Redundant Access: MSP360 RMM is then leveraged to deploy ScreenConnect (ConnectWise Control), establishing a secondary, persistent remote access channel.
  • Purpose: This creates multiple avenues for remote control and persistence, enhancing attacker resilience against detection or remediation efforts and facilitating long-term access.
  • Affected Tools: MSP360 RMM, ScreenConnect (ConnectWise Control).

Detection

  • Monitor for the installation of legitimate RMM software (e.g., ScreenConnect.exe, cbsa.exe for MSP360 RMM) on endpoints where it is not explicitly authorized or expected by IT administration.
  • Look for suspicious process parent-child relationships, such as powershell.exe or cmd.exe spawning RMM installer executables or their agents.
  • Analyze network traffic for connections from RMM tool processes to unexpected or unapproved external IP addresses or domains.
  • Review endpoint logs for unusual service creations or modifications related to RMM tools, especially those configured for automatic startup.
  • Hunt for ScreenConnect.exe or cbsa.exe processes running on non-IT administration workstations or servers.

Sigma Detection Rules

⚠️ AI-generated detection rules. These are experimental starting points. Review field names, EventIDs, and logic against your environment’s schema before deploying. Tune to reduce false positives.

Suspicious RMM Agent Process Creation

title: Suspicious RMM Agent Process Creation
id: 4d1e2f3a-5b6c-4d8e-9f0a-1b2c3d4e5f6a
status: experimental
description: Detects the creation of processes associated with legitimate RMM tools (ScreenConnect, MSP360 RMM) that could be abused by attackers.
logsource:
  product: windows
  service: sysmon
detection:
  selection:
    EventID: 1
    Image|endswith:
      - '\ScreenConnect.exe'
      - '\cbsa.exe'
  condition: selection
level: high

RMM Tool Initiating Network Connection

title: RMM Tool Initiating Network Connection
id: 7e8f9a0b-1c2d-3e4f-5a6b-7c8d9e0f1a2b
status: experimental
description: Detects network connections initiated by ScreenConnect or MSP360 RMM agents, which could indicate active remote control or data exfiltration.
logsource:
  product: windows
  service: sysmon
detection:
  selection:
    EventID: 3
    Image|endswith:
      - '\ScreenConnect.exe'
      - '\cbsa.exe'
  condition: selection
level: medium

Mitigations

  1. User Awareness Training: Educate users on identifying and reporting phishing attempts, especially those involving social engineering tactics to install software or grant remote access.
  2. Multi-Factor Authentication (MFA): Implement MFA for all remote access services, critical accounts, and RMM tool access to prevent unauthorized access even if credentials are stolen.
  3. Endpoint Detection and Response (EDR): Deploy EDR solutions to monitor for suspicious process execution, file modifications, and network connections indicative of RMM tool abuse.
  4. Application Whitelisting/Control: Restrict the execution of unauthorized applications, including RMM tools, to only approved software and specific user groups.
  5. Network Segmentation: Isolate critical systems and segment networks to limit lateral movement and the scope of compromise if an endpoint is breached.
  6. Monitor RMM Tool Usage: Strictly monitor and audit the legitimate use of RMM tools, ensuring they are only deployed and accessed by authorized personnel from approved locations and for documented purposes.

References

  • https://www.microsoft.com/en-us/security/blog/2026/09/29/phishing-abuses-rmm-tools-persistent-access/

Indicators of Compromise

No public IOCs available at time of writing.

MITRE ATT&CK

  • T1566.001 — Spearphishing Attachment
  • T1219 — Remote Access Tools
  • T1133 — External Remote Services
🤖 AI Attribution
Generated by gemini-2.5-flash ·
1,587 input / 1,277 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in phishingTagged high, msp360, persistence, phishing, rmm, screenconnect, windowsLeave a comment
Proudly powered by WordPress | Theme: micro, developed by DevriX.