Skip to content

Detection: Microsoft Intune Bulk Wipe Detected#3978

Open
jakeenea51 wants to merge 2 commits intosplunk:developfrom
jakeenea51:develop
Open

Detection: Microsoft Intune Bulk Wipe Detected#3978
jakeenea51 wants to merge 2 commits intosplunk:developfrom
jakeenea51:develop

Conversation

@jakeenea51
Copy link
Copy Markdown
Contributor

Details

Contributing 1 new detection:

  • Microsoft Intune Bulk Wipe Detected

Details:

  • Inspired by the recent Stryker incident involving a compromised Intune admin account being used to bulk wipe thousands of endpoints
  • Currently set to a threshold of >= 5 wipe actions/hour
  • I will be opening a separate PR on the attack_data repo to upload the associated test dataset

This is my first time contributing a detection, so let me know if I missed anything or if any information should be changed. Thanks!

Checklist

  • Validate name matches <platform>_<mitre att&ck technique>_<short description> nomenclature
  • CI/CD jobs passed ✔️
  • Validated SPL logic.
  • Validated tags, description, and how to implement.
  • Verified references match analytic.
  • Confirm updates to lookups are handled properly.

Notes For Submitters and Reviewers

  • If you're submitting a PR from a fork, ensuring the box to allow updates from maintainers is checked will help speed up the process of getting it merged.
  • Checking the output of the build CI job when it fails will likely show an error about what is failing. You may have a very descriptive error of the specific field(s) in the specific file(s) that is causing an issue. In some cases, its also possible there is an issue with the YAML. Many of these can be caught with the pre-commit hooks if you set them up. These errors will be less descriptive as to what exactly is wrong, but will give you a column and row position in a specific file where the YAML processing breaks. If you're having trouble with this, feel free to add a comment to your PR tagging one of the maintainers and we'll be happy to help troubleshoot it.
  • Updates to existing lookup files can be tricky, because of how Splunk handles application updates and the differences between existing lookup files being updated vs new lookups. You can read more here but the short version is that any changes to lookup files need to bump the the date and version in the associated YAML file.

@@ -0,0 +1,61 @@
name: Microsoft Intune Bulk Wipe Detected
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jakeenea51 - can you Install pre-commit using pip install pre-commit then proceed to installing the hooks via pre-commit install. this is a pre-requisite to validate and apply the proper formatting.

| rename identity as user, resultType as result
| table _time user tenantId signature result vendor_account vendor_product
| fillnull
| stats min(_time) as firstTime max(_time) as lastTime values(*) as * count by _time signature user tenantId vendor_account vendor_product
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we not get any src related info from the search, it will be good to add that to the output and to the threat object

risk_objects:
- field: user
type: user
score: 80
Copy link
Copy Markdown
Contributor

@patel-bhavin patel-bhavin Mar 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

since this is a TTP detection, lets keep this score to 50. We havent enforced this in CI yet but soon will be enforcing this in our checks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants