Skip to content

Security Sense

AI Threat Intelligence

  • About
  • Blog
  • Privacy Policy

Category: apt

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

MI5 Warns of China’s MSS Funding UK Academic Research for Intelligence

Posted on October 5, 2026 by Kyle

Overview

The U.K.’s MI5 has issued a “Security Service Espionage Alert” concerning the China General Technology Research Institute (CGTRI) and its activities within the British academic sector. Over 100 UK-linked academics are reported to have participated in research funded by CGTRI, which MI5 assesses as a front for China’s Ministry of State Security (MSS) to bolster its intelligence gathering capabilities. This alert highlights a non-traditional vector for state-sponsored intelligence collection, leveraging academic collaboration.

Technical Analysis

The threat described is primarily an intelligence gathering operation leveraging academic research funding.
* Actor: China’s Ministry of State Security (MSS)
* Front Organization: China General Technology Research Institute (CGTRI) 中国通用技术研究院
* Vector: Funding academic research projects within the U.K.
* Target: Over 100 U.K.-linked academics.
* Objective: To boost China’s intelligence gathering efforts, likely through access to research, expertise, and potentially sensitive information or networks within the academic and broader U.K. landscape.
* Mechanics: CGTRI provides financial support for research, which then serves the strategic intelligence objectives of the MSS. The specific nature of the research or how it directly contributes to intelligence gathering is not detailed in the provided source.

Detection

Given the nature of this threat as an intelligence gathering operation leveraging academic funding rather than direct technical exploitation, traditional technical detection methods are limited. However, defenders should consider:
* Financial Monitoring: Unusual or opaque funding sources for research projects, especially those originating from entities with unclear affiliations or known links to foreign state-sponsored programs.
* Research Project Scrutiny: Review of research topics, data access, and collaboration agreements for projects involving foreign entities, particularly those in sensitive or dual-use technology areas.
* Insider Threat Indicators: Monitoring for unusual data access patterns, attempts to exfiltrate sensitive research data, or suspicious communications by individuals involved in such collaborations.
* Network Traffic Analysis: While not directly specified, any subsequent attempts to exfiltrate data or establish command-and-control channels from compromised academic systems would be detectable via network logs (e.g., DNS queries to suspicious domains, unusual outbound connections).

Mitigations

  1. Enhanced Due Diligence: Academic institutions and researchers should conduct thorough due diligence on all foreign funding sources and collaborating entities, scrutinizing their ultimate beneficial ownership and affiliations.
  2. Increased Awareness: Educate academics and research staff on the risks of state-sponsored intelligence gathering through academic collaboration and the methods employed by foreign intelligence services.
  3. Policy Review: Implement or strengthen policies regarding foreign research collaboration, intellectual property protection, and data handling for sensitive research.
  4. Security Controls for Research Data: Ensure robust access controls, monitoring, and data loss prevention (DLP) solutions are in place for sensitive research data to prevent unauthorized exfiltration.
  5. Reporting Suspicious Activity: Establish clear channels for reporting suspicious funding offers, collaboration requests, or unusual pressure from foreign entities to institutional security and intelligence contacts.

References

  • https://thehackernews.com/2026/10/mi5-says-chinas-mss-funded-research.html

Indicators of Compromise

No public IOCs available at time of writing.

MITRE ATT&CK

  • T1588 — Obtain Capabilities
  • T1591 — Gather Victim Org Information
🤖 AI Attribution
Generated by gemini-2.5-flash ·
1,555 input / 931 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in aptTagged academic, apt, china, espionage, high, intelligenceLeave a comment

JADEPUFFER-Linked Attackers Used Compromised Service Principals to Delete Azure Resources

Posted on September 28, 2026 by Kyle

Overview

The JADEPUFFER threat actor (Microsoft’s Storm-3168) has been observed executing destructive actions within Microsoft Azure environments. This activity, occurring over approximately 18 hours in early June 2026, involved the use of compromised service principals to delete Azure resources. This represents an evolution in the actor’s tradecraft, posing a critical threat to cloud infrastructure integrity and availability.

Technical Analysis

JADEPUFFER attackers gained unauthorized access to Azure environments by compromising service principals. These compromised identities were then leveraged to initiate destructive operations, specifically the deletion of Azure resources. The attack unfolded over an 18-hour window, indicating a sustained effort to cause disruption or data loss. The specific methods of initial service principal compromise were not detailed in the available information, but the subsequent actions focused on resource removal.

Detection

Defenders can identify this activity by monitoring Azure Activity Logs and Azure AD Audit Logs for suspicious actions by service principals.

  • Monitor Azure Activity Logs for operationName related to resource deletion (e.g., Microsoft.Resources/subscriptions/resourceGroups/delete, Microsoft.Compute/virtualMachines/delete, Microsoft.Storage/storageAccounts/delete) where the identity.type is ServicePrincipal.
  • Look for an unusual volume or pattern of resource deletion events originating from a single service principal or a cluster of service principals within a short timeframe.
  • Analyze Azure AD Audit Logs for suspicious modifications to service principal permissions or credentials, or sign-ins from unusual geographic locations or IP addresses for service principals.
  • Hunt for service principals performing actions outside their established baseline or expected scope of work.

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.

Azure Resource Group Deletion by Service Principal

