Unsecured Credentials: Chat Messages
- ID
- T1552.008
- Tactics
- TA0006 Credential Access
- Sub-technique of
- T1552 Unsecured Credentials
- Platforms
- SaaS, Office Suite
- Data sources
- Application Log Content, User Account Authentication
- Source
- attack.mitre.org
- MITRE last modified
- 16 Apr 2025
Adversaries may directly collect unsecured credentials stored or passed through user communication services. Credentials may be sent and stored in user chat communication applications such as email, chat services like Slack or Teams, collaboration tools like Jira or Trello, and any other services that support user communication. Users may share various forms of credentials (such as usernames and passwords, API keys, or authentication tokens) on private or public corporate internal communications channels.
Rather than accessing the stored chat logs (i.e., Credentials In Files), adversaries may directly access credentials within these services on the user endpoint, through servers hosting the services, or through administrator portals for cloud hosted services. Adversaries may also compromise integration tools like Slack Workflows to automatically search through messages to extract user credentials. These credentials may then be abused to perform follow-on activities such as lateral movement or privilege escalation [1].
Detection
- DET0111 Detect Unsecured Credentials Shared in Chat Messages
Data components: Application Log Content, User Account Authentication
Mitigations (2)
- M1017 User Training
Ensure that developers and system administrators are aware of the risk associated with sharing unsecured passwords across communication services.
- M1047 Audit
Preemptively search through communication services to find shared unsecured credentials. Searching for common patterns like "
password is", “password=” and take actions to reduce exposure when found.
