Thank You

[edit]

I just wanted to post a quick note of appreciation to the many editors who contributed to this article. Thanks to everyone's efforts it was linked on the Main Page (in WP:ITN) barely a day after creation. Well done. -Ad Orientem (talk) 20:10, 24 September 2016 (UTC)[reply]

Mention of PRISM and MUSCULAR on "Events" Section

[edit]

I think the last paragraph of the Events section, about other actors having access to Yahoo´s data (meaning PRISM and MUSCULAR programs) is quite misleading as these are a different kind of data breachs. Maybe we could move this to the article´s ending in the "See also" section? Javier Jelovcan (talk) 12:56, 28 September 2016 (UTC)[reply]

@Javier Jelovcan: How are these different kinds of data breaches? It seems that the only two differences are that those programs also breached into the content of email-accounts and not just the account-info (not enough to breach into most yahoo accounts and thereby gain access to the content) and that it wasn't self-reported by Yahoo but instead was disclosed by a whistleblower's leaks. However, while I do think that this information needs to be included in the article I too think that the "Events" section might be a bit inappropriate - it's not really part of the events of this breach. So either the section needs to be renamed (e.g. to "Background" or alike) or a new section needs to be set up.
--Fixuture (talk) 17:09, 30 September 2016 (UTC)[reply]

Just want to agree with Javier that these breaches seem quite separate. As a casual reader, it felt like the article was trying to make a political point. The government breaches probably don't belong in this article. People reading this article are interested in the specific breaches cited in the news recently, not in "every time that Yahoo user data has been compromised". — Preceding unsigned comment added by 2600:1017:B425:8ED4:5D1E:F33C:6EC9:9CCF (talk) 16:44, 2 October 2016 (UTC)[reply]

Well, I happen to agree with the inclusion of the mentions. If a government actor is mentioned, it should be made clear to what extent various such actors are already involved, as part of general context. Samsara 01:40, 4 October 2016 (UTC)[reply]

It's actually 2 breaches that have been disclosed: 2012 and 2014

[edit]

While the article is named Yahoo! data breach it seems that 2 separate breaches were publicized more or less at the same time:

Not sure if those 2 breaches are in any way related (e.g. by motivation, by attacker, by method used in the breach etc.). I'm also not sure whether or not Yahoo has confirmed this breach to date. Maybe they try to damage control by only confirming the larger breach and trying to only imply that the previous breach occurred as well without explicitly confirming it?

So what should be done here?
Should the article be renamed to sth like "Yahoo! data breaches" or "2014 and 2012 Yahoo! data breaches" or "Yahoo! data breaches revealed in 2016"...?
Or should there be a new article for the 2012 breach? (And if so: what about the other social media accounts "Peace_of_mind" is selling? It looks like those sites were breached as well.)
Or nothing at all?

--Fixuture (talk) 17:26, 30 September 2016 (UTC)[reply]

For now, the two breaches should have clearly delineated and headlined sections. Once that's been achieved, it'll be easier to decide whether a split of the article is appropriate or not. Samsara 22:37, 1 October 2016 (UTC)[reply]
The 2012 breach apparently refers to the 2012 LinkedIn hack. FallingGravity 21:06, 16 December 2016 (UTC)[reply]

Open questions

[edit]

There are a number of open questions I'd like to know the answers to if anybody has them (or can help find the answers to; Yahoo should have provided them already or clearer):

Note that these open questions may also be included in the article if they were/are not answered.

--Fixuture (talk) 18:06, 30 September 2016 (UTC)[reply]

Strictly speaking, we can't raise questions that aren't raised in reliable sources. If you can't find these questions raised elsewhere, maybe get in touch with Ars Technica, Wired or any similar publication to see if they'll accept an editorial contribution from you. Once that's published, there should be no question that we can cite it. I know it's silly, but that's how the current model works. If you want some help writing such a piece, let me know. HTH, Samsara 22:56, 1 October 2016 (UTC)[reply]

Another data breach

[edit]

There are reports of some 1 billion odd accounts (New York Times, Wall Street Journal, TechnoBuffalo, and more). This appears to be a different breach than the one the article currently covers. We could either incorporate this into the current article and rename it "Yahoo! data breaches" or move the current article to "2014 Yahoo! data breach" and create a new article 2013 Yahoo! data breach. However, as mentioned above, the current article also covers a 2012 data breach. I guess if this keeps up we'll see a data breach from Yahoo! every year. FallingGravity 02:41, 15 December 2016 (UTC)[reply]

