A highly organized, financially motivated threat group tracked as Diesel Vortex has been conducting a large-scale phishing campaign against the freight and logistics sectors in the United States and Europe since at least September 2025. The operation successfully stole 1,649 unique credentials by targeting users of critical industry platforms like DAT Truckstop, Penske Logistics, and Electronic Funds Source (EFS). The attackers leveraged a sophisticated Phishing-as-a-Service (PaaS) kit, employing advanced tactics such as typosquatted domains, voice phishing (vishing) to bypass MFA, and a 'Dual-Domain Deception' technique to evade detection. The discovery of an exposed .git repository provided critical intelligence, leading to the takedown of the group's infrastructure in a coordinated effort involving Cloudflare and Google's Threat Intelligence Group.
The Diesel Vortex campaign represents a significant threat to the supply chain and transportation industries. The group's primary motive is financial gain, achieved by compromising accounts on freight exchanges and fuel card systems. This access is then used to commit fraud, such as 'double-brokering'—where stolen carrier identities are used to take control of legitimate shipments, which are then diverted and stolen. The investigation uncovered 35 confirmed instances of EFS check fraud stemming from the compromised credentials.
The operation was notable for its professionalism and technical sophistication. It included a full-service PaaS model with a call center and email support, 52 typosquatted domains that were near-perfect clones of legitimate portals, and the use of Telegram bots for real-time communication and MFA code theft. The actors are assessed to be Armenian-speaking with links to Russian infrastructure, indicating a transnational criminal enterprise.
The campaign's success hinged on a combination of social engineering and technical evasion techniques designed to defeat both human and automated defenses.
T1586.002 - Email Accounts): The group targeted over 75,000 email contacts, likely gathered from industry lists or previous breaches.T1566.002 - Spearphishing Link): Victims received spearphishing emails containing links to one of 52 typosquatted domains.T1204.001 - Malicious Link): The user clicks the link, leading them to a convincing phishing page.T1608.005 - Link Target Manipulation): The attackers used a 'Dual-Domain Deception' technique. A seemingly clean domain loaded the actual phishing kit from a separate, malicious domain within a hidden iframe. This helps bypass some browser-based phishing detection that only analyzes the primary URL.T1598.003 - Spearphishing Voice): If a user entered credentials, the system would prompt for an MFA code. The PaaS kit likely triggered an alert to the attackers, who would then engage in vishing (a phone call) or use Telegram to socially engineer the victim into providing the real-time MFA code.T1078 - Valid Accounts): With credentials and the MFA code, the attackers gained full access to the victim's account on the targeted platform.The exposure of the group's
.gitrepository was a critical operational security failure. It allowed researchers to reconstruct the phishing kit's source code and access a 36.6MB SQL database, providing a comprehensive view of the campaign's scale and victims.
The Diesel Vortex campaign has had a direct and severe financial impact on the freight and logistics industry.
Detecting this campaign requires a multi-layered approach focusing on email security, web traffic analysis, and user awareness.
D3-DNSDL: DNS Denylisting is essential.Defending against sophisticated phishing requires technical controls and continuous user education.
M1032 - Multi-factor Authentication): While Diesel Vortex bypassed some MFA, organizations should prioritize the adoption of phishing-resistant MFA methods like FIDO2/WebAuthn, which are not susceptible to real-time credential and session relay attacks.M1017 - User Training): Conduct regular, realistic phishing simulation and training. Specifically educate users on vishing tactics and the danger of sharing MFA codes over the phone or chat, even if the person seems legitimate.M1021 - Restrict Web-Based Content): Implement strict web filtering to block access to uncategorized or newly registered domains. This can prevent users from ever reaching the phishing page.Train users to identify phishing and vishing attempts, and to never share MFA codes. This is the primary defense against the social engineering aspect of the campaign.
Implement phishing-resistant MFA, such as FIDO2 hardware keys, to prevent credential theft even if the user is tricked.
Mapped D3FEND Techniques:
To combat the 'Diesel Vortex' campaign's use of 52 typosquatted domains, organizations in the logistics sector must deploy robust URL Analysis at the email gateway and web proxy. This technique involves more than just checking a URL against a denylist. Advanced systems should analyze URLs in real-time for suspicious characteristics, such as the use of Punycode, excessive subdomains, or slight misspellings of trusted brands like 'Truckstop' or 'Penske'. The 'Dual-Domain Deception' tactic, which loads a malicious iframe, can be specifically countered by solutions that dynamically analyze rendered web page content, not just the initial URL. By inspecting the final destination of all links and the content they load, security tools can identify the malicious payload and block the connection, even if the initial link appears benign. This is a critical defense layer to prevent employees from ever being exposed to the credential harvesting form.
The 'Diesel Vortex' campaign's success in bypassing MFA through vishing underscores the need for stronger authentication methods. While any MFA is better than none, organizations should strategically move towards phishing-resistant authenticators. This means migrating away from SMS and one-time password (OTP) apps where possible, as these are vulnerable to social engineering. The gold standard is to implement FIDO2/WebAuthn-based authentication, using hardware security keys (e.g., YubiKey) or platform authenticators (e.g., Windows Hello, Face ID). These methods create a cryptographic bond between the user, the device, and the specific service being accessed, making it impossible for an attacker to capture a code and reuse it on their own machine. For the targeted logistics platforms, mandating FIDO2 for all users would have completely neutralized the attackers' ability to take over accounts, even if a user fell for the initial phishing lure.
A proactive defense against campaigns like 'Diesel Vortex' is the aggressive use of DNS Denylisting. Security teams should subscribe to high-quality threat intelligence feeds that provide lists of known phishing and malicious domains, and integrate these into their DNS resolvers (e.g., Cisco Umbrella, Quad9) or firewalls. Furthermore, organizations can create their own proactive denylists by monitoring Certificate Transparency logs for newly registered domains that mimic their brand or key partners ('typosquatting'). For example, a rule could automatically flag any new domain containing 'truckst0p' or 'pensk-logistics'. By blocking DNS resolution for these domains at the network edge, employees are prevented from ever connecting to the phishing sites, effectively cutting off the attack at its earliest stage. This automated defense scales well and reduces the reliance on users to spot sophisticated fake websites.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats