FORENSIA

ATT&CK · T1528

Steal Application Access Token

Tactics: credential-access

About

Adversaries can steal application access tokens as a means of acquiring credentials to access remote systems and resources. Application access tokens are used to make authorized API requests on behalf of a user or service and are commonly used as a way to access resources in cloud and container-based applications and software-as-a-service (SaaS). Adversaries who steal account API tokens in cloud and containerized environments may be able to access data and perform actions with the permissions of these accounts, which can lead to privilege escalation and further compromise of the environment. For example, in Kubernetes environments, processes running inside a container may communicate with the Kubernetes API server using service account tokens. If a container is compromised, an adversary may be able to steal the container’s token and thereby gain access to Kubernetes API commands. Similarly, instances within continuous-development / continuous-integration (CI/CD) pipelines will often use API tokens to authenticate to other services for testing and deployment. If these pipelines are compromised, adversaries may be able to steal these tokens and leverage their privileges. In Azure, an adversary who compromises a resource with an attached Managed Identity, such as an Azure VM, can request short-lived tokens through the Azure Instance Metadata Service (IMDS). These tokens can then facilitate unauthorized actions or further access to other Azure services, bypassing typical credential-based authentication. Token theft can also occur through social engineering, in which case user action may be required to grant access. OAuth is one commonly implemented framework that issues tokens to users for access to systems. An application desiring access to cloud-based services or protected APIs can gain entry using OAuth 2.0 through a variety of authorization protocols. An example commonly-used sequence is Microsoft's Authorization Code Grant flow. An OAuth access token enables a third-party application to interact with resources containing user data in the ways requested by the application without obtaining user credentials. Adversaries can leverage OAuth authorization by constructing a malicious application designed to be granted access to resources with the target user's OAuth token. The adversary will need to complete registration of their application with the authorization server, for example Microsoft Identity Platform using Azure Portal, the Visual Studio IDE, the command-line interface, PowerShell, or REST API calls. Then, they can send a Spearphishing Link to the target user to entice them to grant access to the application. Once the OAuth access token is granted, the application can gain potentially long-term access to features of the user account through Application Access Token. Application access tokens may function within a limited lifetime, limiting how long an adversary can utilize the stolen token. However, in some cases, adversaries can also steal application refresh tokens, allowing them to obtain new access tokens without prompting the user.

Platforms: Containers, IaaS, Identity Provider, Office Suite, SaaSMITRE ATT&CK ↗

Used by actors

2 known groups

Software

4 malware/tools implement this

AADInternalsPeiratesShai-HuludTruffleHog

Corpus indicators tagged with this technique

236 indicators in the corpus carry T1528.

IndicatorTypeFamilySevSrc
6894a51278ec89118276c2dd2dc36e6f9ea2790ahashphishing802
103c4e6181151c1bcfedc41506cd1815458c38375d08a8fcd9981dbe0b965ce0sha256supply_chain801
9a59eb454f3ca3fe91214136ee5edd417cc47a80e6f169b52099d6561944baf9sha256supply_chain801
7f30259d72eb7432b2454c07be83365ecfa835188185b35b30d11654aadf86a0sha256phishing803
febb622cd9eeb5c8860dcef4cbfd4b74hashphishing802
ec7b0bc82c00464d8e0a59bc19c585e2hashphishing801
bba32ddeab075a5e5015eec50f5d2af364c95b848732c714aea6b6baf78f49f0sha256supply_chain801
c8cb3f6d5b90c46686d2bf531dc1a5786e27edc5sha1supply_chain781
22bf76fe317ea6769bd38619bd440e42d119bd6bsha1supply_chain781
ea5d2096a2ef3dfe4fb870bd1f0270efaea993a6sha1phishing783
87867ad29e621bf9ebf57e1757f75090842458besha1781
eb8ede7598220dbef28953dc7df2e5418d52fa36sha1phishing783
a7e18d96efd3cdb127ef4cdcad9e3ad26c482bf2sha1supply_chain781
c70e105e212ff3c1daa04bb2a62507717f296b0bsha1supply_chain782
5f3f99b14243404c7cf57b40bb101244cce394bfsha1781
32d0c3300825b0bb991c4a8f1e6244f0ad2da989sha1781
f496736e2d2344de7963d4f722381f03227ec452sha1phishing783
11a42ef076686cb27ba2c8845301943652a5aadcsha1781
38d744543b2051e6f749af171b5ef8d6df8aac7bsha1781
cf3cbf93adf43d50618c88705857d3adb123ed24sha1phishing783
09002d4668a778853e8da5c488c6e421c0628357sha1781
e9a44b3fe951cca57313533d6bc1d11e789c2018sha1phishing783
2ea61cdead470f570586f513e22d43d787befec6sha1phishing783
ff8d2afd9d7f0a828592fee34ca55d1a3542f7edsha1781
b4101027bf2f1261402bf6318c6eb016ce249037sha1781
6a4cb1c75e1c59bbd4fbc4667f4c3bb5a74fe965sha1phishing783
c0e178d26e1e67985a9c67e649d71d54642e0eedsha1781
9890950adcbc2478e7a080234f053214adbad44esha1supply_chain781
f61e3a643f2417e1a1ab2c83bbdbfc8a7cb96756sha1781
35f23dfb4135d4cd38a6a29e64d79191d166344dsha1phishing783

Showing the top 30 by severity of 236.