Given the extent to which reliable sources are reporting on the separate incidents together (focusing on the underlying vulnerabilities and combined impact on the company and on the public), I favor expanding this article and renaming it Yahoo! data breaches. —David Levy 03:34, 15 December 2016 (UTC)[reply]
Since it's believed to be the same "state actors", I'm going ahead and moving it to "Yahoo! data breaches". There still isn't that much info about the new hack in the article yet. FallingGravity 09:39, 15 December 2016 (UTC)[reply]

Removed info on the 2012 breach

[edit]

A few days ago User:FallingGravity removed the "2012 breach" section, saying that it's about the 2012 LinkedIn hack.

While that's correct the section also contained information on the breach that apparently occurred in 2012. As of right now the "July 2016 discovery" section contains parts of that now-removed section. However there is no section "2012 breach" despite there apparently being a third breach and it's missing much info that was previously found in the removed section such as the motivation of the hackers and the use of the data.

Should parts of it be restored? If so how (should the section be renamed, left as it is or a new section get added)?

--Fixuture (talk) 18:15, 2 January 2017 (UTC)[reply]

No, it should be kept out. The only connection to the 2012 LinkedIn hack is that there is the same black market seller involved in both. It's necessary to name this seller (and his connection to the 2012 hack) because awareness of this data led to the discovery of these larger breaches. The 2016 discovery section properly alludes to the seller's roll in the 2012 hack, but that's all that's needed. --MASEM (t) 18:19, 2 January 2017 (UTC)[reply]

Article Frustratingly Lacks Basic Information

[edit]

There does not appear to be even the most basic information posted related to this. Breach could mean anything, obviously it's implied credentials to the accounts were gained, but then what was done?

I assume passwords and contact information was downloaded for every account. What about individual emails, did the hackers download every email?

Did they download location information?

Contact Lists?

Calendar Appointments?

Where is the information — Preceding unsigned comment added by 108.29.37.45 (talk) 18:27, 8 February 2020 (UTC)[reply]

GA Review

[edit]

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


This review is transcluded from Talk:Yahoo! data breaches/GA1. The edit link for this section can be used to add comments to the review.

Nominator: Joereddington (talk · contribs) 05:53, 27 March 2024 (UTC)[reply]

Reviewer: Sohom Datta (talk · contribs) 06:52, 31 March 2024 (UTC)[reply]

Another security article in GA finally! I'll take this on tmrw, feel free to ping liberally in case I forget. Sohom (talk) 06:52, 31 March 2024 (UTC)[reply]

Awesome. I just gave bit a bit of a check over and sorted out a bunch of typos that snuck in :) Joe (talk) 11:37, 31 March 2024 (UTC)[reply]

Review

[edit]

Giving this an initial read, this is unfortunately going to have to be a quick fail since as it currently stands the article is a pretty long way from meeting the official good article guidelines. Particularly,

I think most of these issues can be solved by rewriting the article with some help from WP:GOCE. The sourcing behind the article is strong, and I definitely think a GA is within reason. I hope to see this article back at GA once the issues mentioned are fixed. Sohom (talk) 17:22, 31 March 2024 (UTC)[reply]

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

GA Review

[edit]
This review is transcluded from Talk:Yahoo! data breaches/GA2. The edit link for this section can be used to add comments to the review.

Nominator: Joereddington (talk · contribs) 06:34, 2 April 2024 (UTC)[reply]

Reviewer: Schierbecker (talk · contribs) 18:17, 22 April 2024 (UTC)[reply]


This article appears to still be a little ways off from GA.


 On hold pending improvements. Schierbecker (talk) 18:17, 22 April 2024 (UTC)[reply]

