Skip to content

Security Sense

AI Threat Intelligence

  • About
  • Blog
  • Privacy Policy

Category: phishing

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

Lucifer DaaS: Scaling Crypto Wallet Theft via Malicious Transaction Approvals

Posted on May 21, 2026 - September 27, 2026 by Kyle

Overview

Lucifer DaaS is a Drainer-as-a-Service platform enabling threat actors to conduct widespread cryptocurrency wallet theft. It operates by deceiving users into authorizing malicious transactions that transfer their digital assets to attacker-controlled wallets. This method bypasses direct wallet hacking, relying instead on social engineering and phishing campaigns to exploit user trust and lack of vigilance.

Technical Analysis

Lucifer DaaS provides a scalable infrastructure for threat actors to deploy crypto drainers. The core mechanism involves presenting users with deceptive prompts, often through phishing websites or compromised legitimate platforms, that request approval for what appears to be a benign blockchain transaction. In reality, these transactions are crafted to transfer all or specific types of tokens from the victim’s wallet to an attacker’s address. The platform automates the generation of these malicious transaction requests and handles the subsequent transfer of stolen funds. Attack vectors commonly include:
* Phishing links distributed via email, social media, or messaging apps.
* Compromised legitimate websites or dApps injecting malicious scripts.
* Pop-ups or redirects that mimic legitimate wallet connection requests.
Victims are typically prompted to “connect wallet” or “approve transaction” for seemingly innocuous actions, but the underlying transaction details, if scrutinized, reveal a transfer of assets.

Detection

Detecting crypto drainer attacks primarily relies on user vigilance and careful scrutiny of blockchain transaction details before approval.
* Transaction Detail Scrutiny: Always meticulously review the details of any transaction request in your wallet interface. Look for unexpected token transfers, unusually high gas fees, or requests to approve unlimited spending for unknown contracts.
* URL Verification: Verify the URL of any website requesting wallet connection or transaction approval. Phishing sites often use subtle misspellings or subdomains.
* Unexpected Pop-ups: Be suspicious of unsolicited pop-up windows or redirects asking for wallet interaction.
* Revoke Approvals: Regularly check and revoke token approvals for dApps you no longer use or trust, especially those with “unlimited” spending allowances. Tools like Etherscan’s Token Approvals page can assist.

Mitigations

  1. Educate Users: Train users to critically examine all transaction requests, verify URLs, and understand the implications of approving blockchain transactions.
  2. Use Hardware Wallets: Store significant cryptocurrency holdings on hardware wallets (e.g., Ledger, Trezor), which require physical confirmation for transactions, adding an extra layer of security.
  3. Limit Token Approvals: Grant token approvals only when necessary and for specific amounts. Regularly review and revoke unnecessary or unlimited approvals.
  4. Implement Browser Security Extensions: Utilize browser extensions that provide Web3 security warnings (e.g., MetaMask’s built-in warnings, WalletGuard, Revoke.cash) to identify suspicious transactions or phishing sites.
  5. Network-Level Filtering: Implement DNS filtering and web proxies to block known phishing domains, though attackers frequently rotate infrastructure.

References

  • https://www.bleepingcomputer.com/news/security/inside-a-crypto-drainer-how-to-spot-it-before-it-empties-your-wallet/

Indicators of Compromise

No public IOCs available at time of writing.

MITRE ATT&CK

  • T1566.002 — Spearphishing Link
🤖 AI Attribution
Generated by gemini-2.5-flash ·
1,276 input / 889 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in phishingTagged highLeave a comment
Proudly powered by WordPress | Theme: micro, developed by DevriX.