What was exposed
SpeedX exposure
- 1
Storage exposure
By March 13, 2026SpeedX confirmed that a storage configuration allowed limited container metadata responses. Cybernews identified the storage service as Microsoft Azure.
- 2
Disputed file access
March 2026Cybernews said it could see delivery and driver records. SpeedX said access to objects required specific paths. Neither account establishes a bulk download.
- 3
Found and closed
April–May 2026Cybernews dated discovery to March 13, initial disclosure to April 2 and closure to May 11. SpeedX confirmed that the configuration had been corrected.
Impact
Cybernews reported more than 840 million files, including parcel photos, shipping labels and driver records. The count describes files. SpeedX disputed how broadly they were accessible and reported no evidence of unauthorized access to sensitive customer data or exfiltration.
Could this have been prevented?
Restrict anonymous reads on the ordinary Blob endpoint
If every container in the storage account can require authorized requests, turning off anonymous Blob access blocks ordinary unauthenticated reads, even for someone who knows a file’s path. The reports do not establish the exact access setting or whether other ways of authorizing a request were in use.
Incident control assessments
- 0
- Prevented
- 2
- Contained
- 1
- Not covered
How it could have been prevented
The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.
SpeedX exposure
1 · Storage exposure
1 Contained2 · Disputed file access
1 Contained3 · Found and closed
1 Not coveredKey facts
- Cybernews discovered the exposed storage on March 13 and dated its initial disclosure to April 2.
- Researchers reported more than 840 million files, including about 618 million parcel photos. Those counts do not measure distinct people or deliveries.
- SpeedX confirmed limited metadata responses. It disputed the researchers’ account of file access and said specific object paths were required.
- Cybernews dated closure to May 11. SpeedX reported no evidence of exfiltration or unauthorized access to sensitive customer data.
Sources
Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.
- 1.Delivery mega leak: 840M+ files exposed as US delivery company leaks massive file storageCybernews · undated · ResearchFirsthand observations, discovery and disclosure timeline, file counts and the operator’s disagreement about the access required.
- 2.SpeedX data leak exposes more than 840 million customer and driver recordsteiss · May 28, 2026 · NewsContemporaneous May 28 public reporting on researcher findings.
- 3.Remediate anonymous read access to blob dataMicrosoft · undated · Vendor reportAccount-wide denial overrides container anonymous settings for ordinary Blob service access.
- 4.Static website hosting in Azure StorageMicrosoft · undated · Vendor reportThe separate static website endpoint remains anonymously accessible when enabled.
- 5.Azure Storage firewall rulesMicrosoft · undated · Vendor reportPublic network endpoint restrictions, approved source networks and service exceptions.
The estate in the replay is illustrative and drawn at the level of the exposure; the owner's real environment is not public. Verdicts describe what a control does when it is in place before the data is exposed. They are not an assessment of the owner's security program.