Repository navigation
new: [import_mod] Darkmoon JSON findings import module - #912
Merged
Merged
Conversation
Author
|
The |
Member
|
Thank you! |
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
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.
Adds an import module for the JSON findings of Darkmoon, an open source (GPL-3.0) autonomous AI penetration testing platform. An LLM orchestrates specialist agents and offensive tools and tries to prove each finding with a real exploit; the open source CLI writes a JSON findings report.
What it does
import_mod/darkmoon_import.pyfollows the usual import module layout (handler,introspection,version,misp_standardoutput) and turns the report into MISP objects:titlevulnerabilityobject,summarydescription,remediation,evidence_explanation,evidence_commands,evidence_logs,raw_request,raw_responsevulnerabilitydescriptioncvevulnerabilityidand NVD referencecvss_score,cvss_vectorcvss-score,cvss-stringmitre_attack_idmisp-galaxy:mitre-attack-patterntag when the technique name is presentseverity,status(exploited / confirmed / unconfirmed),category,discovered_by_agentdarkmoon:*tagsendpointurlobject, with avulnerabilityaffectsurlreferenceOne user option (
include_unconfirmed) skips findings whose exploitation could not be confirmed. A bare list and{"findings": [...]}are both accepted. Input is rejected with a clear error unless every finding carries a title,discovered_by_agentand a Darkmoon exploitation status, so other JSON files (for example a Gitleaks-stylefindingslist) are not misread.Tests
tests/test_darkmoon_import.py(pytest, same style astest_cuckooimport.py) withtests/darkmoon_findings.json(exploited, confirmed and unconfirmed findings, with and without CVE / CVSS vector). 5 passed locally with PyMISP;black -l 120andflake8 --max-line-length 120are clean. Modules are auto-discovered, so no registration is needed, and the docs page is generated at release.Scope: the module only reads the JSON file the open source CLI writes. No Darkmoon API or dashboard is involved.
Link to tool: https://github.com/ASCIT31/Dark-Moon
🤖 Generated with Claude Code
https://claude.ai/code/session_014HBQNzAf5C2E3MiJC48HQw