SharpCollection Documentation

repository·master·Indexed 25 days ago

https://github.com/flangvik/sharpcollection

A repository of nightly builds for common C# offensive security tools, automated via Azure DevOps pipelines. It provides binaries compiled from master branches for various .NET Framework versions, including specific targets for tools like ADCollector, Certify, and KrbRelay.

Tokens
437
Snippets
0
Records
3
Agent score
34%

What's inside SharpCollection

  1. Overview of SharpCollection

    master

    SharpCollection provides nightly builds of common C# offensive tools. These tools are compiled from their respective master branches using Azure DevOps release pipelines in a Continuous Deployment (CDI) fashion.

    Important Compatibility Note: If you are using Cobalt Strike's execute-assembly, note that it only accepts binaries compiled with the "Any CPU" configuration.

  2. Operational Security (OpSec) Warnings

    master

    ⚠️ Critical Security Warning

    Do not blindly deploy any binaries from this repository during real-life engagements.

    Always inspect any binary you deploy on a client machine or network (e.g., using tools like dnSpyEx).

    Recommended Use Cases:

    • Lab environments
    • Virtual Machines (VMs)
    • HackTheBox
    • Detection mapping
  3. Build Availability and Framework Targets

    master

    SharpCollection provides builds for various .NET Framework versions. When selecting a tool, verify its target framework and architecture requirements.

    Framework Version Constraints

    Some tools target specific versions regardless of the general availability table:

    • ADCollector: Targets v4.6.1.
    • Certify, KrbRelay, KrbRelayUp, ShadowSpray: Target v4.7.2.

    Architecture and Build Notes

    • AtYourService, Evasor: Do not have AnyCPU builds; they only provide x64/x86 platforms.
    • SharpBlock: Only builds for NET 4.0 and NET 4.5 (NET 4.7 steps are disabled). Does not support AnyCPU (x64/x86 only).
    • SharpDoor: Only publishes x64 binaries.
    • Scout: Binaries are outdated and no longer maintained as the original repository has been removed.
    • SharpSystemTriggers: The pipeline is currently paused; existing binaries may be outdated.
    • InveighZero: The pipeline is non-functional (all build steps disabled); existing binaries are from previous builds.