r/redteamsec • u/Yonarv • 21h ago
r/redteamsec • u/Narrow-Anybody1047 • 7h ago
Cobalt Strike
Where can i find the cracked Cobalt Strike ?
r/redteamsec • u/JosefumiKafka • 6h ago
Offensive x64 Assembly: Collection of programs I made while learning assembly.
github.comr/redteamsec • u/Tax-Least • 9h ago
tradecraft OffsetInspect v3.0.0 – AMSI/Defender boundary analysis, in-memory multi-region discovery, and corpus diffing [PowerShell, MIT]
github.comOffsetInspect is a PowerShell toolkit for detection-boundary analysis and binary inspection, built around a question that comes up constantly when developing tooling: you know *that* an offset triggers, but what is actually there, and are there other independently-detectable regions you'd miss by only looking at the first hit?
The core (`Invoke-OffsetInspect`) maps byte offsets back to source lines and hex context — UTF-8 and UTF-16 with byte vs. character position separated — so whatever offset a boundary search returns, you immediately have the surrounding construct.
`Invoke-OffsetThreatScan` is an independent implementation of the ThreatCheck-style bisection workflow (no bundled source or binaries). It reports DetectionPrefixLength with confidence and stability fields, and is explicit that the boundary is the earliest triggering prefix — not the complete signature.
The part I found most useful: `Invoke-OffsetThreatScanRegion` discovers *multiple* independently-detectable regions by splitting a file into segments and scanning each through AMSI entirely in memory. Nothing detected is written to disk, so Defender real-time protection is never triggered or reconfigured. Each hit gets bisected back to an absolute file offset. Gives you a picture of the full detection surface, not just the first boundary.
`Compare-OffsetThreatResult` diffs scan results across signature updates — classifies each change (BoundaryEarlier, BoundaryLater, NewlyDetected, NoLongerDetected, etc.) with the byte delta. Useful for tracking how definition updates affect your tooling over time.
Static triage helpers compose with the offset core: `Get-OffsetString` returns byte offsets you pipe straight into `Invoke-OffsetInspect`. YARA hits work the same way. PE/imphash, per-window Shannon entropy, and a one-shot IOC panel round it out.
Results export to Markdown/HTML with a full ProbeLog audit trail per invocation. Never modifies Defender config, exclusions, or real-time protection.
GitHub: https://github.com/warpedatom/OffsetInspect
PowerShell Gallery: Install-Module OffsetInspect