title: Azure Resource Group Deletion by Service Principal
id: 9a2b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d
status: experimental
description: Detects the deletion of an Azure Resource Group by a Service Principal, which could indicate a compromised identity or destructive activity.
logsource:
  product: azure
  service: activitylogs
detection:
  selection:
    operationName: 'Microsoft.Resources/subscriptions/resourceGroups/delete'
    identity.type: 'ServicePrincipal'
  condition: selection
level: critical

Suspicious Azure Resource Deletion by Service Principal

title: Suspicious Azure Resource Deletion by Service Principal
id: 0f1e2d3c-4b5a-6f7e-8d9c-a0b1c2d3e4f5
status: experimental
description: Identifies general resource deletion operations performed by a Service Principal in Azure, potentially indicating a compromised account or malicious activity.
logsource:
  product: azure
  service: activitylogs
detection:
  selection:
    operationName|contains: '/delete'
    identity.type: 'ServicePrincipal'
  condition: selection
level: high

Mitigations

  1. Implement Strong Authentication for Service Principals: Where possible, use managed identities or certificate-based authentication for service principals instead of secrets. If secrets are necessary, enforce strong, regularly rotated secrets.
  2. Apply Least Privilege: Grant service principals only the minimum necessary permissions required for their function. Regularly review and audit assigned roles and permissions.
  3. Monitor Azure Activity and Audit Logs: Implement continuous monitoring for resource deletion events, service principal activity, and changes to permissions. Integrate these logs with a SIEM for alert generation and correlation.
  4. Enable Azure Resource Locks: Apply resource locks (CanNotDelete, ReadOnly) to critical Azure resources to prevent accidental or malicious deletion.
  5. Regularly Audit Service Principals: Periodically review all service principals in your Azure AD tenant, their assigned permissions, and their activity to identify dormant or over-privileged accounts.

References

  • https://thehackernews.com/2026/09/jadepuffer-linked-attackers-used.html

Indicators of Compromise

No public IOCs available at time of writing.

MITRE ATT&CK

  • T1078.004 — Cloud Accounts
  • T1531 — Account Access Removal
🤖 AI Attribution
Generated by gemini-2.5-flash ·
1,543 input / 1,123 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in aptTagged apt, azure, cloud, critical, destructiveLeave a comment

Bitget Crypto Exchange Suffers $387.5M Breach, Linked to North Korean APT

Posted on September 28, 2026 by Kyle

Overview

Bitget, a major cryptocurrency exchange, recently suffered a substantial security breach resulting in the theft of an estimated $387.5 million in various cryptocurrencies. The attack is suspected to have been carried out by North Korean state-sponsored hacking groups. Following the incident, Bitget temporarily halted Bitcoin withdrawals but has since restored these services.

Technical Analysis

Specific technical details regarding the initial compromise vector and post-exploitation activities are not publicly available at the time of writing. The incident is broadly described as a breach of Bitget’s systems, leading to unauthorized access and subsequent exfiltration of digital assets. The attribution to North Korean hackers suggests a sophisticated, well-resourced attack, likely involving advanced persistent threat (APT) methodologies. The scale of the theft indicates a compromise of critical infrastructure related to asset management and withdrawal processes.

Detection

Given the lack of specific technical indicators from the source, general detection strategies for similar high-value breaches would include:
* Monitoring for unusual access patterns to critical financial systems, including access from new IP addresses, geolocations, or user agents.
* Anomaly detection for large or unusual cryptocurrency withdrawal requests, especially those bypassing standard multi-factor authentication or approval workflows.
* Auditing of API key usage for unauthorized or excessive permissions, particularly for actions related to asset transfers.
* Reviewing system and application logs for evidence of unauthorized account creation, privilege escalation, or attempts to disable security controls.
* Network traffic analysis for high-volume data exfiltration or communication with known suspicious IP addresses or domains.

Mitigations

  1. Implement Robust Access Controls: Enforce strict multi-factor authentication (MFA) for all administrative and user accounts, especially those with financial transaction capabilities. Utilize least privilege principles.
  2. Regular Security Audits and Penetration Testing: Conduct frequent, independent security audits and penetration tests focusing on critical infrastructure, hot wallets, and withdrawal systems.
  3. Enhanced Monitoring and Alerting: Deploy advanced threat detection systems (e.g., SIEM, EDR) with real-time alerting for suspicious activities, including unusual login attempts, large transactions, and system configuration changes.
  4. Network Segmentation: Isolate critical systems, such as hot wallets and financial transaction servers, from less secure network segments to limit lateral movement in case of a breach.
  5. Incident Response Plan: Maintain a well-tested incident response plan specifically tailored for financial breaches, including clear communication protocols and asset recovery procedures.

References

  • https://www.bleepingcomputer.com/news/security/bitget-resumes-bitcoin-withdrawals-after-3875-million-crypto-heist/

Indicators of Compromise

No public IOCs available at time of writing.

MITRE ATT&CK

  • T1078 — Valid Accounts
  • T1003 — OS Credential Dumping
  • T1041 — Exfiltration Over C2 Channel
  • T1567 — Exfiltration Over Web Service
🤖 AI Attribution
Generated by gemini-2.5-flash ·
1,493 input / 816 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in aptTagged apt, breach, critical, cryptocurrency, financial theft, north koreaLeave a comment
Proudly powered by WordPress | Theme: micro, developed by DevriX.