Skip to content

New attack technique: Backdoor a Cloud Function (gcp.persistence.backdoor-cloud-function)#807

Open
Minosity-VR wants to merge 3 commits into
simon.marechal/gcp-impact-ransomware-gcs-individual-deletionfrom
simon.marechal/gcp-persistence-backdoor-cloud-function
Open

New attack technique: Backdoor a Cloud Function (gcp.persistence.backdoor-cloud-function)#807
Minosity-VR wants to merge 3 commits into
simon.marechal/gcp-impact-ransomware-gcs-individual-deletionfrom
simon.marechal/gcp-persistence-backdoor-cloud-function

Conversation

@Minosity-VR

Copy link
Copy Markdown
Collaborator

What does this PR do?

Adds a new GCP attack technique gcp.persistence.backdoor-cloud-function that grants unauthenticated invocation access to a Cloud Functions v2 function by adding an allUsers IAM binding on both the function and the underlying Cloud Run service.

Motivation

GCP parity effort with existing AWS techniques (analogous to aws.persistence.lambda-backdoor-function).

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 (google.cloud.functions.v2.CloudFunctionsService.SetIamPolicy and google.cloud.run.v2.Services.SetIamPolicy with allUsers binding) — note that organization-level policies can prevent public access while still generating the audit log

@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-impact-ransomware-gcs-individual-deletion branch from e1f393d to f57a647 Compare March 30, 2026 14:54
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-persistence-backdoor-cloud-function branch from c3fbc21 to be166ae 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-ransomware-gcs-individual-deletion branch from f57a647 to 807d3ee Compare April 1, 2026 08:29
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-persistence-backdoor-cloud-function branch from be166ae to 65f501d Compare April 1, 2026 08:29
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-impact-ransomware-gcs-individual-deletion branch from 807d3ee to 2a8cd64 Compare April 1, 2026 08:53
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-persistence-backdoor-cloud-function branch from 65f501d to 10a401f Compare April 1, 2026 08:54
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-impact-ransomware-gcs-individual-deletion branch from 2a8cd64 to af6b6d6 Compare April 1, 2026 09:04
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-persistence-backdoor-cloud-function branch from 10a401f to a370532 Compare April 1, 2026 09:04
Minosity-VR and others added 3 commits April 9, 2026 10:22
…door-cloud-function)

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-ransomware-gcs-individual-deletion branch from af6b6d6 to fc57a54 Compare April 9, 2026 08:28
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-persistence-backdoor-cloud-function branch from a370532 to 3a0ae74 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