https://feed.craftedsignal.io/tags/initial_access/Trending threats, MITRE ATT&CK coverage, and detection metadata — refreshed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioSun, 15 Mar 2026 15:31:12 +0000https://feed.craftedsignal.io/briefs/2024-01-03-fake-claude-ads/Sun, 15 Mar 2026 15:31:12 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-03-fake-claude-ads/Malware is distributed via malicious advertisements on Google impersonating 'Claude Code', targeting both Windows and macOS operating systems with the goal of infecting users.A malware campaign is underway, leveraging deceptive advertisements on Google that masquerade as legitimate ‘Claude Code’ software. The attackers are using these ads to direct unsuspecting users to malicious websites hosting malware payloads for both Windows and macOS systems. While specific details on the malware are limited, the campaign’s reliance on search engine advertisement poisoning indicates a broad targeting strategy aimed at users actively seeking ‘Claude Code’ related software or tools. This campaign highlights the increasing sophistication of threat actors in using search engine optimization (SEO) poisoning techniques to distribute malware. Defenders should be aware of the potential for users to be directed to malicious sites through search results.

Attack Chain

1. The attacker creates malicious advertisements on Google that mimic legitimate ‘Claude Code’ software or related tools.
2. Users searching for ‘Claude Code’ or related terms encounter the malicious advertisements in their search results.
3. Unsuspecting users click on the malicious advertisement, believing it to be a legitimate source for ‘Claude Code’.
4. The advertisement redirects the user to a malicious website controlled by the attacker.
5. The malicious website hosts malware payloads tailored for both Windows and macOS operating systems.
6. Upon visiting the site, the user is tricked into downloading and executing the malware, potentially through social engineering or drive-by download techniques.
7. The malware executes on the victim’s system, establishing persistence and potentially disabling security controls.
8. The malware performs its intended malicious activities, such as data theft, credential harvesting, or further malware deployment.

Impact

The impact of this campaign could be widespread, affecting both individual users and organizations who rely on ‘Claude Code’. Successful infection can lead to data theft, financial loss, and reputational damage. Given the use of Google Ads, the number of potential victims is substantial. The cross-platform nature of the attack further amplifies the risk, as it targets a broader range of users regardless of their operating system.

Recommendation

• Implement browser security extensions and ad blockers to reduce the likelihood of users clicking on malicious advertisements.
• Educate users about the risks of clicking on advertisements in search results and encourage them to verify the legitimacy of websites before downloading software.
• Monitor network traffic for connections to newly registered domains or known malicious IP addresses associated with malware distribution.
• Deploy endpoint detection and response (EDR) solutions to detect and prevent malware execution on both Windows and macOS systems.
• Enable and review web proxy logs for user visits to suspicious domains.
• Configure intrusion detection systems (IDS) to identify and block malicious traffic originating from advertisement networks.

]]>highadvisorymalwaregoogle_adsinitial_accesswindowsmacoshttps://feed.craftedsignal.io/briefs/2024-01-wmi-script-execution/Wed, 03 Jan 2024 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-wmi-script-execution/The rule identifies the use of Windows script interpreters (cscript.exe or wscript.exe) executing a process via Windows Management Instrumentation (WMI), which may indicate malicious activity, especially when initiated by non-system accounts.This detection identifies the use of Windows script interpreters (cscript.exe or wscript.exe) to execute processes via Windows Management Instrumentation (WMI). Adversaries exploit WMI to execute scripts or processes stealthily, often using script interpreters. The rule monitors for these interpreters executing processes via WMI, specifically when initiated by non-system accounts, indicating potential malicious intent. The detection focuses on identifying scenarios where wmiutils.dll is loaded by wscript.exe or cscript.exe, followed by wmiprvse.exe spawning a new process. This is often associated with malicious initial access or execution techniques.

Attack Chain

1. An attacker gains initial access via phishing (T1566) or other means.
2. The attacker leverages a script, such as VBScript or JavaScript (T1059.005, T1059.007), to execute commands using WMI.
3. The script interpreter (cscript.exe or wscript.exe) loads wmiutils.dll to interact with WMI.
4. The WMI Provider Host process (wmiprvse.exe) is invoked as a parent process, triggered by the script execution.
5. wmiprvse.exe executes a secondary process, such as powershell.exe, cmd.exe, or other executables, often from unusual locations like C:\\Users\\ or C:\\ProgramData\\.
6. The executed process performs malicious actions, such as downloading additional payloads or establishing persistence.
7. The attacker attempts to maintain persistence by creating scheduled tasks or modifying registry keys.
8. The ultimate objective is often lateral movement, data exfiltration, or deploying ransomware.

Impact

Successful exploitation allows attackers to execute arbitrary code, bypass security controls, and establish persistence on the compromised system. The use of WMI enables stealthy execution, making detection challenging. The impact can range from data theft and system compromise to full network takeover. In some cases, threat actors may deploy ransomware, leading to significant financial losses and operational disruption.

Recommendation

• Enable Sysmon Event ID 1 (Process Creation) and Event ID 7 (Image Loaded) logging to provide the necessary data for the provided Sigma rules.
• Deploy the provided Sigma rule “WMI Scripting Process Creation” to detect suspicious process creation events originating from wmiprvse.exe.
• Investigate any alerts generated by the provided Sigma rule “WMI Scripting Process Creation” with a focus on processes spawned by wmiprvse.exe from unusual locations or with suspicious command-line arguments.
• Implement endpoint protection policies to block or alert on the execution of high-risk processes when initiated by non-system accounts as mentioned in the overview.
• Regularly review and update endpoint protection policies to block or alert on the execution of high-risk processes like those listed in the detection query, especially when initiated by non-system accounts.

]]>mediumadvisorywindowswmiscript_executioninitial_accessexecution