Wonderful! Thank you so much for your review. I'll pop back shortly to do proper replies/fixes - I suspect that the answer to some of your questions is "Yahoo refuses to give any information about this and thus there are no relable sources one way or the other", but I can make some changes on the basis of this :) Joe (talk) 12:04, 23 April 2024 (UTC)[reply]
Right, I've fixed an array of things and replied to all comments. Apologies for how many of the answers are "There isn't really a source for that" I did do quite a bit of digging... Joe (talk) 18:49, 24 April 2024 (UTC)[reply]
Hi, can I check in and see what's left to do? I'm aware that the clock is ticking and I don't want to miss out on the GA because I forgot to response to a particular comment :) Joe (talk) 06:42, 27 April 2024 (UTC)[reply]
It appears that Igor Sushchin is linked to the wrong guy. Will take a look tomorrow. Schierbecker (talk) 07:22, 27 April 2024 (UTC)[reply]
Definately the wrong guy (his age is about ten years different on the indictment compared to the wiki article) Joe (talk) 19:10, 30 April 2024 (UTC)[reply]
I've used this source now :)
I've used this source now :)
I found a paragraph I'd removed previously and resurrected it (with your excellent source above)
So I'm a little nervous here. On the one hand I don't want to add much content for exactly BLPCRIME reasons - all that we actually know is that he's been accused. The other problem is that Belan's own Wikipedia article is magnificently low on content. We could say that he was last known to be in Krasnodar Russia (per https://www.fbi.gov/wanted/cyber/alexsey-belan) but the major issue there is that page is showing signs of having barely been updated since before the breach... Is this in one of the GA criteria or is this more of a 'nice to have' thing? Joe (talk) 11:10, 1 May 2024 (UTC)[reply]
I guess we don't know for sure that he fled? Just that his last known location was in Russia? You could say that. Just make sure to attribute this to the FBI. Use Internet Archive to lock down when the FBI said this. Schierbecker (talk) 15:38, 1 May 2024 (UTC)[reply]
Fixed :)
I think this is done, I'm not sure. :)
Done :)
Done :)

Schierbecker (talk) 20:57, 30 April 2024 (UTC)[reply]

Done :)
Found! :)
Done :)
Done :)
Done :)
Your memory of the culture at the time matches mine; I'd love a source that suggested that the breach was a factor, but I haven't found one, and I wouldn't expect to: it is genuinely amazing how little a splash the whole thing made overall. I think Mayer went basically because she wasn't able to make the shareholders enough money.
American, and then owned (mostly) by another technically American company. I'm happy to put that in, but I also feel like the company is multinational enough that it's not particularly in context. (Like, Sony is a Japanese Company but that's not mentioned (and I would argue, not particular relevant) in 2014_Sony_Pictures_hack (you can argue that because it used to be Columbia Pictures, it's an American Company owned by a Japanese one but we end up a long way from the actual topic.Joe (talk) 20:01, 8 May 2024 (UTC)[reply]
It's a great quote for an anecdote - I'm just wary about using it in an encyclopedia (and I spent a lot of time cleaning up random incorrect quotes in a previous version of this article that I am a little anti) - I don't mind much either way tho. The AU Law Review source is genuinely extremely good and I'm glad you found it. You have probably noticed I'm periodically sneaking it in to back up other things. Joe (talk) 20:01, 8 May 2024 (UTC)[reply]
Fixed, one snuck in when I copied from a previous version.
DOne
I'm paywalled for that one, I'm fine for you to throw it in tho...Joe (talk) 20:01, 8 May 2024 (UTC)[reply]
I believe not. There's a stonewalling press comment at and then a letter letter from the chairs of the relevant Senate committee complaining about lack of information (https://www.commerce.senate.gov/services/files/35ecbbeb-9fc1-4913-9448-c8d29807f93c) so I get the impression it was just stonewalling.
I have gone with 'a' - 'any' might also work
Fixed the comma :)
the AU article is the strongest source we have, but it's all still alleged and vague and rests on the word of an anonymous criminal. It's relevant to the article in that it's (allegedly) what prompted Yahoo to take a look at their severs, but the FBI indictment that went out (which I feel is our strongest source) doesn't reference it (I think, I should double check that)Joe (talk) 20:01, 8 May 2024 (UTC)[reply]
Baratov's book is annoyingly vague and slightly hard to believe on the topic of his methods. I would have bet that it boiled down to 'just spear phishing all day' but his memoir has a lot of things in it that are incompatible with that (breaking into accounts with lost passwords for example). In general Yahoo claim there was some evidence of Cookie Forging - but the FBI indictment covers a wide spread of different techniques all of which are things done _after_ access was gained. I'd bet it was originally speak phishing (because these things always turn out to be) but I don't have a clear unequivocal source.

Next batch

