Attacks/Breaches

5/3/2017
07:30 PM
100%
0%

Google Docs Phishing Attack Abuses Legitimate Third-Party Sharing

Phishing messages appear nearly identical to legitimate requests to share Google documents, because in many ways, they are.

Google users today were hit with an extremely convincing phishing spree launched by attackers who manipulated Google Docs' legitimate third-party sharing mechanism.

Targets received messages with the subject like "[Sender] has shared a document on Google Docs with you" often from senders they knew. The messages contained links, which led to a page that clearly requested access to the user's Gmail account. If the target user provides access, the attack begins sending spam to all the user's contacts. Theoretically, the attacker could also access the victim's messages and steal sensitive data, but thus far there have been no reports of such activity.

Because it takes advantage of Google's legitimate third-party sharing mechanism, the phishing message is much more difficult to identify as malicious. The icons and messaging are familiar to Google users. Gmail itself did not filter the messages as phishing or flag them as spam, but rather sent them to Gmail users' "Primary" inbox mail folders. The senders were familiar enough to have the target in their contact lists.

One way to spot the attack: some targets report that the message includes a recipient with an address that begins "hhhhhhhhhhhhhh" and ends with the domain "mailinator.com."  

Google responded with a fix and issued a statement

"We have taken action to protect users against an email impersonating Google Docs, and have disabled offending accounts. We’ve removed the fake pages, pushed updates through Safe Browsing, and our abuse team is working to prevent this kind of spoofing from happening again. We encourage users to report phishing emails in Gmail. If you think you were affected, visit http://g.co/SecurityCheckup"

Those who have already fallen victim to this attack should also go to their Google account permissions settings and revoke access to the false "Google Docs" application. They're also advised to set up two-factor authentication.

Read more here.

 

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
'Hidden Tunnels' Help Hackers Launch Financial Services Attacks
Kelly Sheridan, Staff Editor, Dark Reading,  6/20/2018
Tesla Employee Steals, Sabotages Company Data
Jai Vijayan, Freelance writer,  6/19/2018
Inside a SamSam Ransomware Attack
Ajit Sancheti, CEO and Co-Founder, Preempt,  6/20/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-2668
PUBLISHED: 2018-06-22
389-ds-base before versions 1.3.5.17 and 1.3.6.10 is vulnerable to an invalid pointer dereference in the way LDAP bind requests are handled. A remote unauthenticated attacker could use this flaw to make ns-slapd crash via a specially crafted LDAP bind request, resulting in denial of service.
CVE-2017-7466
PUBLISHED: 2018-06-22
Ansible before version 2.3 has an input validation vulnerability in the handling of data sent from client systems. An attacker with control over a client system being managed by Ansible, and the ability to send facts back to the Ansible server, could use this flaw to execute arbitrary code on the An...
CVE-2018-12648
PUBLISHED: 2018-06-22
The WEBP::GetLE32 function in XMPFiles/source/FormatSupport/WEBP_Support.hpp in Exempi 2.4.5 has a NULL pointer dereference.
CVE-2018-12641
PUBLISHED: 2018-06-22
An issue was discovered in arm_pt in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.30. Stack Exhaustion occurs in the C++ demangling functions provided by libiberty, and there are recursive stack frames: demangle_arm_hp_template, demangle_class_name, demangle_fund_type, do_type, do_...
CVE-2018-12642
PUBLISHED: 2018-06-22
Froxlor through 0.9.39.5 has Incorrect Access Control for tickets not owned by the current user.