Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
How Guccifer 2.0 Got 'Punk'd' by a Security Researcher
Threaded  |  Newest First  |  Oldest First
SchemaCzar
50%
50%
SchemaCzar,
User Rank: Strategist
3/8/2018 | 10:18:09 AM
Why would anyone still believe Guccifer was driven by Russians?
Everything in this article makes me doubt that Guccifer 2.0 was driven by Russian state actors.  To fall for a trick like this is not what happens with Russian state-level hackers.  If the Russians were paying him/her, the only purpose was to muddy the waters.  It's hard to think of a nation-state, or a trans-national movement, that would be unable to set up a cutout like this to "look Russian."
Gorilla Hunter
40%
60%
Gorilla Hunter,
User Rank: Strategist
3/8/2018 | 11:02:48 AM
Re: Why would anyone still believe Guccifer was driven by Russians?
Because "RUSSIA, RUSSIA, RUSSIA". There is nothing here that shows that Guccifer was "punked" or that he is even connected to the Russians, but we have to hear once again "RUSSIA, RUSSIA, RUSSIA!!!1!"
Dong_Johnson
50%
50%
Dong_Johnson,
User Rank: Apprentice
3/8/2018 | 1:38:07 PM
Re: Why would anyone still believe YOU KNOW WHAT YOU TALK ABOUT?
You're not understanding the article I guess.  It's pretty clear Gucci was punked because he's no longer responding.  

 

Russia has various means of accomplishing what they want to, and using low-level useful idiots isn't below their means either.  I agree with the premise presented in the article that it's clear Russia wasn't going "all-in" using state resources (which would be attributable directly, of issue) to publish the stolen emails, and instead decided to disseminate them using troll networks rather than official ones.  The fact is you have no compelling or offered reason to doubt anything in this story.  If you did you wouldn't be doing the typical spambot/chatbot song and dance of crying about people focusing on "russia russia russia' for what Russia did did did provably provably provably.  Get your politics out of here, this is a discussion about facts.   The fact is Russia was involved.

Once again, if you want to discredit any aspect of this, you're going to need something to point to.  Whining won't help your case.
Gorilla Hunter
67%
33%
Gorilla Hunter,
User Rank: Strategist
3/9/2018 | 10:21:49 AM
Re: Why would anyone still believe YOU KNOW WHAT YOU TALK ABOUT?
So because he stopped talking to a reporter, he was punked? You demand facts, yet you are unable to back up your claim with any of your own. Julian Assange, the publisher of the hacked emails and knows who the source is, has came out time and time again saying the Russians had nothing to do with it.

http://thehill.com/policy/cybersecurity/346904-assange-meets-us-congressman-vows-to-prove-russia-did-not-leak-him

https://www.democracynow.org/2017/4/12/full_interview_julian_assange_on_trump 

https://www.huffingtonpost.com/entry/donna-brazile-owes-an-apology-to-julian-assange-and_us_59fe1c3ae4b076eaaae2701d

I doubt the story because I looked at the authors twitter feed, saw her politics, and then read her parroting the same agenda, and  once again hear the clams of "Russia did hax", when everyone who is involved with the DNC email dump says otherwise.  Also included three sources from both left and right. But hey, a dude stopped talking to a reporter, ao case closed, right?

 
antivirussupport12
50%
50%
antivirussupport12,
User Rank: Strategist
3/12/2018 | 11:46:13 AM
Re: Why would anyone still believe YOU KNOW WHAT YOU TALK ABOUT?
I totally agree with you.This the way we can tackle this situation.if you know the situation and all other prospects you can handle it in a better way. visit https://antivirussupport.org for more.
ellascottgm123
50%
50%
ellascottgm123,
User Rank: Apprentice
3/11/2018 | 10:07:03 PM
Re: Why would anyone still believe Guccifer was driven by Russians?
Such a very useful article. Very interesting to read this article.I would like to thank you for the efforts you had made for writing this awesome article.


COVID-19: Latest Security News & Commentary
Dark Reading Staff 6/5/2020
Abandoned Apps May Pose Security Risk to Mobile Devices
Robert Lemos, Contributing Writer,  5/29/2020
How AI and Automation Can Help Bridge the Cybersecurity Talent Gap
Peter Barker, Chief Product Officer at ForgeRock,  6/1/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: What? IT said I needed virus protection!
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-13842
PUBLISHED: 2020-06-05
An issue was discovered on LG mobile devices with Android OS 7.2, 8.0, 8.1, 9, and 10 (MTK chipsets). A dangerous AT command was made available even though it is unused. The LG ID is LVE-SMP-200010 (June 2020).
CVE-2020-13843
PUBLISHED: 2020-06-05
An issue was discovered on LG mobile devices with Android OS software before 2020-06-01. Local users can cause a denial of service because checking of the userdata partition is mishandled. The LG ID is LVE-SMP-200014 (June 2020).
CVE-2020-13839
PUBLISHED: 2020-06-05
An issue was discovered on LG mobile devices with Android OS 7.2, 8.0, 8.1, 9, and 10 (MTK chipsets). Code execution can occur via a custom AT command handler buffer overflow. The LG ID is LVE-SMP-200007 (June 2020).
CVE-2020-13840
PUBLISHED: 2020-06-05
An issue was discovered on LG mobile devices with Android OS 7.2, 8.0, 8.1, 9, and 10 (MTK chipsets). Code execution can occur via an MTK AT command handler buffer overflow. The LG ID is LVE-SMP-200008 (June 2020).
CVE-2020-13841
PUBLISHED: 2020-06-05
An issue was discovered on LG mobile devices with Android OS 9 and 10 (MTK chipsets). An AT command handler allows attackers to bypass intended access restrictions. The LG ID is LVE-SMP-200009 (June 2020).