[edit]
So, there's some other sources about Infoarmour - they (along with a bunch of other security firms who I feel were looking for publicity) broadly looked at the some forums to see if anyone was selling a billion records and didn't find anything conclusive. I'd assume that NYT is a reliable source, but this quote looks like an error given that it doesn't match up with any statements by Yahoo or law enforcement.
For the diplomatic tensions bit - I imagine it did threaten to, but it's like two months before this sort of thing https://web.archive.org/web/20170515224247/https://www.nytimes.com/2017/05/15/us/politics/trump-russia-classified-information-isis.html so I don't think it was really a blip in the wild ride that is US-Russia relations.
The quote about the targets is I think almost verbatim from the inditement. I haven't got a reason to doubt it but on the other hand I'm trying to presume innocence...Joe (talk) 06:05, 25 May 2024 (UTC)[reply]

Baratov, the only man arrested, was extradited to the United States when?

Fixed
That sentance was a mess and I've redone it.

Instead, Yahoo last week posted an alert on its website asking users who were potentially affected by the breach to “promptly change their passwords,” as well as any security questions and answers used to access their accounts. [2] I'll send a screenshot if you need.

I'm 50-50. There's a lot of different quotes from fairly good sources we can use to take a swing at Mayer (who was clearly in charge and who clearly wasn't prioritising security), but I'm worried about a) UNDUE WEIGHT and b) overcompensating for the lack of technical details about the breach my making the article a hit-piece. Joe (talk)
Fixed
Reworded
Fixed in a couple of places.
I've reworded so it's clear he's CEO of Verizon. It's certainly suggested by a bunch of outlets that there was a big negociation, and their probably was, but we have no sources in the room where it happened.
Added.
Fixed
Fixed
Not entirely sure I follow this? Joe (talk) 06:05, 25 May 2024 (UTC)[reply]
Fixed
Done
That's certainly what a selection of sources say. I don't particularly like the inference but I think it was added in as a response to some of your earlier comments?

Next Split

[edit]
Lede
Hmmm... I don't know how much I buy that compartmentalization was any more or less than at equivilent companies... it feels like a leap when we don't even have technical details for the breaches?
My reading of MOS:$ was that the first usage should be "US$"?
I'm game, but it was also investigated by other countries? I think this has come up before and we don't have a clear steer from MOS...
Done.


I've popped the year in.
August 2013
breach
Done, good tip!
Early 2014
security culture at Yahoo
Done (finding a short word for Snowdon took a while!)
Rewored - I don't think the quotes I've found are attributed (I do think they come from him, but...)
Late 2014
breach
Done.
Hmmm, I'm vaguely sure it's capitalised in the indictment. Also it's a proper noun right? Because it's the core example. Like: there are many caves that have bats that would be batcaves, but Batcave is capitalised? Joe (talk) 06:30, 25 May 2024 (UTC)[reply]
Ha! Fixed.
I've reworded the start of the section to make it clear that it's not set.
July 2016 to October 2017
public disclosures
Within 24 hours (on the basis it's in the the articles that are from the 23rd) but I don't have a particular source.
Done
Done
Prosecution
Reworded.


Done
rewritten


Class action lawsuits
Done
Reworded to be much more correct.


International
Done
Done
Done
Dealt with earlier.

The final stretch

[edit]

Nearly there.

lede
Done
Done
Done
August 2013
Done
Done
Done
Early 2014
Done
Late 2014

believed to by the US Justice Department extraneous word

Done
Done
July 2016
Done
July 2016 to October 2017
Done
Prosecution
Class action lawsuits
Done
Done
International
Done
General commenets/questions
Done - I picked "U.S."
Done
Done
Mayer certainly did at congress https://www.reuters.com/article/idUSKBN1D825V - (there's a cute fact about the volentary testimony at the bottom) but Yahoo certainly didn't at the initial disclosure. It's an odd PR 'thing'. I can definately put Mayer's bit in somewhere?
I think I might have missed that in the sources? Can you point me in the right direction.
Added with a certain amount of discretion.
That's a different event - it's included in a few other sources.
With my computer-person hat on - it's nice that the FBI said this but it's entirely within what one would privately expect: the vast marjority of large scale breaches are spear-phishing and the only thing suprising here is that Yahoo's logging was bad enough that they don't know who got phished, or, it appears, much else about the whole affair.
This batch has been processed! Thank you so much for all your work on it :) Joe (talk) 06:39, 27 May 2024 (UTC)[reply]

 Pass Congratulations! Schierbecker (talk) 15:21, 29 May 2024 (UTC)[reply]