News for hackers. Stuff that matters.
Re:Analyzing the compromised DLL file that started the Solor... by smspf on Saturday December 19, 2020 @11:56AM (#25478767)
>In an interesting turn of events, the investigation of the whole SolarWinds compromise led to the discovery of an additional malware that also affects the SolarWinds Orion product but has been determined to be likely unrelated to this compromise and used by a different threat actor.

Either that one was used to compromise the supply chain (in which case it makes little to no sense to keep it around and risk detection), or at least 2 different groups had the chance to target sensitive US infrastructure.

Funny how media coverage of this issue misses no chance of mentioning Russia and nobody else, not even possible suspects.

I wonder what happens if the attackers notice each other on the compromised system. Do they get along in exfiltrating data or do they fight quietly?

Re:Analyzing the compromised DLL file that started the Solor... by Shank on Saturday December 19, 2020 @12:43PM (#25479285)
> Funny how media coverage of this issue misses no chance of mentioning Russia and nobody else, not even possible suspects.

There are parts of the intelligence community that know with confidence who the true attacker is. Even if they had no idea they were being exploited, there are many ways to perform post-mortem analysis when you're, e.g., the NSA. So, someone has 100% confidence, or close to it.

In terms of what the media says: typically, they report on off-the-record remarks from officials and leaks. That's just how the game is played. It's an unfortunate byproduct of everyone wanting to tell, but nobody wanting to be caught telling. The value of Reuters and AP is that they typically do enough due diligence on their own sources to make sure that they're not just spouting nonsense. "Top of the food chain" sources like them are very regularly correct, but fallible.

Re:Analyzing the compromised DLL file that started the Solor... by roywiggins on Saturday December 19, 2020 @01:20PM (#25479680)
The secretary of state has said as much, and pointed at Russia. Sure, he could be lying, but given the president's reflexive defense of Russia, that would be a weird lie to go with. If anything, it's an admission against interest, which strongly suggests to me that this is the assessment of the relevant security agencies.
Re:Analyzing the compromised DLL file that started the Solor... by chris_wot on Saturday December 19, 2020 @04:17PM (#25481295)
Trump said it was China
Re:Analyzing the compromised DLL file that started the Solor... by WarOnPrivacy on Saturday December 19, 2020 @06:15PM (#25482212)
Trump said a thing and China was one of the words in that thing.
Re:Analyzing the compromised DLL file that started the Solor... by akadruid1 on Saturday December 19, 2020 @07:51PM (#25482845)
Don't forget the "intelligence" community is paid to find Russian spooks hiding everywhere. The 2014 JP Morgan hack was blamed on Russian state backed hackers[1]. We know now that was pure speculation and not NSA inside knowledge, since some time later a small criminal gang were successfully prosecuted for it. Apparently they were running a pump-n-dump scheme. 1. https://eu.usatoday.com/story/tech/2014/08/28/russia-jpmorga...
Re:Analyzing the compromised DLL file that started the Solor... by scoot_718 on Saturday December 19, 2020 @11:28PM (#25483846)
> Russian state backed hackers

> small criminal gang

They're the same picture.

Re:Analyzing the compromised DLL file that started the Solor... by jjk166 on Saturday December 19, 2020 @08:01PM (#25482900)
> In terms of what the media says: typically, they report on off-the-record remarks from officials and leaks. That's just how the game is played.

This isn't how the game is supposed to be played and is a symptom of the erosion of the media's journalistic integrity. Anonymous sources can tell you where the bodies are buried, but you still need to dig up the bodies. One would think if you're going through all the trouble to track down three different sources who are both competent and trustworthy to comment on who the government suspects, that you'd take the opportunity to ask a follow up question like "why do you think it was them?" Yeah, everyone wants to be the first to break a story, and real investigation is a lot harder than tabloid journalism, but that's the job, or at least that's what it used to be.

Re:Analyzing the compromised DLL file that started the Solor... by _kbh_ on Sunday December 20, 2020 @12:49AM (#25484174)
And herein lies the problem, anyone who actually knows who it is, is not going to tell you how they know. The intelligence that was used to discover who the attacker, is much more valuable than the information of who the attacker is. The best you'd probably get is 'classified sources/methods/intelligence'.
Re:Analyzing the compromised DLL file that started the Solor... by jjk166 on Sunday December 20, 2020 @03:00PM (#25489052)
And anyone who doesn't know can give you just as much information. If you don't substantiate the rumor, it remains an unsubstantiated rumor.
Re:Analyzing the compromised DLL file that started the Solor... by netsharc on Saturday December 19, 2020 @02:57PM (#25480621)
But media can just add ", person X says" at the end of a sentence and then the burden of proof is no longer with them. They can report that "Obama is born in Kenya, President Trump claims" and, hey, they're reporting the true fact that Trump claimed something...