The Federal Communications Commission proposed and then ordered a $4.5 million penalty against U.S. voice service provider Voxbeam Telecommunications for allegedly accepting and routing suspicious robocall traffic from Axfone, a Czech Republic-based provider that was not listed in the FCC’s Robocall Mitigation Database. The agency said Voxbeam was barred from carrying Axfone’s traffic over U.S. networks but still transmitted calls between March 31 and April 3, 2025, enabling tens of thousands of scam calls to reach Americans.
According to the FCC, the robocalls spoofed fraud prevention and customer service numbers tied to Bank of America, Chase, and other financial institutions, using non-compliant and long-dormant accounts to impersonate banks and target customers. The investigation began after a bank reported the scam activity, and FCC Chairman Brendan Carr said gateway providers are responsible for blocking illegal foreign call traffic rather than serving as pass-throughs for it.

See the reporting duties and controls this puts on the clock.
3 events from the most recent confirmed update back to the earliest known activity.
The FCC announced a proposed $4.5 million fine against Voxbeam Telecommunications for allegedly routing suspicious foreign robocall traffic from unauthorized provider Axfone into U.S. networks. The penalty was not yet final at the time of the announcement because Voxbeam was given an opportunity to respond.
After a bank reported that its customers had received the scam calls, the FCC opened an investigation into the suspicious traffic routed by Voxbeam. The probe focused on robocalls impersonating financial institutions and fraud departments.
Between March 31 and April 3, 2025, Voxbeam Telecommunications allegedly accepted and routed call traffic from Czechia-based Axfone, which was not listed in the FCC's Robocall Mitigation Database. The traffic enabled tens of thousands of financial impersonation robocalls spoofing numbers associated with Bank of America, Chase, and other institutions.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See what this changes for your reporting obligations and which controls it puts on the clock.
2 references tracked. Mallory keeps watching after this page renders.
scworld.com
Open sourcetherecord.media
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.