Image: any.run · rights & removal
Executive Summary
Facts Only
* HelloFriends used phishing emails impersonating FMCSA, using sender addresses at dotcompanyinfo[.]com.
* Phishing links led to fraudulent SAFER or Motus portals.
* Victims were asked to provide SSNs, EINs, date of birth, and contact details, along with a supposed $300 administrative fee.
* HelloFriends infrastructure used Next.js applications on Vercel to submit data via endpoints like /api/send-telegram.
* NodeRemote distributed malware through fake broker onboarding pages and documents.
* Infection chains deployed PowerShell or VBS scripts to retrieve components from attacker infrastructure, including Cloudflare Workers endpoints.
* NodeRemote established persistence using scheduled tasks named NodeRemote{GUID} or NodeRemoteWebServer-.
* The malware communicated relay information via a main.js backdoor retrieving data from BNB Smart Chain contracts, DNS-over-HTTPS, and GitHub gists, cached in lastknownrelays.json.
* Fake Freight Portals used malicious WebDAV shortcuts to deliver terms\and\conditions.pdf.lnk, which executed terms\and\conditions.exe.
* The installation resulted in the deployment of a MeshCentral agent and CastleRAT, which attempted to retrieve BitLocker recovery passwords.
* IOCs include dotcompanyinfo[.]com, /api/send-telegram, NodeRemote, and various C2 endpoints like 87.120.104[.]213:1010.
Full Take
The existence of these campaigns demonstrates a systemic risk rooted in the trust inherent within logistics workflows. The attackers are not merely looking for credentials; they are exploiting the high volume and procedural regularity of document exchange—carrier verification, freight booking, and broker communication—to embed malware and establish deep persistence. The key pattern is the exploitation of legitimate business tools (SAFERS, Motus, DAT portals, MeshCentral) as vectors for malicious payload delivery. This challenges traditional perimeter-focused defenses, necessitating a shift toward behavioral monitoring within enterprise systems.
The attack progression from simple credential theft (HelloFriends) to persistent remote control (NodeRemote and Fake Freight Portals) reveals an escalation strategy. Attackers leverage the initial breach to achieve deeper access by installing legitimate management tools like MeshCentral, masking malicious activity within authorized processes. Furthermore, the use of dynamic C2 infrastructure rotation, discovered through blockchain and DNS methods in NodeRemote, indicates a sophisticated operational security designed to evade static IOC blocking.
The most critical implication for SOC/MSSP teams is that surface-level indicators are insufficient. The observable behavior shifts from file reputation to process interaction (e.g., WebDAV execution), configuration changes (e.g., BitLocker access), and communication patterns (e.g., internal telemetry endpoints). The capability of tools like Interactive Sandbox to reveal these granular execution chains, combined with context-aware threat intelligence, bridges the gap between raw alerts and actionable defense. The challenge lies in developing detection logic that recognizes legitimate software acting maliciously within a known logistical context, rather than focusing solely on unknown files.
Bridge Questions: How can security architecture be redesigned to inherently trust operational workflow integrity, rather than relying solely on endpoint signatures? What organizational changes are required to effectively manage the high-volume data exchange necessary for logistics operations while maintaining security posture? If threat intelligence is being delivered via TI Feeds, how should organizations prioritize integrating behavioral context over raw indicator volume in their detection pipelines?
From the original · Any.run Blog
American trucking and logistics companies rely on digital platforms to verify carriers, onboard brokers, exchange documents, and coordinate freight. Cybercriminals increasingly exploit these routine business processes.Read the full story at any.run
Sentinel unavailable
The automated check of the source article's wording did not complete, so no result is shown.
This looks only at the wording of the original source article, not at this page's AI-written sections. A small local AI model made this estimate. It has not been checked against known human and machine texts, so treat it as provisional. It cannot show who wrote an article.
