0xacb

@0xacb.com

Hacker grinding for L1gh7 and Fr33dφm, straight outta the cosmic realm. Co-founder @ethiack.com https://0xacb.com

Are you familiar with zero-width space? This character 👉 %E2%80%8B Try inserting %E2%80%8B between characters of a blocked word. If the filter sees a different string, and the backend ignores the invisible character, you may bypass some filters.

Which AI pentesting agent is the best in the world? And how can we even measure this? (We figured it out! Keep reading 👇) The existing benchmarking methods ain't good because they work like a CTF, which doesn't resemble real-world vulns.

Revshells is a great tool for quickly generating shell payloads according to your needs. It supports reverse shells, bind shells, msfvenom payloads, HoaxShell, and assembled payload options.

Bild

Most recon stops at A records, and that's where some attack surface hides. Querying all DNS records allows you to expand your recon. 🧑‍💻 CNAME records can reveal third-party services and subdomain takeover opportunities 🧑‍💻 MX records expose mail infrastructure

Bild

Here's a quick one-liner for finding open redirects to chain with something more impactful. This will hit all archived URL variants, replace parameter values with your payload, and confirm live redirects using HTTPX response matching.

Bild

Here's a simple concept that's helped me find a lot of bugs. Once it clicks you can't unsee it. A huge family of bugs is basically the same bug: two components read the same input and disagree about what it means.

When @jameskettle.com dropped his last-byte synchronization research back in 2019 I started hunting for race conditions. It's crazy that this still works so often 7 years later. It's such a common, widespread issue and I don't think most hackers are checking for it (usually low dupe count)

Submitting alert(document.location) will probably get you a medium. Proving impact can make a real difference. Escalating an XSS used to be as easy as leaking cookies. That often doesn't work anymore because the HttpOnly flag is typically present on the juicy session cookies.

Are you getting a forbidden status code hitting a sensitive endpoint on a Node.js app? It may be using Fastify. The middleware may check the exact path, e.g. /internal. If the app has router normalization options enabled, the following or variations may work: //internal /internal;a=b

A lot of people are now building and using their own hackbots daily. Here's a nice blog on using AI to hunt for vulns by 0xAsm0d3us. Some takeaways that I've also been experiencing:

CI/CD pipelines provide a lot of juicy attack surface. One common pattern: a build system lets you specify an output path for artifacts. If that path isn't sanitized, a ../ sequence lets you write files anywhere on the build server.

Reverse engineering MCPs like IDA Pro MCP or Ghidra MCP are really powerful to find memory corruption 0days or reversing CVEs.

Race conditions in OAuth flows can still happen in custom implementations. Tools like Turbo Intruder or even a simple multi-threaded script sending concurrent requests to the callback URL with different tokens may trigger it. Further reading here:

A couple more common OAuth 2.0 vulnerabilities

TL;DR The couple of bugs described below are common across different OAuth 2.0 implementations. The bugs may allow a malicious application to maintain an access to victim's account even after access revocation performed by the victim.

blog.avuln.com

Hackerone MCP Server (unofficial). An MCP server that gives you quick access to your HackerOne reports, programs, earnings, and scope data. Very useful tool by @OriginalSicksec for anyone that's automating but bounty hunting. GitHub repo 👇

GitHub - Sicks3c/hackerone-mcp-server: Unofficial MCP server for accessing your HackerOne reports, programs, scope, and earnings from Claude Code

Unofficial MCP server for accessing your HackerOne reports, programs, scope, and earnings from Claude Code - Sicks3c/hackerone-mcp-server

github.com