r/redteamsec • u/Minimum_Hour519 • 4h ago
r/redteamsec • u/dmchell • Feb 08 '19
/r/AskRedTeamSec
We've recently had a few questions posted, so I've created a new subreddit /r/AskRedTeamSec where these can live. Feel free to ask any Red Team related questions there.
r/redteamsec • u/Itz_hany • 9h ago
I attacked a real AI agent 360 times with prompt injection. It resisted every attack, but the defenses broke normal tasks.
github.comI built **AgentArena**, an open-source red-team range for AI agents and MCP servers, and ran 600 live trials against Claude models.
**What it is**
- Fake agents with fake MCP servers (email, GitHub issues, notes, web). Everything is local and fake, and the "secret" is a random canary string, so nothing real can leak.
- An attacker LLM that writes prompt-injection and tool-poisoning payloads, sees why they failed, and evolves them.
- A judge (rules first, LLM only for fuzzy cases).
- An MCP gateway with 5 switchable defenses: tool-description scanner + hash pinning, taint tracking, per-task allowlist, spotlighting, and a monitor model.
- Results with 95% confidence ranges, so small samples don't pretend to be facts.
**Live results** (Claude Haiku 5.5 as the agent, Sonnet 5.5 as the attacker, 30 attempts per cell)
| | no defense | taint tracking | spotlighting | all defenses |
|---|---|---|---|---|
| Attack success | 0% (0–4%) | 0% | 0% | 0% |
| Legit "reply to the sender" task | 30/30 | 0/30 | 30/30 | 0/30 |
**What I found**
- The model resisted all 360 attack attempts with no defense at all, and often called them out ("this looks like a prompt injection, I ignored it").
- Taint tracking blocked a normal "reply to the sender" task every time, because the address came from the email and not from the user. Against this model it added no measurable protection, but it removed 100% of that task's usefulness.
- Spotlighting (marking untrusted text as data) cost nothing.
**Limits, to be upfront**
- The attacker model refused to write the attack in about 47% of its turns, so attack pressure was lower than a determined human's. "0%" means these attacks failed, not that the model can't be injected.
- Only one victim model, and only 3 of the 6 attack types were run live (all 6 run in the free mock mode).
- Total API cost was about $5.
There's a free mock mode (`arena demo`) that runs the full matrix with no API key.
GitHub: https://github.com/Ahany1440/agentarena
Full write-up: https://github.com/Ahany1440/agentarena/blob/main/docs/WRITEUP.md
I'd love feedback, especially attack ideas that would get past the model, or better defenses that don't break legitimate tasks.
r/redteamsec • u/Minimum_Hour519 • 4h ago
Post-mortem: how an attacker got a shell through our Postgres
chovy.bl0ggers.comr/redteamsec • u/reach_u • 18h ago
I open-sourced REI: agents on Windows/Linux that reverse-engineer live connections into a data-center topology map
theshewaspretty.github.ior/redteamsec • u/Ferraun • 2d ago
Pass-the-Device (CODE BLUE 2026): taking VPN/SASE access off an EDR-monitored host
github.comSharing a writeup/talk release from cryptopeg ("Pass-the-Device" from CODE BLUE 2026). The repo includes EN/JA slides, 5 recon tools, and experimental Sigma + KQL detections:
Key takeaways:
- Device trust ≠ device binding: Moving from an enrolled laptop to an unmonitored machine (no EDR) via either (A) copying client state (certs/cookies/config) or (B) enrolling a new client via SSO.
- Persistence outside EDR: Cites Cisco and Zscaler examples where host isolation and account disablement still left a second session alive-treating new VPN/SASE enrollment as persistence outside EDR visibility.
- Three defender checks:
- Confirm VPN/SASE, enrollment, and IdP logs hit the SIEM.
- Reconcile 90-day device enrollments against asset inventory.
- Add session termination and enrollment revocation to IR playbooks alongside host containment.
r/redteamsec • u/gerard0_b4r0n • 2d ago
Daily Red-Team Tradecraft Briefing (20 Nov 2026): vCenter CVE-2026-123890 post-exploitation, a new AdaptixC2 agent, and a Windows 11 lock screen bypass PoC
medium.com
r/redteamsec
•
u/Unhappy_Champion5641
•
3d ago
[Hiring] Some More Remote Cybersecurity Roles (For both US and non-US candidates)
terac.comSo...a couple of days ago I posted about a remote cybersecurity role that's currently open at Mercor. However, since it's only open to US-based candidates, a couple of folks reached out asking if there are any roles for candidates outside the US. I took a look around on Mercor as well as some other companies I work with, and found some openings. Putting them down below for any non-US candidates looking for part-time/freelance oppurtunities (though US-based candidates are eligible too). I'm just copy-pasting some of the basics, like the responsibilities and pay rates...feel free to check out the full job listings for more detail.
1. Cyber Engineer (3+ Years Experience) [at Mercor]
Help build and review realistic code-security tasks for evaluating AI systems. Work includes identifying vulnerabilities, documenting reproducible exploits in controlled environments, and validating fixes and regression tests. Strong coding skills and clear technical writing are essential.
- Compensation: $400 per task
- Estimated average handling time: 5 hours per task
2. Offensive Cybersecurity Engineers [at Terac]
Responsibilities:
- Design and build offensive cybersecurity reinforcement learning environments
- Harden existing benchmarks to withstand advanced AI interactions
- Develop rigorous evaluation criteria for frontier AI models
- Collaborate on a long-term hourly basis to iterate on security scenarios
Compensation: $150/hr
3. Cyber Threat Intelligence SME [at Micro1]
- Map cyber threat intelligence (CTI) cases to established taxonomies, especially within the surveillance and privacy evaluation domains.
- Author boundary cases illustrating prohibited surveillance, attribution, and intrusion-adjacent requests, helping delineate permissible and impermissible actions.
- Evaluate and grade submitted threat responses with special attention to source reliability, analytic reasoning, stated limitations, and actionable utility.
- Identify and flag instances of over-refusal, ensuring legitimate threat analysis is not unnecessarily declined.
- Document and clarify challenging edge cases involving nation-state operations and other advanced threats.
- Provide concise written and verbal feedback to support the continuous improvement of AI threat assessment capabilities.
Compensation: $70 - $110/hr
Additionally, Mercor also has a Cybersecurity Research Expert talent network focused on Offensive Security & Vulnerability Research that you guys can sign up on to be considered for upcoming projects you might be eligible for - https://t.mercor.com/xkRzL
Hope you guys find these helpful and can land a role 🤞. I'll just add the same disclaimer I had put under my previous post - this is a referral post, and I may be compensated by the companies for any candidates referred by me. However, rest assured that my referral bonus is directly tied to your earnings (with no cost to you, ofc) - so unless you actually make any money on the platform, I won't either! Just wanted to let you know I'm not trying to get you to sign up for something that will only benefit me :D. The company is legit - I have been working with them for a while without any issues and getting paid on time, and I also know others in my professional circle who have had good experiences working on the platform. I'll do my best to help with any queries based on my knowledge and experience, but you can also reach out to the official support team on the platfiorm. Good luck! 🤞
r/redteamsec • u/Historical_Arm7977 • 3d ago
I rebuilt evilgrade against the eMudhra leak: a narrow MITM test of first-install TLS trust
faradaysec.comr/redteamsec • u/Additional_Curve3495 • 6d ago
Every week a popular package or SaaS vendor gets hacked. I built a tool that tells you within minutes if it's one you use
github.comr/redteamsec • u/Unhappy_Champion5641 • 5d ago
[Hiring] Part-Time Ream Teamers For a Responsible AI / Security Specialist (US only) [$90-$140per hour]
t.mercor.comHi folks. A company I'm working with (Mercor) is currently hiring security, red teaming and responsible AI specialists with hands-on expertise in application security, offensive security, threat analysis or trust and safety to improve the quality of their AI-training data with a safety-first approach. This is a W-2 employment position with Cincinnatus LLC, with the opportunity to be placed at a leading AI Lab as part of their extended workforce. The position requires a time commitment of 20 hours a week and offers an hourly rate in the range of $90-$140. The final rate will be confirmed in the offer letter for you to review before accepting. Apply Here.
Key Responsibilities
- Guide research and engineering teams to close knowledge gaps and improve AI model performance in security and responsible AI, application and infrastructure security, and red teaming and abuse prevention topics.
- Design challenging, domain-relevant tasks, and write accurate and well-structured solutions to security and responsible AI problems.
- Evaluate security and responsible AI tasks and solutions and provide clear, written technical feedback.
- Design adversarial tasks and red teaming scenarios that probe AI systems for security vulnerabilities, unsafe behavior and policy violations.
- Develop rubrics to assess the safety, accuracy and harm potential of AI responses on security and sensitive topics.
- Collaborate with other subject matter experts to ensure consistency and accuracy in training data.
Core Qualifications
- 4+ years of dedicated professional experience in cybersecurity, red teaming, penetration testing, threat intelligence or trust and safety at a recognized, top-tier organization.
- Hands-on experience in at least one of: application security and secure code review, penetration testing and offensive security, threat intelligence or incident response, or trust and safety policy enforcement.
- Relevant credentials such as OSCP, OSWE, GPEN, CISSP or published CVEs, bug bounty findings or security research are a strong plus.
- Demonstrable career progression.
- Ability to engage reliably for at least 20 hours/week during weekdays.
- Strong written communication skills and the ability to explain complex technical decisions clearly.
Feel free to check out the full job listing here for more details and apply if you think you might be a good fit. Please note that this opening is for US-based applicants only. I'd also like to add a disclaimer that this is a referral post, and I may be compensated by the company for any candidates who apply through my links. However, rest assured that my referral bonus is directly tied to your earnings (with no cost to you, ofc) - so unless you actually make any money on the platform, I won't either! Just wanted to let you know I'm not trying to get you to sign up for something that will only benefit me :D. The company is legit - I have been working with them for a while without any issues and getting paid on time, and I also know others in my professional circle who have had good experiences working on the platform. I'll do my best to help with any queries based on my knowledge and experience, but you can also reach out to the official support team on the platfiorm. Good luck! 🤞
r/redteamsec • u/Fun_Lawfulness_8167 • 6d ago
tradecraft [Open Source] RESX: Windows specialized malware analysis with API deobfuscation, argument recovery, kernel driver analysis and a lot, lot more!
github.comHiya,
I'm proud to showcase RESX, an open-source Windows reverse engineering and malware analysis toolkit written in Rust.
It started off as a small project to make reversing Windows binaries a bit less painful, but it's grown into something quite a bit bigger.
Now, before you think it's another IDA clone or something, I should probably clarify that RESX is specifically tailored towards Windows software, particularly malware analysis, Windows internals, and some of the techniques and headaches I've repeatedly run into while using other RE tools.
For example, malware often hides its Windows APIs behind hashes or encoded names, then calls them through function pointers. RESX can recover those API names, figure out how they were resolved, and trace them back to their actual call sites, even without PDB symbols.
Here's a small excerpt from one of the API-hashing test samples:
> resx behavior .\hash_resolver.exe --no-pdb --no-headers
Dynamic API resolution: PEB loader-list walk; API hashing (ror13-add); manual export-table walk; loader API by name
Dynamically resolved APIs (7):
0x000011F8 ?!LoadLibraryA [export-table walk sub_00001010 · ror13-add hash 0xEC0E4E8E, 1 call site]
0x00001208 ?!VirtualAlloc [export-table walk sub_00001010 · ror13-add hash 0x91AFCA54, 1 call site]
0x00001218 ?!VirtualProtect [export-table walk sub_00001010 · ror13-add hash 0x7946C61B, 1 call site]
0x00001228 ?!VirtualFree [export-table walk sub_00001010 · ror13-add hash 0x30633AC, 2 call sites]
0x00001238 ?!GetComputerNameW [export-table walk sub_00001010 · ror13-add hash 0x96A422A5, 1 call site]
0x0000129B ?!GetUserNameW [export-table walk sub_00001010 · ror13-add hash 0x5C52AA4A, 1 call site]These API names aren't present in the binary, even as encoded strings. RESX identifies the hashing algorithm, matches the hashes against Windows exports, and connects the recovered APIs to their indirect call sites.
It also reconstructs API arguments, analyzes kernel drivers and IOCTLs, traces Windows APIs through syscalls into the kernel, and handles things like packer analysis and overlapping instruction streams. There's quite a bit more, including a VS Code extension if you prefer something graphical over the CLI.
I've included some reproducible comparisons against IDA Pro and Ghidra in the README, particularly around API hashing and overlapping instructions. The test binaries and commands are included too, so you can check the results yourself.
It's still actively being developed, and I'd love to hear what people think, especially if you manage to break something or find cases where the analysis gets things wrong.
r/redteamsec • u/gerard0_b4r0n • 6d ago
Daily red-team tradecraft: AdaptixBOFKit, NTLM signing Phase 1, Outlook NTLM KEV, GSocket Linux persistence (16 Nov 2026)
medium.comr/redteamsec • u/Designer-Classic3925 • 7d ago
I built an open source project for OSCP-style practice labs, and more machines are on the way
github.comHey 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:
- GitHub: https://github.com/askarlabs/TheHackingMachine
- 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/nanaynunay • 7d ago
exploitation FortiClient, FortiShield_74.sys kernel driver oob
github.comhi, this is my new research repo, support pls
r/redteamsec • u/ROUNAK316 • 7d ago
I gave a sandboxed local model a one-line Apache patch. It built the working RCE.
github.comr/redteamsec • u/nanaynunay • 7d ago
FortiClient, FortiShield_74.sys kernel driver oob
github.comhi, this is my new research repo, support pls
r/redteamsec • u/bgbe_ • 7d ago
initial access Enterprise customer asked for your pentest report and vuln scan? I'll red-team one app or AI agent per founder for free this month
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/jdefr • 8d ago
tradecraft SrcWranglr v0.13 - C/C++ Graphical source navigator/analyzer. Find 0days and Generate a harness automatically.
github.comr/redteamsec • u/gerard0_b4r0n • 9d ago
TrustFall (CVE-2026-88235) — TrustedInstaller/CBS Session COM LPE, any interactive user → SYSTEM write (public PoC)
github.comr/redteamsec • u/RubberDuck31337 • 9d ago
Write-up: Win x64 Shellcode – Calling Convention and Stack Alignment (Part 4)
proteqtum.comPart 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/wtfse • 10d ago
exploitation exploit a 22 years old PostgreSQL composite-type vulnerability CVE-2026-6460
mehmetince.netr/redteamsec • u/BenTheCyberOne • 11d ago
CopperHound: open-source attack-path analysis for AD, ADCS and Entra ID, written in Rust
github.comI'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!