3D printing site Thingiverse suffers breach of 228,000 email addresses amid sluggish disclosure
(2021/10/14)
- Reference: 1634227384
- News link: https://www.theregister.co.uk/2021/10/14/thingiverse_data_breach_228k_email_addresses/
- Source link:
Thingiverse, a site that hosts free-to-use 3D printer designs, has suffered a data breach – and at least 228,000 unlucky users' email addresses have been circulating on black-hat crime forums.
News of the breach came from Have I Been Pwned (HIBP), whose maintainer Troy Hunt uploaded the 228,000 breached email addresses to the site after being tipped off to their circulation on the forums.
Hunt claimed on Twitter that in excess of two million addresses were in the breach. He qualified that by saying the majority were email addresses that appeared to be generated by Thingiverse itself, judging from their format: webdev+$username@makerbot[.]com.
[1]
HIBP's maintainer also claimed that some of the data included poorly encrypted passwords: one he highlighted was an unsalted SHA-1 hash which resolved to the password "test123".
[2]
[3]
Thingiverse is owned by 3D printing firm Makerbot, last seen in these pages back in 2015 when it was [4]making staff redundant after failing to meet "ambitious goals".
Makerbot was less than responsive to his private overtures, Hunt claimed on Twitter, eventually forcing him to go public in the hope of convincing someone that the source of the breach ought to be closed off.
Meanwhile, I get a DM from someone who alleges [5]@thingiverse "have a backup file exposed". I don't ask details, so I never verified the claim (but I have strong reasons to believe this person), and during this process they later told me that "the bucket is set to private now". — Troy Hunt (@troyhunt) [6]October 14, 2021
We have asked Brooklyn-based Makerbot for comment on Hunt's observations, which stretch for a number of tweets that can be read in full by clicking the one above. The company does not appear to have publicly acknowledged the breach so far.
[7]NHS-backed org reacted to GitHub leak disclosure with legal threats and police call, complains IT pro
[8]Why MakerBot failed – but 3D printing is far from dead
[9]Maker–NOT: 3D printer upstart Makerbot jams, cuts extra 20% of staff
[10]McDonald's email blunder broadcasts database creds to comedy competition winners
[11]Hole blasted in Guntrader: UK firearms sales website's CRM database breached, 111,000 users' info spilled online
Breach disclosure is sometimes a difficult topic. Earlier this week El Reg reported on the case of a company that [12]asked a researcher making a responsible disclosure to not contact them again . In that case the researcher had been trying to warn the firm that a Laravel debug page was exposing the username and password for a database – quite concerning given that Schools Marketing Company Ltd claimed to hold the details of a million teachers and school admin personnel.
Earlier this year a fraught disclosure attempt by a techie who formerly worked with an open source org [13]resulted in the police being called and a High Court lawsuit being threatened , all because of misunderstandings.
[14]
Sometimes, however, some companies just don't want to hear bad news – which makes it all the more important to get through to them. ®
Get our [15]Tech Resources
[1] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2YWioljsk@dwYkkfMm4VnAAAAAEQ&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YWioljsk@dwYkkfMm4VnAAAAAEQ&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YWioljsk@dwYkkfMm4VnAAAAAEQ&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[4] https://www.theregister.com/2015/10/08/more_makerbot_layoffs/
[5] https://twitter.com/thingiverse?ref_src=twsrc%5Etfw
[6] https://twitter.com/troyhunt/status/1448593640339623938?ref_src=twsrc%5Etfw
[7] https://www.theregister.com/2021/05/14/apperta_rob_dyke_disclosure_brouhaha/
[8] https://www.theregister.com/2015/05/06/why_makerbot_failed_and_3d_printing_is_far_from_dead/
[9] https://www.theregister.com/2015/10/08/more_makerbot_layoffs/
[10] https://www.theregister.com/2021/09/09/mcdonalds_database_credentials_blunder/
[11] https://www.theregister.com/2021/07/23/guntrader_hacked_111k_users_sql_database/
[12] https://www.theregister.com/2021/10/12/schools_marketing_company_database_credentials_exposed/
[13] https://www.theregister.com/2021/05/14/apperta_rob_dyke_disclosure_brouhaha/
[14] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YWioljsk@dwYkkfMm4VnAAAAAEQ&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[15] https://whitepapers.theregister.com/
News of the breach came from Have I Been Pwned (HIBP), whose maintainer Troy Hunt uploaded the 228,000 breached email addresses to the site after being tipped off to their circulation on the forums.
Hunt claimed on Twitter that in excess of two million addresses were in the breach. He qualified that by saying the majority were email addresses that appeared to be generated by Thingiverse itself, judging from their format: webdev+$username@makerbot[.]com.
[1]
HIBP's maintainer also claimed that some of the data included poorly encrypted passwords: one he highlighted was an unsalted SHA-1 hash which resolved to the password "test123".
[2]
[3]
Thingiverse is owned by 3D printing firm Makerbot, last seen in these pages back in 2015 when it was [4]making staff redundant after failing to meet "ambitious goals".
Makerbot was less than responsive to his private overtures, Hunt claimed on Twitter, eventually forcing him to go public in the hope of convincing someone that the source of the breach ought to be closed off.
Meanwhile, I get a DM from someone who alleges [5]@thingiverse "have a backup file exposed". I don't ask details, so I never verified the claim (but I have strong reasons to believe this person), and during this process they later told me that "the bucket is set to private now". — Troy Hunt (@troyhunt) [6]October 14, 2021
We have asked Brooklyn-based Makerbot for comment on Hunt's observations, which stretch for a number of tweets that can be read in full by clicking the one above. The company does not appear to have publicly acknowledged the breach so far.
[7]NHS-backed org reacted to GitHub leak disclosure with legal threats and police call, complains IT pro
[8]Why MakerBot failed – but 3D printing is far from dead
[9]Maker–NOT: 3D printer upstart Makerbot jams, cuts extra 20% of staff
[10]McDonald's email blunder broadcasts database creds to comedy competition winners
[11]Hole blasted in Guntrader: UK firearms sales website's CRM database breached, 111,000 users' info spilled online
Breach disclosure is sometimes a difficult topic. Earlier this week El Reg reported on the case of a company that [12]asked a researcher making a responsible disclosure to not contact them again . In that case the researcher had been trying to warn the firm that a Laravel debug page was exposing the username and password for a database – quite concerning given that Schools Marketing Company Ltd claimed to hold the details of a million teachers and school admin personnel.
Earlier this year a fraught disclosure attempt by a techie who formerly worked with an open source org [13]resulted in the police being called and a High Court lawsuit being threatened , all because of misunderstandings.
[14]
Sometimes, however, some companies just don't want to hear bad news – which makes it all the more important to get through to them. ®
Get our [15]Tech Resources
[1] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2YWioljsk@dwYkkfMm4VnAAAAAEQ&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YWioljsk@dwYkkfMm4VnAAAAAEQ&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YWioljsk@dwYkkfMm4VnAAAAAEQ&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[4] https://www.theregister.com/2015/10/08/more_makerbot_layoffs/
[5] https://twitter.com/thingiverse?ref_src=twsrc%5Etfw
[6] https://twitter.com/troyhunt/status/1448593640339623938?ref_src=twsrc%5Etfw
[7] https://www.theregister.com/2021/05/14/apperta_rob_dyke_disclosure_brouhaha/
[8] https://www.theregister.com/2015/05/06/why_makerbot_failed_and_3d_printing_is_far_from_dead/
[9] https://www.theregister.com/2015/10/08/more_makerbot_layoffs/
[10] https://www.theregister.com/2021/09/09/mcdonalds_database_credentials_blunder/
[11] https://www.theregister.com/2021/07/23/guntrader_hacked_111k_users_sql_database/
[12] https://www.theregister.com/2021/10/12/schools_marketing_company_database_credentials_exposed/
[13] https://www.theregister.com/2021/05/14/apperta_rob_dyke_disclosure_brouhaha/
[14] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YWioljsk@dwYkkfMm4VnAAAAAEQ&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[15] https://whitepapers.theregister.com/
Not Surprised.
SusiW
Sadly, since the sale of Thingiverse (MakerBot) to a certain company, this once hallowed site has started to suffer from a lack of funding.
Something like this was bound to happen. I'm just surprised it took so long to occur.
Not just companies
" some companies just don't want to hear bad news – which makes it all the more important to get through to them "
Such examples are minor signs of a very deep problem. Eric Haseltine's 'The spy in Moscow Station' [Icon Books 2019] describes the extraordinary contortions that various US government agencies went through to ignore evidence that pretty much all official communications to and from the US embassy in Moscow were being read in real time by the Soviet security services. This got as extreme as, when hardware keystroke exfiltration modifications were found in a golfball typewriter used in the Ambassador's private office, it was rumoured that the NSA officer in charge of the discovery had fabricated the evidence to improve his career prospects.