T1078: Valid Accounts
AI Answer
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, (Source: MITRE ATT&CK T1078)
ATT&CK Mapping
| Field | Value |
|---|---|
| Technique ID | T1078 |
| Name | Valid Accounts |
| Tactic | stealth (stealth) |
| Platforms | Containers, ESXi, IaaS, Identity Provider, Linux, macOS, Network Devices, Office Suite, SaaS, Windows |
| Sub-technique | No |
Why it matters
In the OpenTrojan knowledge graph, Valid Accounts (T1078) is one of the highest-connectivity ATT&CK techniques: 65 MITRE STIX relationships reference this technique; 47 threat groups observed using it; 7 software families associated; 11 campaigns associated; 52 OpenTrojan content pages reference it. These counts are derived from MITRE ATT&CK STIX relationships and are not an estimate of exploitation volume.
How attackers use it
Behavior described below is from the MITRE ATT&CK canonical definition (source: https://attack.mitre.org/techniques/T1078). Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence. In some cases, adversaries may abuse inactive accounts: for example, those belonging to individuals who are no longer part of an organization. Using these accounts may allow the adversary to evade detection, as the original account user will not be present to identify any anomalous activity taking place on their account. The overlap of permissions for local, domain, and cloud accounts across a network of systems is of concern because the adversary may be able to pivot across accounts and systems to reach a high level of access (i.e., domain or enterprise administrator) to bypass access controls set within the enterprise.
Detection
DET0560 Detection of Valid Account Abuse Across Platforms AN1543 Detection of compromised or misused valid accounts via anomalous logon patterns, abnormal logon types, and inconsistent geographic or time-based activity across Windows endpoints. AN1544 Detection of valid account misuse through SSH logins, sudo/su abuse, and service account anomalies outside expected patterns. AN1545 Detection of interactive and remote logins by service accounts or users at unusual times, with unexpected child process activity. AN1546 Detection of valid account abuse in IdP logs via geographic anomalies, impossible travel, risky sign-ins, and multiple MFA attempts or failures. AN1547 Detection of containerized service accounts or compromised kubeconfigs being used for cluster access from unexpected nodes or IPs.
Detection strategy text is from the MITRE ATT&CK official technique page (https://attack.mitre.org/techniques/T1078).
Mitigation
Application Developer Guidance focuses on providing developers with the knowledge, tools, and best practices needed to write secure code, reduce vulnerabilities, and implement secure design principles. By integrating security throughout the software development lifecycle (SDLC), this mitigation aims to prevent the introduction of exploitable weaknesses in applications, systems, and APIs. This mitigation can be implemented through the following measures:
Preventing SQL Injection (Secure Coding Practice):
- Implementation: Train developers to use parameterized queries or prepared statements instead of directly embedding user input into SQL queries.
- Use Case: A web application accepts user input to search a database. By sanitizing and validating user inputs, developers can prevent attackers from injecting malicious SQL commands.
Cross-Site Scripting (XSS) Mitigation:
- Implementation: Require developers to implement output encoding for all user-generated content displayed on a web page.
- Use Case: An e-commerce site allows users to leave product reviews. Properly encoding and escaping user inputs prevents malicious scripts from being executed in other users’ browsers.
Secure API Design:
- Implementation: Train developers to authenticate all API endpoints and avoid exposing sensitive information in API responses.
- Use Case: A mobile banking application uses APIs for account management. By enforcing token-based authentication for every API call, developers reduce the risk of unauthorized access.
Static Code Analysis in the Build Pipeline:
- Implementation: Incorporate tools into CI/CD pipelines to automatically scan for vulnerabilities during the build process.
- Use Case: A fintech company integrates static analysis tools to detect hardcoded credentials in their source code before deployment.
Threat Modeling in the Design Phase:
- Implementation: Use frameworks like STRIDE (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege) to assess threats during application design.
- Use Case: Before launching a customer portal, a SaaS company identifies potential abuse cases, such as session hijacking, and designs mitigations like secure session management.
Tools for Implementation:
- Static Code Analysis Tools: Use tools that can scan for known vulnerabilities in source code.
- Dynamic Application Security Testing (DAST): Use tools like Burp Suite or OWASP ZAP to simulate runtime attacks and identify vulnerabilities.
- Secure Frameworks: Recommend secure-by-default frameworks (e.g., Django for Python, Spring Security for Java) that enforce security best practices.
Mitigation guidance is from the MITRE ATT&CK course-of-action associated with this technique.
Related Software
- Linux Rabbit
- SeaDuke
- LP-Notes
- Kinsing
- Industroyer
- Dtrack
- Duqu
Software associations are from MITRE ATT&CK STIX relationships (observed usage, not attribution).
Related Threat Groups
- Indrik Spider
- BlackByte
- GALLIUM
- Volt Typhoon
- APT41
- Dragonfly
- menuPass
- FIN6
- FIN7
- Sandworm Team
- APT18
- Scattered Spider
Group associations are from MITRE ATT&CK STIX relationships.
Related Campaigns
- RedPenguin
- Operation MidnightEclipse
- 2015 Ukraine Electric Power Attack
- 3CX Supply Chain Attack
- Anthropic AI-orchestrated Campaign
- HomeLand Justice
- C0032
- SolarWinds Compromise
- Night Dragon
- Operation Wocao
- Leviathan Australian Intrusions
Campaign associations are from MITRE ATT&CK STIX relationships.
Related Content
References
Source Attribution
Source: MITRE ATT&CK (MITRE ATT&CK) · Confidence: 0.9 · Reviewed: OpenTrojan - Human Review
Start Investigation
Move from reading to investigating T1078 Valid Accounts. The workspace is a structured analysis surface — not a chat — organised as:
- Question — what do you need to know about T1078 Valid Accounts?
- Evidence — assertions mapped to verifiable references.
- Timeline — events in chronological order.
- Related Entities — CVE, threat actor, campaign, malware links.
- Sources — NVD, CISA KEV, MITRE ATT&CK, vendor advisories.
- Notes — your own observations and working hypotheses.
AI assistance is limited to summarising, explaining, and suggesting related evidence. AI never completes your investigation, modifies entity relationships, or generates facts — all published analysis stays human-reviewed.