Implant Internal Image T1525

Tactic: Persistence

Adversaries may implant cloud or container images with malicious code to establish persistence after gaining access to an environment. Amazon Web Services (AWS) Amazon Machine Images (AMIs), Google Cloud Platform (GCP) Images, and Azure Images as well as popular container runtimes such as Docker can be implanted or backdoored. Unlike Upload Malware, this technique focuses on adversaries implanting an image in a registry within a victim’s environment. Depending on how the infrastructure is provisioned, this could provide persistent access if the infrastructure provisioning tool is instructed to always use the latest image.

Authoring guide

Patterns shared across the 5 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (10 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

FieldRulesHowSample values
aws::eventName3in 2, eq 1AddPermission, BatchCheckLayerAvailability, BatchDeleteImage, BatchGetImage, CreateAlias
aws::eventSource3eq 3ecr.amazonaws.com, ecs.amazonaws.com, lambda.amazonaws.com
EventType1in 1CreateCustomModelDeployment, CreateMarketplaceModelEndpoint, CreateModelImportJob
Provider_Name1eq 1bedrock.amazonaws.com
data_stream.dataset1eq 1aws.cloudtrail
event.outcome1eq 1success
namespace1in 1gke-system, kube-node-lease, kube-public
requestParameters.containerDefinitions.command1contains 1$aws_container_credentials_relative_uri
subresource1is_null 1
username1contains 1serviceaccount

Top indicator values (46 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.

FieldKindValueRules (here)Corpus reach
EventTypein
CreateCustomModelDeployment
1
EventTypein
CreateMarketplaceModelEndpoint
1
EventTypein
CreateModelImportJob
1
EventTypein
RegisterMarketplaceModelEndpoint
1
Provider_Nameeq
bedrock.amazonaws.com
115
aws::eventNameeq
DescribeTaskDefinition
1
aws::eventNameeq
RegisterTaskDefinition
1
aws::eventNameeq
RunTask
1
aws::eventNamein
AddPermission
1
aws::eventNamein
BatchCheckLayerAvailability
1
aws::eventNamein
BatchDeleteImage
1
aws::eventNamein
BatchGetImage
1
aws::eventNamein
CompleteLayerUpload
1
aws::eventNamein
CreateAlias
1
aws::eventNamein
CreateEventSourceMapping
1
aws::eventNamein
CreateFunction
1
aws::eventNamein
CreateRepository
1
aws::eventNamein
DeleteAlias
1
aws::eventNamein
DeleteEventSourceMapping
1
aws::eventNamein
DeleteFunction
1
aws::eventNamein
DeleteRepository
1
aws::eventNamein
DeleteRepositoryPolicy
1
aws::eventNamein
GetAuthorizationToken
1
aws::eventNamein
GetDownloadUrlForLayer
1
aws::eventNamein
GetRepositoryPolicy
1
aws::eventNamein
InitiateLayerUpload
1
aws::eventNamein
PublishVersion
1
aws::eventNamein
PutImage
1
aws::eventNamein
RemovePermission
1
aws::eventNamein
SetRepositoryPolicy
1

Exclusions (9 distinct)

Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.

FieldKindValueRules excluding
aws::userIdentity.arnends_with
DeployRole
2
resourcene
pods
1
responseStatus.codege
1
1
responseStatus.codege
400
1
responseStatus.codele
16
1
usernamein
aksService
1
usernamein
masterclient
1
usernamestarts_with
system:
1
verbne
create
1

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Platform (all)
Domain (all)

Sigma 1 rule

Elastic 1 rule

Panther 3 rules