Skip to content

New attack technique: Delete All GCS Objects in Batch (gcp.impact.ransomware-gcs-batch-deletion)#804

Open
Minosity-VR wants to merge 3 commits into
simon.marechal/gcp-impact-invoke-vertex-ai-modelfrom
simon.marechal/gcp-impact-ransomware-gcs-batch-deletion
Open

New attack technique: Delete All GCS Objects in Batch (gcp.impact.ransomware-gcs-batch-deletion)#804
Minosity-VR wants to merge 3 commits into
simon.marechal/gcp-impact-invoke-vertex-ai-modelfrom
simon.marechal/gcp-impact-ransomware-gcs-batch-deletion

Conversation

@Minosity-VR

Copy link
Copy Markdown
Collaborator

What does this PR do?

Adds a new GCP attack technique gcp.impact.ransomware-gcs-batch-deletion that simulates a ransomware attack by concurrently deleting all objects in a GCS bucket and uploading a ransom note.

Motivation

GCP parity effort with existing AWS techniques (analogous to aws.impact.s3-ransomware-batch-deletion).

Checklist

  • The attack technique emulates a single attack step, not a full attack chain
  • We have factual evidence & references that the attack technique was used by real malware, pentesters, or attackers
  • The attack technique makes no assumption about the state of the environment prior to warming it up

Test results

  • Technique detonates successfully
  • Detection log identified (storage.objects.delete) — there is no audit log emitted for GCS object deletions without non-default Data Access audit log configuration; a burst-based detection would yield too many false positives given typical GCS usage at scale

@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-impact-invoke-vertex-ai-model branch from ce449a2 to 43077e4 Compare March 30, 2026 14:54
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-impact-ransomware-gcs-batch-deletion branch from 1abe77e to 24d6c78 Compare March 30, 2026 14:54
@Minosity-VR Minosity-VR marked this pull request as ready for review April 1, 2026 07:25
@Minosity-VR Minosity-VR requested review from a team as code owners April 1, 2026 07:25
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-impact-invoke-vertex-ai-model branch from 43077e4 to 9c7f9ff Compare April 1, 2026 08:28
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-impact-ransomware-gcs-batch-deletion branch from 24d6c78 to cef4be3 Compare April 1, 2026 08:29
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-impact-invoke-vertex-ai-model branch from 9c7f9ff to 0575fcb Compare April 1, 2026 08:53
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-impact-ransomware-gcs-batch-deletion branch from cef4be3 to 643d9d7 Compare April 1, 2026 08:53
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-impact-invoke-vertex-ai-model branch from 0575fcb to 0bd7fea Compare April 1, 2026 09:04
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-impact-ransomware-gcs-batch-deletion branch from 643d9d7 to ebeb6e5 Compare April 1, 2026 09:04
Minosity-VR and others added 3 commits April 9, 2026 10:10
…somware-gcs-batch-deletion)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-impact-invoke-vertex-ai-model branch from 0bd7fea to 4c60a98 Compare April 9, 2026 08:28
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-impact-ransomware-gcs-batch-deletion branch from ebeb6e5 to 18e15e7 Compare April 9, 2026 08:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant