Add Darkmoon (autonomous pentest platform) to Azure Recon Tools - #2
Open
MBK-fr wants to merge 1 commit into
Open
Add Darkmoon (autonomous pentest platform) to Azure Recon Tools#2MBK-fr wants to merge 1 commit into
MBK-fr wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds one entry to the Azure Recon Tools list for Darkmoon, an open source (GPLv3) autonomous penetration testing platform.
Why it fits this repo's users: this section already curates third party offensive Azure tooling (ROADtool, StormSpotter, AzureHound, MicroBurst, PowerZure, SkyArk). Darkmoon runs 50 specialist agents over MCP driving 50+ offensive tools across web, API, Active Directory, Kubernetes and cloud, and returns proof of exploitation behind each finding, so it maps directly to the cloud and Azure AD attack paths documented throughout this repository. It is self hosted, and its privacy gateway tokenizes sensitive target values before any cloud model sees them, which matters for red teamers operating under engagement scope and data handling rules.
The change is a single bullet in the existing format, no other files touched.
Disclosure: I contribute to Darkmoon. I am proposing this because it directly supports this repository's documented use case, and I am happy to adjust or withdraw it if maintainers consider it out of scope.