r/redteamsec • u/ElectrodeGuy1337 • 4h ago
Sentinels: host intrusion detection and response for automated attacks
r/redteamsec • u/ElectrodeGuy1337 • 4h ago
r/redteamsec • u/bgbe_ • 4h ago
If you sell B2B, the enterprise security questionnaire arrives sooner or later. It usually asks for a recent pentest, vulnerability scan results, an SBOM, and proof that critical findings were fixed. Many small teams get stuck right there because a manual pentest costs thousands of dollars and takes weeks to schedule.
I built a tool that covers this workflow, and I'm offering free runs to a few teams in exchange for feedback:
* **Scan:** Checks your code, dependencies, secrets, IaC, and container images. You get a full findings report plus an SBOM.
* **Automated Red Team:** Runs against a staging copy of your app and actually tries to exploit what it found. Vulnerability classes like XSS, open redirects, and boolean-blind SQLi get a live PoC. Each finding is marked **Verified** or **Not Verified**—not just a noisy list of theoretical CVEs.
* **AI Agent Testing:** If you ship an AI agent (chat, tool-calling, MCP, or one that reads emails), it attacks it like a real user would—testing for prompt injection, system-prompt leakage, and poisoned inputs (like an email trying to make the agent leak a planted canary token).
* **Fix Proof:** After you patch the issues, it re-runs the exploits and generates a before-and-after verification report you can hand directly to your customer's security team.
### What this is NOT (setting clear expectations)
* **Not a compliance certification:** This won't replace SOC 2 or ISO 27001 controls. If a customer or auditor strictly mandates a certified human pentest, this gets you early evidence and cleans up your app beforehand, rather than replacing a formal audit.
* **Early-stage AI agent coverage:** The AI-agent red-teaming is currently validated against reference vulnerable and hardened agents I built, rather than hundreds of production agents in the wild. That's a big reason I'm looking for early testers.
### Ground Rules
To keep everything safe and strictly above board: I only test assets you own, on a **staging environment**, with written authorization. I will not run anything against a live production app or third-party systems.
**The Offer:** Opening up **[X] free slots**. If you want in, drop a comment, DM me. In return, all I ask for is blunt feedback on what the report got wrong (or missed), and a one-line quote if it helped you unblock a deal.
Ask me anything—especially about where it's weak or how the verification works under the hood.
r/redteamsec • u/nanaynunay • 9h ago
hi, this is my new research repo, support pls
r/redteamsec • u/nanaynunay • 9h ago
hi, this is my new research repo, support pls
r/redteamsec • u/ROUNAK316 • 12h ago
r/redteamsec • u/Designer-Classic3925 • 16h ago
Hey everyone,
I've been working on an open source project called The Hacking Machine, and I finally feel it's in good enough shape to share.
The idea is simple. Each lab is a deliberately vulnerable machine built around one real CVE, and the whole thing is set up with Ansible. You spin up a fresh Ubuntu VM, run a playbook, and you get a vulnerable target to attack. Nothing exploits it for you. The build only deploys the vulnerable service, and the actual hacking is up to you. Revert the VM to a clean snapshot and you can build a different lab on the same box.
I made it because I wanted practice that felt like the OSCP: find the service, figure out what's wrong, and exploit it yourself, instead of following a walkthrough that does everything in one click. It also helps that you can read the playbooks and see exactly how the vulnerable setup was put together, which is useful when you want to understand why something is exploitable and not just that it is.
Some of the labs so far cover things like Log4Shell and React2Shell, and I'm adding more regularly. New machines are in development right now, so there will be more to try soon. I'm also preparing for my OSCP exam at the moment, so I'll start adding more CVEs in bulk once that is done.
Links:
Website: https://thehackingmachine.com/
Get started guide: https://thehackingmachine.com/get-started/01
If you try it out, I'd really like to hear what worked, what broke, and which CVEs or machine types you'd want to see next. Issues and PRs on GitHub are welcome too. A star helps others find it if you think it's useful.
Please only run these on your own isolated VMs, since they are intentionally vulnerable.
One more thing: this project is sponsored by my employer, Askar Labs. They gave me the time and support to build it and keep it open source, so a big thank you to them. It wouldn't exist without that.
Thanks
r/redteamsec • u/jdefr • 1d ago
r/redteamsec • u/RubberDuck31337 • 2d ago
Part 4 of my Win x64 shellcode development series.
This one is about the ABI mechanics behind shellcode stability -
calling convention, shadow space, and stack alignment. The kind
of stuff that makes your shellcode work in a test harness but
crash unpredictably when injected into a real process.
Key topics:
- Shadow space: 32 bytes the caller allocates but the callee owns
- Stack alignment bug specific to shellcode (and rsp without saving
RSP = silent crash on ret)
- Full shellcode example: calc.exe via WinExec, PEB traversal,
ROR13 hash resolution
- WinDbg walkthrough showing the actual structures and stack layout
r/redteamsec • u/gerard0_b4r0n • 2d ago
r/redteamsec • u/wtfse • 3d ago
r/redteamsec • u/BenTheCyberOne • 4d ago
I've been building CopperHound, an alternative to BloodHound for large environments. It reads the collector output you already have (SharpHound, bloodhound-python, AzureHound, ldapdomaindump), plus raw LDIF dumps and AD Explorer snapshots. Everything goes into a memory-mapped graph store, with no graph database behind it. This makes it exponentially more faster for querying larger datasets or enterprise-wide collections. I vibed/built this out of necessity given current constraints with the BH CE , and figured someone else might have similar use cases.
- Fast on big data: a 10 GB SharpHound collection (12.5M objects, 65.7M edges) ingests in about 25 seconds. A shortest path to Tier Zero on that graph takes under 1 ms.
- Queries: CHQL is a read-only Cypher dialect, so most BloodHound CE queries run unchanged. It ships with 159 prebuilt queries.
- Findings: 30 finding types across AD, ADCS (ESC1–ESC15), Entra ID and hybrid setups. Each one shows how many principals lose their path to Tier Zero if you fix it.
- Remediation planner: a step-by-step fix plan, a what-if simulator, and hand-off to PowerShell, Jira or ServiceNow.
- Over time: posture is tracked across ingests, with change alerts to Slack, Teams, email or a webhook.
- Deployment: one Docker container for the web UI, the REST API and SSO (OIDC and SAML).
Feedback, bug reports and PRs are welcome!
r/redteamsec • u/elohhs • 5d ago
A while back, I had released a blog showing that NTLMv1 downgrade attacks still work on Windows Server 2022! While it isn't a default setting, it's still a misconfiguration to potentially look for.
If a DC’s LmCompatibilityLevel is set to 0-2, you can coerce authentication, strip Extended Session Security (ESS), and obtain an NTLMv1-SSP hash that’s crackable with a rainbow table. :)
r/redteamsec • u/lymn • 5d ago
On November 2nd, researcher Colsto dropped a video proving you can geolocate raw audio down to a specific riverbank using hidden, inaudible aircraft frequencies and flight logs.
I spent the last week in a drop-dead sprint to replicate the entire 3D physics pipeline, DEM elevation models, and locked multi-event scoring code. I successfully tested the triangulation model on my own archive—and it works.
If you want to see the threat vector in action and the defense tool I built to scrub the signal, watch the breakdown here:
Video Response: https://www.youtube.com/watch?v=0WnnCtGaZnI&t=5s
For context, you can see Colsto’s original demonstration video here:
Original Exploit Video: https://www.youtube.com/watch?v=UytYrhYLOKI
NOTICE ON THE DEMO ENGINE: I have stood up a closed-source live replication engine at doppler.ninja, hosted on a Railway instance. Because the physics pipeline is incredibly heavy—requiring over 100 hours of localized audio history and an hour of active backend compute just to return a single location result—the demo sandbox is heavily rate-limited and restricted.
If you want a full walkthrough of the technical build log and how the signal processing pipeline operates behind the scenes without waiting on the hosted engine queues, I've logged it here: https://doinfinitely.github.io/doppler-triangulation-attack/
Engine details and the deployment access password are listed in the comments below.
r/redteamsec • u/____none____ • 5d ago
| Armory | +550 adapted BOF and .NET utilities |
|---|---|
| Communication | Custom C2 with external platforms (e.g. Telegram, Discord, etc.) |
| Runtime evasion | Indirect syscalls, stack spoofing, sleep mask, AMSI/ETW patch, etc. |
| Injections | Allocation modes: VirtualAlloc, section, and module stomping |
| LOTL | Living off the Land integration with +240 native Windows binaries (LOLBAS) |
| Static evasion | PE customization |
| Implants | Cross platform: Windows, Linux, macOS (ARM support) |
| Linux | Implants compatible with Linux BOFs |
| AI | Integration with agents (DeepSeek, local, etc.) |
| Reports | Executed commands, IOCs, and compromised hosts |
r/redteamsec • u/johncross08 • 5d ago
I built this over the last few weeks and released it on 8 Nov. It’s a beta.
The idea: when someone gets into a network, the next thing they do is hunt for saved passwords. Lure plants fake ones where they look (a passwords spreadsheet, an RDP file, .git-credentials, a VPN profile, a QR code on a helpdesk notice, a DNS name for a backup server that doesn’t exist). The files only point at a listener machine you control.
r/redteamsec • u/Rare_Bicycle_5705 • 7d ago
r/redteamsec • u/utku1337 • 7d ago
r/redteamsec • u/djad04 • 8d ago
r/redteamsec • u/Mafifrizi • 8d ago
r/redteamsec • u/Rebellionxkid • 8d ago
r/redteamsec • u/Infosecsamurai • 9d ago
Weekly Purple Team: HTML Smuggling + WASM Payload Delivery
Dropped a new episode this week covering HTML smuggling combined with WASM-based payload obfuscation — reconstructing payloads client-side in the browser via Blob objects/data URIs, with WebAssembly layered in to obscure the decoding logic and complicate static analysis.
On the blue team side, we break down the detection and reverse-engineering workflow, identifying smuggling indicators, extracting and decoding the embedded payload, and doing basic analysis of the WASM module to recover its logic
Covers T1027.006, T1140, and T1566 with the full red vs. blue format.
Video: https://youtu.be/iUdtkH_nw6k
Happy to discuss the smuggling/obfuscation mechanics or the RE side in the comments.
r/redteamsec • u/socradario • 9d ago
r/redteamsec • u/Rebellionxkid • 10d ago
I’ve built a tool for advanced subdomain enumeration and reconnaissance. I was never a fan of Amass or Sublist3r—they simply lacked the functionality I needed. My tool goes beyond basic passive reconnaissance (without requiring API keys) and standard brute-forcing; it features deep brute-forcing with complex mutations, PTR resolving, network segment (NETSEC) walking, ASN identification, web crawling, automated SYN/TCP port scanning, and HTTP header analysis to uncover web server technologies. It also identifies other domains belonging to the same organization, providing a percentage-based match score. Furthermore, it searches for S3 (and other) storage buckets, performs TLS SAN and vhost probing, checks SPF/DMARC/MX records, analyzes CSP headers, and extracts JS source maps. It includes wildcard-aware DNS resolution, verified independently at every zone level—not just at the root. It also maintains a convenient search history in an SQLite database and supports exporting results to JSON, TXT, or CSV formats (making it easy to integrate with AI/machine learning models).I would welcome suggestions for improving the tool, as well as constructive criticism regarding its architecture (the latter is particularly important to me).