Skip to Content
logologo
AI Incident Database
Open TwitterOpen RSS FeedOpen FacebookOpen LinkedInOpen GitHub
Open Menu
Discover
Submit
  • Welcome to the AIID
  • Discover Incidents
  • Spatial View
  • Table View
  • List view
  • Entities
  • Taxonomies
  • Submit Incident Reports
  • Submission Leaderboard
  • Blog
  • AI News Digest
  • Risk Checklists
  • Random Incident
  • Sign Up
Collapse
Discover
Submit
  • Welcome to the AIID
  • Discover Incidents
  • Spatial View
  • Table View
  • List view
  • Entities
  • Taxonomies
  • Submit Incident Reports
  • Submission Leaderboard
  • Blog
  • AI News Digest
  • Risk Checklists
  • Random Incident
  • Sign Up
Collapse

Report 3215

Associated Incidents

Incident 5671 Report
Deepfake Voice Exploit Compromises Retool's Cloud Services

Loading...
Hacker Deepfakes Employee's Voice in Phone Call to Breach IT Company
pcmag.com · 2023

A hacker used AI to deepfake an employee’s voice and break into an IT company. 

The breach, which ensnared 27 cloud customers, occurred last month at Retool, a company that helps clients build business software.

The hacker kicked off the intrusion by sending several employees at Retool SMS-based text messages that claimed to come from a member of Retool’s IT team who was reaching out to resolve a payroll issue preventing employees from receiving healthcare coverage. Most Retool employees who received the phishing message refrained from responding, except for one. 

The unsuspecting employee clicked a URL in the message, which forwarded them to a fake internet portal to log in. After logging into the portal, which included a multi-factor authentication form, the hacker called the employee while using an AI-powered deepfake.   

“The caller claimed to be one of the members of the IT team, and deepfaked our employee’s actual voice,” Retool said in the report. “The voice was familiar with the floor plan of the office, coworkers, and internal processes of the company. Throughout the conversation, the employee grew more and more suspicious, but unfortunately did provide the attacker one additional multi-factor authentication (MFA) code.”

The incident suggests the mysterious attacker may have already infiltrated Retool to some extent before calling the employee. Once the multi-factor code was given up, the attacker added their own device to the employee’s account and pivoted toward accessing their GSuite account.

Retool says the GSuite access was especially devastating since Google’s Authenticator app recently incorporated a cloud syncing function. This means your multi-factor authenticator codes can be viewed on more than one device, like a smartphone and a tablet synced to the account.

Google added the cloud syncing so people could access MFA codes in the event their phone was lost or stolen. But Retool points out a key drawback to the approach: "If your Google account is compromised, so now are your MFA codes.”

“The fact that access to a Google account immediately gave access to all MFA tokens held within that account is the major reason why the attacker was able to get into our internal systems," the company adds.

Although Retool has since revoked the hacker’s access, it decided to disclose the incident to warn other companies about protecting themselves from similar attacks. “Social engineering is a very real and credible attack vector, and anyone can be made a target," it says. "If your company is large enough, there will be somebody who unwittingly clicks a link and gets phished.”

The company also urged Google to change its authenticator app to make it easier for companies to disable the cloud-syncing function for their employees. Google didn’t immediately respond to a request for comment.

Read the Source

Research

  • Defining an “AI Incident”
  • Defining an “AI Incident Response”
  • Database Roadmap
  • Related Work
  • Download Complete Database

Project and Community

  • About
  • Contact and Follow
  • Apps and Summaries
  • Editor’s Guide

Incidents

  • All Incidents in List Form
  • Flagged Incidents
  • Submission Queue
  • Classifications View
  • Taxonomies

2024 - AI Incident Database

  • Terms of use
  • Privacy Policy
  • Open twitterOpen githubOpen rssOpen facebookOpen linkedin
  • e1b50cd