Valid Accounts

APT18 actors leverage legitimate credentials to log into external remote services.^[2]

APT28 has used legitimate credentials to gain initial access, maintain access, and exfiltrate data from a victim network. The group has specifically used credentials stolen through a spearphishing email to login to the DCCC network. The group has also leveraged default manufacturer's passwords to gain initial access to corporate networks via IoT devices such as a VOIP phone, printer, and video decoder.^[3][4][5][6]

APT29 used different compromised credentials for remote access and to move laterally.^[7][8][9]

APT33 has used valid accounts for initial access and privilege escalation.^[10][11]

APT39 has used stolen credentials to compromise Outlook Web Access (OWA).^[12]

APT41 used compromised credentials to log on to other systems.^[13][14]

Carbanak actors used legitimate credentials of banking employees to perform operations that sent them millions of dollars.^[15]

Chimera has used a valid account to maintain persistence via scheduled task.^[16]

Dragonfly 2.0 compromised user credentials and used valid accounts for operations.^[17]

Dtrack used hard-coded credentials to gain access to a network share.^[18]

Adversaries can instruct Duqu to spread laterally by copying itself to shares it has enumerated and for which it has obtained legitimate credentials (via keylogging or other means). The remote host is then infected by using the compromised credentials to schedule a task on remote machines that executes the malware.^[19]

FIN10 has used stolen credentials to connect remotely to victim networks using VPNs protected with only a single factor.^[20]

FIN4 has used legitimate credentials to hijack email communications.^[21][22]

FIN5 has used legitimate VPN, RDP, Citrix, or VNC credentials to maintain access to a victim environment.^[23][24][25]

To move laterally on a victim network, FIN6 has used credentials stolen from various systems on which it gathered usernames and password hashes.^[26][27][28]

FIN7 has harvested valid administrative credentials for lateral movement.^[29]

FIN8 has used valid accounts for persistence and lateral movement.^[30]

Fox Kitten has used valid credentials with various services during lateral movement.^[31]

GALLIUM leveraged valid accounts to maintain access to a victim network.^[32]

Industroyer can use supplied user credentials to execute processes and stop services.^[33]

Kinsing has used valid SSH credentials to access remote hosts.^[34]

Leviathan has obtained valid accounts to gain initial access.^[35][36]

Linux Rabbit acquires valid SSH accounts through brute force. ^[37]

menuPass has used valid accounts including shared between Managed Service Providers and clients to move between the two environments.^{[38][39][40][41]}

Night Dragon has used compromised VPN accounts to gain access to victim systems.^[42]

OilRig has used compromised credentials to access other systems on a victim network.^[43][44][14]

Operation Wocao has used valid VPN credentials to gain initial access.^[45]

PittyTiger attempts to obtain legitimate credentials during operations.^[46]

Sandworm Team have used previously acquired legitimate credentials prior to attacks.^[47]

Some SeaDuke samples have a module to extract email from Microsoft Exchange servers using compromised credentials.^[48]

Silence has used compromised credentials to log on to other systems and escalate privileges.^[49]

Silent Librarian has used compromised credentials to obtain unauthorized access to online accounts.^[50]

Suckfly used legitimate account credentials that they dumped to navigate the internal victim network as though they were the legitimate account owner.^[51]

TEMP.Veles has used compromised VPN accounts.^[52]

Threat Group-3390 actors obtain legitimate credentials using a variety of methods and use them to further lateral movement on victim networks.^[53]

Wizard Spider has used valid credentials for privileged accounts with the goal of accessing domain controllers.^[54]

Ensure that applications do not store sensitive data or credentials insecurely. (e.g. plaintext credentials in code, published credentials in repositories, or credentials in public cloud storage).

Applications and appliances that utilize default username and password should be changed immediately after the installation, and before deployment to a production environment. ^[55] When possible, applications that use SSH keys should be updated periodically and properly secured.

Audit domain and local accounts as well as their permission levels routinely to look for situations that could allow an adversary to gain wide access by obtaining credentials of a privileged account. ^{[1] [56]} These audits should also include if default accounts have been enabled, or if new local accounts are created that have not be authorized. Follow best practices for design and administration of an enterprise network to limit privileged account use across administrative tiers. ^[57]

Applications may send push notifications to verify a login as a form of multi-factor authentication (MFA). Train users to only accept valid push notifications and to report suspicious push notifications.