NotC2 AWS AI C2
NotC2: AWS-Native AI C2 Proof of Concept
- Published
- 6 November 2026
- Added
- 10 November 2026, 15:14 UK
- Last updated
- 10 November 2026
Nothing to block2 to hunt11 behaviours to hunt
Hunt3 platforms
Run the hunt before you block, to find past activity. The same hunt is published for each platform. Preview and copy the queries in the dashboard.
- Defender XDRKQLDefender portal > Hunting > Advanced hunting. Paste and run over 30 days.Download hunt.kql
- SplunkSPLSearch & Reporting, last 30 days or more. Reads the CIM data models.Download hunt.spl
- Google SecOpsYARA-L 2.0Rules Editor. Paste, Retrohunt over 30 days, then turn on live mode.Download hunt.yaral
These queries can return false positives. Know your environment and confirm a hit before acting.
Summary
Proof-of-concept C2 built on AWS SQS, Lambda, SNS and Bedrock, with no network IOCs to block. NotC2 is a proof-of-concept command-and-control framework published by Varonis Threat Labs on 6 November 2026.
Do now
- Run the hunt.
- Check for the listed behaviours.
- Hunt CloudTrail for new or unexpected SQS-to-Lambda event source mappings (CreateEventSourceMapping)….
Indicators 2
| Value | Type | Action | Copy |
|---|---|---|---|
NotC2 | Other | monitor | |
execute_aws_operation | Other | monitor |
Sources Varonis
More detail
What to do
- Hunt CloudTrail for new or unexpected SQS-to-Lambda event source mappings (CreateEventSourceMapping), especially on queues or functions that are new or unused.
- Alert on Bedrock InvokeModel or Converse calls from a Lambda execution role that has not previously used Bedrock, particularly if the same role also starts calling unrelated AWS APIs.
- Investigate SNS HTTP or HTTPS subscriptions to external endpoints created by a Lambda execution role, and restrict who can create or modify those subscriptions to approved destinations.
- Enforce IAM least privilege so compromised identities cannot create queues and functions, pass powerful roles, invoke Bedrock or attach external SNS subscribers; enable CloudTrail data events and Bedrock model-invocation logging to correlate the full loop.
Behaviours to hunt 11
Behaviours are leads, not confirmed indicators, and can match legitimate activity. Compare any hit against your own baseline and environment before acting.
alert SNS subscription to an external HTTP(S) endpoint by a Lambda role
Look forSNS Subscribe with protocol http or https, made by a Lambda execution role (assumed-role session, often with exec-env/AWS_Lambda in the user agent)
Why it mattersThis is how NotC2 sends command output to the operator's server. Lambda functions rarely create new external subscriptions at runtime. Varonis
Log sourceCloudTrail management events (sns.amazonaws.com), or CloudAppEvents with the AWS connector
QueriesKQL · SPL · YARA-L
hunt SNS subscription confirmed for a new external endpoint
Look forSNS ConfirmSubscription for a new external HTTP or HTTPS endpoint
Why it mattersNotC2 only receives results once the operator's endpoint confirms the subscription. Record the confirmation's source address as a lead. Varonis
Log sourceCloudTrail management events (sns.amazonaws.com)
QueriesKQL · SPL
hunt SNS topic created by a Lambda role
Look forSNS CreateTopic called by a Lambda execution role
Why it mattersThe NotC2 function creates or resolves its results topic at runtime (create_topic). Application functions usually publish to topics that already exist. Varonis
Log sourceCloudTrail management events (sns.amazonaws.com)
QueriesKQL · SPL
alert New SQS-to-Lambda trigger
Look forNew SQS-to-Lambda event source mapping (CreateEventSourceMapping with an SQS queue ARN)
Why it mattersThe mapping is what makes each queued command run the function automatically. New mappings on new or unused queues and functions are unusual outside deployments. Varonis
Log sourceCloudTrail management events (lambda.amazonaws.com)
QueriesKQL · SPL · YARA-L
alert Queue, function and trigger created by one identity within an hour
Look forOne identity calling sqs:CreateQueue, lambda:CreateFunction and lambda:CreateEventSourceMapping within an hour
Why it mattersThese are the minimum deployment steps Varonis lists for NotC2 when a suitable Lambda role already exists (iam:PassRole is a permission check, not a separate event). Varonis
Log sourceCloudTrail management events
QueriesKQL · SPL
alert AWS resources named NotC2
Look forSQS queue named NotC2-Commands, or queue, function or topic names containing NotC2
Why it mattersNotC2-Commands is the command queue name in Varonis's published screenshots. The name is trivial to change, so a miss means little. Varonis
Log sourceCloudTrail management events (sqs CreateQueue requestParameters.queueName), AWS CLI command lines on endpoints
QueriesKQL · SPL · YARA-L
hunt First Bedrock use by a Lambda role
Look forBedrock InvokeModel, Converse or ConverseStream from a Lambda execution role that has not used Bedrock in the previous 30 days
Why it mattersBedrock is NotC2's command interpreter. Varonis calls out a sudden rise in Converse or InvokeModel calls from a Lambda role, especially one new to Bedrock. Varonis
Log sourceCloudTrail management events (bedrock.amazonaws.com)
QueriesKQL · SPL
hunt Lambda role calling Bedrock and discovery APIs together
Look forThe same Lambda role calling Bedrock and broad discovery APIs (ec2 DescribeInstances, dynamodb ListTables, rds DescribeDBInstances, lambda ListFunctions, s3 ListBuckets) in the same hour
Why it mattersVaronis shows NotC2 using Bedrock to enumerate EC2, DynamoDB, databases and Lambda functions; Bedrock use plus unrelated APIs from one role strengthens the signal. Varonis
Log sourceCloudTrail management events
QueriesKQL · SPL
alert Bedrock function named execute_aws_operation
Look forA Bedrock tool definition named execute_aws_operation, or prompts starting with "ai:"
Why it mattersNotC2 passes every AWS action through one generic tool, execute_aws_operation, with service, operation, parameters and region fields. Only model invocation logging records the request body. Varonis
Log sourceBedrock model invocation logs (CloudWatch Logs or S3); not in CloudTrail
QueriesSPL
hunt Lambda logs relaying commands through SNS
Look forLambda log lines "SNS message body:" followed by Command:, Target:, Exit Code:, Output: and Error: fields, or functions with SNS_TOPIC_ARN or SNS_TOPIC_NAME
Why it mattersThese strings appear in the NotC2 code in Varonis's screenshots. Default names are easy to change, so a match is a strong lead and a miss is no proof. Varonis
Log sourceLambda CloudWatch Logs and function configuration
QueriesSPL
hunt Full SQS to Lambda to Bedrock to SNS command chain
Look forAn SQS message from an unexpected source, then a Lambda run, Bedrock calls, other AWS API calls and an SNS publish to an external subscriber within minutes, all on the same queue, function and topic
Why it mattersEach event is normal on its own; Varonis says the sequence is the C2 loop. Data events are not logged by default and must be enabled first. Varonis
Log sourceCloudTrail data events (SQS, Lambda, SNS), SNS delivery-status logs, Bedrock invocation logs
QueriesNone yet: check by hand
Affected countries and sectors
- Targets
- Not stated
- Sectors
- Not stated
Background
NotC2 is a proof-of-concept command-and-control framework published by Varonis Threat Labs on 6 November 2026. It assumes the attacker already holds AWS credentials and runs the whole C2 loop on native AWS services: commands arrive through Amazon SQS, a Lambda function executes them, Amazon Bedrock translates natural-language prompts into AWS API calls through a generic tool named execute_aws_operation, and results leave through Amazon SNS to an external HTTPS endpoint. There is no conventional C2 server to block. Varonis has not reported in-the-wild use and published no network indicators. Detection depends on CloudTrail and related AWS logs: new SQS-to-Lambda event source mappings, unexpected Bedrock InvokeModel or Converse calls from Lambda roles, and SNS subscriptions to external endpoints.