Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Yahoo! Businesses Security

Some Within Yahoo Knew of Massive Breach in 2014 (usatoday.com) 30

Some within Yahoo knew of a massive data breach that compromised its network when it occurred in 2014, not in late September, when it was first disclosed. From a report on USA Today: An independent committee of Yahoo's board, which launched an internal probe in August to learn more about the state-sponsored attack that affected data belonging to at least 500 million members, discovered that staff knew of the attack two years ago. "The company had identified that a state-sponsored actor had access to the company's network in late 2014," the company said In a filing with Securities and Exchange Commission.
This discussion has been archived. No new comments can be posted.

Some Within Yahoo Knew of Massive Breach in 2014

Comments Filter:
  • by Oswald McWeany ( 2428506 ) on Thursday November 10, 2016 @09:16AM (#53256577)

    Yahoo
        [yah-hoo, yey-, yah-hoo]
    Spell Syllables
    noun, plural Yahoos.
    1.
    (in Swift's Gulliver's Travels) one of a race of brutes, having the form and all the vices of humans, who are subject to the Houyhnhnms.
    2.
    (lowercase) an uncultivated or boorish person; lout; philistine; yokel.
    3.
    (lowercase) a coarse or brutish person.

    Accurate.

  • by Vlad_the_Inhaler ( 32958 ) on Thursday November 10, 2016 @09:49AM (#53256855)

    When Yahoo initially claimed they were breached by a "state sponsored attack", my thoughts were: well - they would say that. Others - better informed - agreed [slashdot.org]. Now that claim is being spun as a "given", is there really any proof at all of that?
    The first I heard about it was at the start of August [slashdot.org]. That appears to be when the "internal probe" was launched, it took them a further 6 weeks to go public.

  • by freeze128 ( 544774 ) on Thursday November 10, 2016 @09:50AM (#53256879)
    We already know this. That's what the whole story in late September was about: Yahoo was hacked and that information was kept from its customers for 2 years. Of course someone inside Yahoo knew about it.

    Maybe this article is just to help stem the mass suicide from learning that Trump won the election.
    • We already know this. That's what the whole story in late September was about: Yahoo was hacked and that information was kept from its customers for 2 years. Of course someone inside Yahoo knew about it.

      The very odd thing that I'm having a problem with is I knew of the breach. At the time, I belonged to several Yahoo groups. A lot of spam and spoofed posts started showing up. Then Yahoo sent out posts telling people to change their passwords. While no one mentioned "State actors", it was pretty obvious that a big hack had just happened.

      Fortunately, I only used my Yahoo email to access the groups, not for anything else. Kinda like there was nothing but the one program I needed Windows for on my W10 machin

  • It was transparently obvious to the rest of us that Yahoo had been breached long before 2014. Empirical evidence of the sheer rate and volume of account compromises (especially re-compromises) over the years compared to other similar services left little else as a plausible explanation. The worst possible news here for Yahoo is that they might be telling the truth and it really took them all the way until 2014 to notice themselves.

  • Wow, it sounds like the state-sponsored attack must have been the US government.

    Can you imagine Yahoo employees keeping their mouths shut for that long if it was a Russian/Chinese/Indian/Iranian-sponsored attack? Or for that matter, even if the evidence wasn't solid, engage in wild speculation? See the recent allegation of Russian support for Trump broadcast as fact despite the lack of any hard evidence.

    We know from the Snowden revelations that in addition to secret courts rubber stamping secret requests; p

  • ROUGE ENGINEER strikes again!

Trap full -- please empty.

Working...