Thingiverse Exposed Subscriber Data in Breach Affecting Hundreds of Thousands of Users
Thingiverse, the 3D-model sharing platform, suffered a data exposure that placed user information in the hands of hackers, with one report describing a 36GB cache of data taken from the service. Reporting indicates the leak involved subscriber records and other user-related information from the MakerBot-owned platform, raising concerns that exposed account data could be used for credential abuse, phishing, or broader identity-focused attacks.
Subsequent coverage said the incident affected 228,000 subscribers, underscoring the scale of the breach and the sensitivity of the compromised dataset. The exposure drew attention to the security risks facing online maker communities and subscription platforms, particularly where large stores of user account information are retained and insufficiently protected against unauthorized access or exfiltration.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
2 events from the most recent confirmed update back to the earliest known activity.
Report says Thingiverse leak affects 228,000 subscribers
DataBreachesToday reported that a Thingiverse data leak affected 228,000 subscribers. This appears to describe the same broader incident with an updated affected-user count, but the reference block does not provide an explicit date for when that impact was determined.
Thingiverse data leak exposes 36GB of user data
Tom's Hardware reported a Thingiverse data leak in which hackers obtained 36GB of user data. The reference does not provide a specific event date beyond the report itself.
Sources
2 references tracked. Mallory keeps watching after this page renders.
See the full picture, correlated to your attack surface.
Map 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.


