feat: credit printnightmare technique after ares-cli #367 gate fix - #32
Merged
Merged
Conversation
…e fix **Changed:** - Moved `printnightmare` from `uncreditableCategories` to `creditableCategories`, allowing it to score as an exploit now that ares-cli dreadnode#367 rebuilt the detection gate on a single "exploit completed" marker the PoC actually prints - `transport_ares.go` - Rewrote the doc comment to scope the remaining refusal to `zerologon` only and explain the corrected rationale for `printnightmare`, whose old gate matched markers that never fired and thus scored zero rather than over-crediting - `transport_ares.go` - Updated tests to assert `printnightmare` now credits under its own technique ID and split the "refusals never credit" case to isolate `zerologon` from the newly credited `printnightmare` - `transport_ares_test.go`
l50
force-pushed
the
fix/credit-printnightmare-after-ares-gate-fix
branch
from
July 30, 2026 18:19
b88f54d to
709d45d
Compare
l50
changed the title
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.
Key Changes:
printnightmarecategory now that ares-cli chore(deps): update terraform aws to v6.55.0 dreadnode/DreadGOAD#367 rebuilt its detection gate on a marker the PoC actually printsprintnightmarefrom the uncreditable refusal list to the creditable categories mapAdded:
printnightmarecategory - AddedprintnightmaretocreditableCategoriesso the technique is scored like any other exploit -transport_ares.goprintnightmarecredits after ares chore(deps): update terraform aws to v6.55.0 dreadnode/DreadGOAD#367, including a dedicatedprintnightmare credits after ares gate fixtoken coverage case -transport_ares_test.goChanged:
printnightmarerefusal was based on a faulty mechanism (a gate matching markers the PoC never printed), corrected by ares-cli chore(deps): update terraform aws to v6.55.0 dreadnode/DreadGOAD#367, and narrowed the remaining refusal rationale tozerologonalone -transport_ares.goTestUncreditableCategoriesAreDeliberate,TestDetectTokenCoverageDrift, and theAresCategoryToTechniqueIDrefusal cases to expect onlyzerologon(plusotherandgolden_ticket) as deliberate refusals -transport_ares_test.goRemoved:
printnightmarerefusal entry - Removedprintnightmarefrom theuncreditableCategoriesmap and its associated refusal test assertions, since the category now credits correctly -transport_ares.go,transport_ares_test.go