Repository navigation
Conversation
Contributor
Coverage Report •
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This branch has not been deployed
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.
Coruna's randomized preference filenames and app-container
Documents/.devcacheartifacts are missed by static filename indicators. Add scoped checks to Manifest and Filesystem, with medium-severity path findings and high-severity findings when the published content structure matches. Correlate matching device-identifier fingerprints across distinct application containers without exporting the raw identifiers or tracked photo path.Map known backup domains to device paths, handle iOS path aliases and Windows separators, and require a directory boundary when matching path indicators. When
--hashesorHASH_FILESis enabled, store and check file SHA-256 values in module results so payload hash IOCs provide detection coverage and saved results can be rechecked. Content reads are bounded for artifact inspection and confined to regular files within the acquisition.The artifact definitions come from iVerify's September 2026 Coruna/DarkSword report. Path-only findings remain distinct from corroborated content matches and confirmed hash IOCs.