Trump Mobile Exposes 27,000 Customer Records via Insecure API

Security researcher Louis found that Trump Mobile's HTTP POST API returned 27,000 customer records without any authorization check during the T1 phone launch.
Table of Contents
    Add a header to begin generating the table of contents

    A security researcher using the pseudonym “Louis” discovered that Trump Mobile — the brand behind the Trump T1 smartphone — had left HTTP POST API endpoints on its website configured to return customer records to any caller without authentication, exposing approximately 27,000 customers’ personal data during the device’s launch period.

    Trump Mobile’s API Endpoints Returned Customer Records Without Authorization

    The exposure required no SQL injection, credential bypassing, or complex attack technique. Louis found that Trump Mobile’s backend API endpoints returned full customer records in response to straightforward POST requests, with no check to verify that the requesting party had authorization to access the data. Louis accessed approximately 5,000 records in one hour before stopping.

    Exposed data for each record included first and last names, primary and secondary physical addresses, email addresses, phone numbers, customer and account numbers, enrollment IDs, and order placement method. The vulnerability appears to have been present throughout the pre-order and launch period for the T1 device, meaning an unknown number of third parties could have accessed the same data during the exposure window.

    Disclosure Through YouTube After No Response from Trump Mobile

    Louis attempted to reach Trump Mobile through official channels before publication but received no response. Louis then shared the findings with YouTube content creators Stephen Findeisen and Charles White Jr., whose videos covering the discovery generated millions of views. That public disclosure path — through social media rather than a coordinated vendor response — was taken after the standard private disclosure route failed to produce acknowledgment from the company.

    Trump Mobile confirmed the issue was fixed following the public disclosure. The company did not issue an official statement, did not publicly acknowledge the exposure, and had not announced customer notification as of the time of the initial reporting.

    No Customer Notification and Potential Regulatory Exposure

    The absence of customer notification raises regulatory considerations. Depending on the state of residence of affected customers, various data breach notification laws set timelines for notifying individuals when their personally identifiable information is exposed. Trump Mobile’s 27,000 affected customers include people whose names, physical addresses, and contact information were accessible without any authorization barrier during the launch period.

    API Access Control Failures at Consumer Electronics Launches

    The Trump Mobile case is an instance of a pattern documented repeatedly across consumer electronics product launches: backend API infrastructure intended for internal use or controlled access is exposed to the public internet without adequate authentication or authorization controls. Pre-launch and launch-period timing is when newly built backend systems are least likely to have undergone full security review. The result is that customer data entered during pre-orders and initial purchases is at highest risk precisely when customer volume is growing fastest.

    Trump Mobile’s confirmation that the issue was fixed, combined with the company’s silence on customer notification and the scope of the exposure, leaves affected customers without official guidance on whether their data was accessed by any party beyond Louis during the period the endpoints were open.

    Related Posts