AWS IAM Backdoor Users Keys
Detects AWS API key creation for a user by another user. Backdoored users can be used to obtain persistence in the AWS environment. Also with this alert, you can detect a flow of AWS keys in your org.
Detection logic
selection
eventSource: iam.amazonaws.com
eventName: CreateAccessKeyfilter_main_same_user
userIdentity.arn|fieldref|contains: responseElements.accessKey.userNameCondition
selection and not 1 of filter_main_*Raw YAML
title: AWS IAM Backdoor Users Keys
id: 0a5177f4-6ca9-44c2-aacf-d3f3d8b6e4d2
status: test
description: |
Detects AWS API key creation for a user by another user.
Backdoored users can be used to obtain persistence in the AWS environment.
Also with this alert, you can detect a flow of AWS keys in your org.
references:
- https://github.com/RhinoSecurityLabs/pacu/blob/866376cd711666c775bbfcde0524c817f2c5b181/pacu/modules/iam__backdoor_users_keys/main.py
- https://github.com/SigmaHQ/sigma/issues/6223
author: faloker
date: 2020-02-12
modified: 2026-08-14
tags:
- attack.persistence
- attack.privilege-escalation
- attack.t1098
logsource:
product: aws
service: cloudtrail
detection:
selection:
eventSource: iam.amazonaws.com
eventName: CreateAccessKey
filter_main_same_user:
userIdentity.arn|fieldref|contains: responseElements.accessKey.userName
condition: selection and not 1 of filter_main_*
falsepositives:
- Adding user keys to their own accounts (the filter cannot cover all possible variants of user naming)
- AWS API keys legitimate exchange workflows
level: mediumFalse positives
- Adding user keys to their own accounts (the filter cannot cover all possible variants of user naming)
- AWS API keys legitimate exchange workflows