Monday, March 3, 2025
HomeComputer SecurityHackers Abusing Legitimate Googlebot Services to Inject Cryptomining Malware

Hackers Abusing Legitimate Googlebot Services to Inject Cryptomining Malware

Published on

SIEM as a Service

Follow Us on Google News

Cybercriminals now abusing the legitimate Googlebot server using fake User-Agent from another Google service to deliver Crypto-currency malware to the target victims network.

Googlebot is providing legitimate traffic to the website which is to appear in Google search engine results.

Googlebot works by crawling the each and every updated link in your website to allow them into its search engine database and later make them available into users searching on Google’s search engine.

So the user of Googlebot service urged to whitelist the IP address that is the relay in Googlebot server, in this case, the security mechanisms will be bypassed if there will be any malicious traffic coming from Googlebot service.

In this case, there are 2 possible ways to abuse the Googlebot service, one is too controlling the Googlebot server which is extremely difficult, another method could be possible by sending a fake User-Agent from another Google service.

A Method to Trick GoogleBot

Initially, Attackers abuse the Googlebot by using the simple trick to send malicious requests to the targeted victims.

This can be achieved by adding the malicious link within the website along with targeted victims address and the specific payload to drop into victims system.

<a href=”http://victim-address.com/exploit-payload”>malicious link<a>

Once the bot crawls this malicious page then it sends malicious GET request along with exploit-payload to the attacker’s target.

Researchers from F5 Networks said, we used two servers when testing this method—one for the attacker and another for the target. Using Google Search Console, we configured Googlebot to crawl through our attacker’s server where we added a web page that contained a link to the target server.
That link held a malicious payload. After some time sniffing traffic on the target server, we spotted the malicious request with our crafted malicious URL hitting the server. The origin of the request was none other than a legitimate Googlebot.

Based this analysis researchers confirmed that it was the real Googlebot delivering a crafted, malicious payload and it can be easily used by attackers to deliver malicious payloads in the very efficient way.

In this case, the attack could be limited since the attack will not get any response from the target and all the response send to the Googlebot, a real sender.

Attackers using the same method In August to send Apache Struts 2 remote code execution flaw with malicious Java payload is delivered via the URL that was delivered into the target by abusing Googlebot.

Related Read

DNS Hijacking Method Used by Powerful Malware to Hack Android, Desktop & iOS Devices

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

Google Launches Shielded Email to Keep Your Address Hidden from Apps

Google is rolling out a new privacy-focused feature called Shielded Email, designed to prevent apps...

Hackers Using PowerShell and Microsoft Legitimate Apps to Deploy Malware

Cybersecurity experts are warning of an increasing trend in fileless attacks, where hackers leverage...

JavaGhost: Exploiting Amazon IAM Permissions for Phishing Attacks

Unit 42 researchers have observed a threat actor group known as JavaGhost exploiting misconfigurations...

New Poco RAT Via Weaponized PDF Attacking Users to Capture Sensitive Data

A new variant of malware, dubbed "Poco RAT," has emerged as a potent espionage...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Winos4.0 Malware Targets Windows Users Through Malicious PDF Files

A new wave of cyberattacks leveraging the Winos4.0 malware framework has targeted organizations in...

Lotus Blossom Hacker Group Uses Dropbox, Twitter, and Zimbra for C2 Communications

The Lotus Blossom hacker group, also known as Spring Dragon, Billbug, or Thrip, has...

Squidoor: Multi-Vector Malware Exploiting Outlook API, DNS & ICMP Tunneling for C2

A newly identified malware, dubbed "Squidoor," has emerged as a sophisticated threat targeting government,...