While the concept of fraudulent emergency data requests previously ended up used by other threat actors, such as Lapsus$, the increase in postings on criminal forums regarding the process of emergency data requests and sale of compromised credentials has led to an increase of their use.
FBI encourages organizations to work to reduce the likelihood and impact from submission of fraudulent emergency data requests to attempt to gain unauthorized access to PII.
Enhanced password protocols implemented in early 2023 highlighted a mandated increase in password length, the use of multi-factor-authentication (MFA) for users with administrative rights, policy controls directed at vishing, and improved baseline monitoring worked together to decrease successful attempts at cracking passwords. Furthermore, this all made networks more resilient to a threat actor’s initial intrusion and persistence.
As of August 2024, FBI noted an uptick in criminal forum posts such as:
- In August 2024, a known cyber-criminal on an online forum posted their sale of “High Quality .gov emails for espionage/social engineering/data extortion/Dada requests, etc”, which included U.S. credentials. The poster indicated they could guide a buyer through emergency data requests and sell real stolen subpoena documents to pose as a law officer.
- In March 2024, a known cyber-criminal on an online forum indicated they “owned” government emails from over 25 countries, and through a successful subpoena, the requestor could gain access to usernames, emails, phone numbers, and other private client information.
- In March 2024, a known cyber-criminal posted photos on an online forum of a fraudulent emergency data request submitted to Paypal. According to PayPal, the threat actor submitted a fraudulent Mutual Legal Assistance Treaty (MLAT) regarding a local ongoing investigation into child trafficking, which included a case number and legal code for verification, but the request was ultimately denied by PayPal.
- In December 2023, cyber-criminals sent a fake emergency data request, along with a statement to provide the requested information immediately, indicating an individual would suffer greatly or die unless the requested information ended up provided by the company.
- In October 2023, a known cyber-criminal stated on an online forum that .gov emails could end up used to carry out emergency data requests on users, and allow a user to “become” a law enforcement officer or government entity. They further stated the data obtained could carry out phishing or malware attacks against the government sector and become an initial access vector.
- In August 2023, a cyber-criminal stated they were teaching individuals how to create and submit their own emergency data requests to get information on any social media account for $100.
Additionally, FBI recommends government and other organizations that receive emergency data requests take the steps below to improve their security posture in response to the noted attack trends and possible outcomes using more resilient security protocols, such as:
Mitigation for cyber incidents:
- Review the security posture of third-party vendors and those interconnected with your organization. Ensure you monitor and review for suspicious activity all connections between third-party vendors and outside software or hardware.
- Document and monitor external remote connections. Organizations should document approved solutions for remote management and maintenance, and immediately investigate if an unapproved solution is on a workstation.
- Implement a recovery plan to maintain and retain multiple copies of sensitive or proprietary data and servers in a physically separate, segmented, and secure location (that is, a hard drive, other storage device, or the cloud).
- Private sector companies receiving law enforcement requests should apply critical thinking to any emergency data requests received. Cyber-criminals understand the need for exigency, and use it to their advantage to shortcut the necessary analysis of the emergency data request.
- Develop and implement strong password protocols: Passwords should use at least 16 characters; even longer passwords are better and significantly reduce risk. Password length is the greater mitigating factor, compared to complexity.
- Use Secure Password Storage: Require all accounts with password logins (for example, service account, admin accounts, and domain admin accounts) to comply with National Institute of Standards and Technology (NIST) standards for developing and managing password policies.
- Require default credentials be changed on all hardware and software products.
- Require phishing-resistant multifactor authentication for all services to the extent possible.
- Review domain controllers, servers, workstations, and active directories for new and/or unrecognized accounts.
- Audit user accounts with administrative privileges, and configure access controls according to the principle of least privilege.
Implement time-based access for accounts set at the admin level and higher. - Generate compliance reports to better assess your organization’s password compliance status, in particular highlighting areas of non-compliance, vulnerabilities, and potential risks related to password security.
- Secure and closely monitor remote desktop protocol (RDP) use.
- Limit access to resources over internal networks, especially by restricting RDP and using virtual desktop infrastructure.
- Segment networks to prevent the spread of malware/ransomware.
- Identify, detect, and investigate abnormal activity and potential traversal of any indicated malware/ransomware with a networking monitoring tool.
- Install, regularly update, and enable real time detection for antivirus software on all hosts.
Vulnerability and Configuration Management:
Keep all operating systems, software, and firmware up to date: Timely patching is one of the most efficient and cost-effective steps an organization can take to minimize its exposure to cybersecurity threats.
Disable command-line and scripting activities and permissions. Privilege escalation and lateral movement often depend on software utilities running from the command line.
Ensure proper device configuration and enable security features.
Disable ports and protocols not used for a business purpose.
Restrict Server Message Block (SMB) Protocol within the network to only access servers that are necessary, and remove or disable outdated versions of SMB.

