Exploitation — CraftedSignal Threat Feed

Democratization of Business Email Compromise (BEC) Attacks

hello@craftedsignal.io — Fri, 03 Apr 2026 12:00:00 +0000

Business Email Compromise (BEC) attacks have historically targeted large organizations with significant payouts justifying the required time investment. However, recent trends indicate a democratization of BEC, with smaller organizations becoming increasingly targeted. This shift is largely driven by the adoption of AI, enabling attackers to rapidly reconnoiter and tailor content for smaller organizations at scale. Attackers are now targeting smaller community associations, charities, and businesses, recognizing that scamming smaller sums from many victims can be as profitable as scamming large sums from a few. These organizations are often less aware of the threat and thus more vulnerable.

Attack Chain

Reconnaissance: Attackers use AI-powered tools to gather information about target organizations and key personnel (e.g., community associations, small businesses).
Impersonation: Attackers craft emails impersonating trusted individuals within the organization (e.g., the chair of the association).
Request Initiation: The attacker sends an email requesting a fund transfer to an account they control, relying on social engineering to trick someone with payment authority.
Evasion: The initial email is often sent from a plausible email address or a compromised genuine account.
Account Compromise: Exploit React2Shell vulnerability (CVE-2025-55182) in Next.js applications to gain access to sensitive data, including cloud tokens, database credentials, and SSH keys, which are used for lateral movement.
Data Exfiltration: Sensitive data, including cloud tokens, database credentials, and SSH keys, is exfiltrated using custom framework called “NEXUS Listener”.
Obfuscation: Once received, funds typically pass through money mules or compromised personal accounts before being rapidly shuffled through multiple transfers, obscuring the trail.
Financial Gain: The attacker successfully initiates the fund transfer and receives the money.

Impact

The democratization of BEC attacks expands the threat landscape to include vulnerable small organizations. While the individual sums may be smaller, the cumulative impact of successful attacks can be significant. If successful, organizations suffer financial losses, potential data breaches through stolen credentials (related to CVE-2025-55182), and reputational damage. The European Commission investigated a breach after an Amazon cloud account hack, highlighting the potential for data leaks.

Recommendation

Educate employees, especially those with payment authority, about the signs of BEC scams, emphasizing unexpected requests for payment and the importance of verifying requests through separate channels (reference: Overview section).
Implement and enforce strict procurement rules that prevent any last-minute urgent payments (reference: Overview section).
Patch Next.js applications against React2Shell vulnerability (CVE-2025-55182) immediately and rotate potentially compromised credentials including API keys and SSH keys (reference: “The one big thing” section).
Deploy the following Sigma rule to detect suspicious process creation activity (reference: rules section).
Monitor for the presence of the malware files identified in the report using the provided SHA256 hashes (reference: IOCs section).

Potential JAVA/JNDI Exploitation Attempt

hello@craftedsignal.io — Wed, 01 Apr 2026 14:24:53 +0000

This detection rule identifies potential exploitation attempts targeting Java Naming and Directory Interface (JNDI) vulnerabilities. These vulnerabilities, exemplified by CVE-2021-45046, allow attackers to perform remote code execution by injecting malicious payloads through directory services like LDAP. The rule focuses on detecting suspicious outbound network connections from Java processes to standard ports associated with LDAP (389, 1389), RMI (1099), and DNS (53, 5353), followed by the execution of suspicious child processes indicative of command execution such as shell interpreters (sh, bash, zsh) or scripting languages (python, perl). The rule aims to identify exploitation attempts similar to those seen with Log4Shell and related vulnerabilities, which have been actively exploited since late 2021. It covers Linux and macOS environments and provides a mechanism to detect ongoing exploitation.

Attack Chain

A vulnerable Java application receives malicious input containing a JNDI lookup string.
The Java application attempts to resolve the JNDI name, initiating an outbound network connection to an LDAP, RMI, or DNS server on ports 389, 1389, 1099, 53, or 5353.
The malicious LDAP/RMI/DNS server, controlled by the attacker, responds with a payload referencing a malicious Java class or remote code.
The Java application loads and executes the malicious code.
As a result of the executed code, a shell interpreter (sh, bash, zsh, etc.) or scripting language (python, perl, ruby, php, wget) is spawned as a child process of the Java application.
The spawned shell/script executes attacker-controlled commands for reconnaissance, privilege escalation, or lateral movement.
The attacker gains a foothold on the system.
The attacker performs actions such as data exfiltration or deploying malware.

Impact

Successful exploitation of JNDI vulnerabilities can lead to remote code execution, allowing attackers to gain complete control over affected systems. This can result in data breaches, system compromise, and further propagation of attacks within the network. The impact can range from service disruption to complete system takeover. Public exploits for vulnerabilities such as Log4Shell have been widely available, leading to widespread scanning and exploitation attempts across various industries.

Recommendation

Deploy the Sigma rule “Potential JAVA/JNDI Exploitation Attempt” to your SIEM to detect suspicious Java processes initiating network connections to LDAP, RMI, or DNS ports followed by suspicious child processes.
Enable process creation and network connection logging on Linux and macOS endpoints to provide the necessary data for the Sigma rules to function correctly.
Review and whitelist legitimate Java applications that may trigger false positives due to legitimate network connections (see the “False positive analysis” section in the original rule’s note field).
Implement network segmentation to limit the impact of successful exploitation by restricting lateral movement.
Patch vulnerable Java applications and libraries, such as Log4j, to prevent exploitation of known vulnerabilities like CVE-2021-45046.

Ongoing Exploitation of Cisco SD-WAN Systems

hello@craftedsignal.io — Wed, 25 Feb 2026 12:00:00 +0000

CISA and its partners have observed malicious cyber actors targeting and compromising Cisco SD-WAN systems across various organizations globally. The attackers are leveraging CVE-2026-20127, an authentication bypass vulnerability, for initial access. Following successful exploitation of CVE-2026-20127, the attackers escalate privileges and establish long-term persistence within the compromised SD-WAN systems using CVE-2022-20775. In response to this active exploitation, CISA issued Emergency…