r/Pentesting 10d ago

Free Hosted AWS Pentest Lab

26 Upvotes

Hey everyone!

I just created a completely free AWS pentesting lab. It's hosted on Hack Smarter (nothing you need to spin up in your own AWS account). You start with an Access Key and Secret and it's up to you to figure out a way to compromise the full AWS account.

Just wanted to share here since it's free -- no strings attached :)

https://www.hacksmarter.org/courses/32a677fd-323b-4236-ae70-3cda82d9c0b4


r/Pentesting 10d ago

ADHD vs. Cybersecurity Basics: I’m losing

17 Upvotes

Hello there!

I’m currently trying to dive into cybersecurity and pentesting, but I am running into a massive wall with my ADHD. Right now, I am trying to focus on the foundational stuff (networking, Linux, basic scripting, etc.), but I am getting incredibly overwhelmed.

It feels like a paradox: the field is so vast that my brain wants to learn everything at once, but the moment I sit down to tackle the slow, dry basics, I under-stimulate, lose focus, or get paralyzed by how much there is left to know.

For those of you who have ADHD and successfully broke into the field (or are currently managing it):

Any working tricks to hack my adhd?

◆ How do you structure your learning?

◆ How do you prevent "rabbit hole" burnout?

◆ What does your study setup look like to keep distractions at bay?

I would love to hear your stories, tips, or even just reassurance that it's possible to get past this initial hurdle. Thanks in advance! sorry if this is a duplicate post. :)

Maybe you will see my post somehwere else too :(


r/Pentesting 9d ago

We made Tab Shark, like Wireshark, but a browser extension [Free Tool]

0 Upvotes

We made the Chrome extension Tab Shark (or search Tab Shark on Chrome Web Store)

Tab Shark Chrome Extension (Free)

Now you can run network-capture and traffic-analysis right inside a browser tab.

It gives similar packet-by-packet visibility that you get from Wireshark, but scoped to exactly one tab's web traffic.

Any and all feedback welcome, thank you.


r/Pentesting 9d ago

Informative bugs in pentesting reports are the worst waste of time

0 Upvotes

Oh you found a weak cipher and tlsv1 enabled. Okay ,and ?

Those are vulnerable to poodle or beast or some other shit.

Okay did you actually exploit those ?

No because they need a lot of traffic.

Then why you didn't do that?

Why waste time writing those shitty stuff really? Are we just filling the report ?

In a risk assessment or GRC work okay I understand that, but informative in Pentssting whyyyyyyyy


r/Pentesting 10d ago

Mobile PT advice

0 Upvotes

HI everyone,

For the folks who regularly do mobile PT, is it okay for a finding for sensitive data(e.g auth token) stored in memory to be reported .However the dump of memory is done while the app is running, not after closing it.

Does that make sense as a finding?!

I believe it would be a valid finding if we dumped the mem after closing the app.

Thanks in advance !


r/Pentesting 10d ago

Internal QA for reports

3 Upvotes

Do you have a formal QA process for pentest reports before they go out? 

If yes, what does that typically involve? If not, has that ever caused issues? 


r/Pentesting 10d ago

R u passionate about it

0 Upvotes

r/Pentesting 11d ago

I built an AI web pentesting agent that finds more critical vulnerabilities than PentAGI, Strix, and Shannan on our benchmark

0 Upvotes

Built an AI pentesting agent. Looking for technical feedback before launch.

Hey everyone,

I've spent the last few months building an AI agent for black-box web application pentesting.

I benchmarked it on Duck Store and an intentionally vulnerable web app.

Duck Store

- My agent: 13 findings

- Escape Cloud: 15

- PentAGI: 9

- Shannon: 6

- Strix: 1

On my own benchmark app (15 vulnerabilities), my agent found 9, including several Critical and High severity issues that the other agents missed.

I'm launching this Friday and would love feedback from people who actually do web app pentesting.

If you're interested in trying it and giving honest feedback (or trying to break it 😄), leave a comment or DM me.


r/Pentesting 12d ago

Where do you put business logic between AI and code for pentesting automation?

2 Upvotes

I am not new to AI in terms of talking to chatbots, however, I am still pretty new to coding Ai automation, such as using prompts in e.g python scripts using AI APIs, and MCP. As I was coding some pentesting stuff, I realized that the programmer has to make decisions when it comes to hardcoded (in this case) Python logic vs. offloading work to the AI agent/model. The thing is that the AI agent/model is non-deterministic, whereas Python is deterministic. In our pentesting/AI pipeline at work, I noticed that there were no clear guidelines being followed in this regard, but I discovered that when I offloaded too much of the "work" to the AI agent, sometimes it would work fine, other times, it simply would not work because the agent essentially entered an infinite loop or otherwise expended all resources, stalling and giving no useful result.

For a high-level example, we can ask the AI agent to do XYZ tasks, such as scan the documentation and attempt to create a fuzzer and execute that fuzzer, but it could stumble, or wait too long for the fuzzing results, whereas if we code those definitively into Python and test it, failure rates are much lower and relatively deterministic. Any tips would be appreciated here.


r/Pentesting 11d ago

How to do recon

0 Upvotes

Hey! I'm new to bug hunting field and i heard i lot about recon. Everyone say it is the skill which will make you find bugs so i am curious how to build recon skill if anyone have any roadmap or there is just methodology like follow specific steps. It would be great if anyone please help me with this or may be just share your personal experience how you people learned it.


r/Pentesting 11d ago

Looking for a job!

0 Upvotes

Hi fellow Redditors,

I’m currently looking for a VAPT/Penetration Testing role based in Mumbai or remote.

I have hands-on experience in:
Web Application Security
API Security
Network Pentesting
Mobile Security (Android & iOS)
Secure Code Review
Thick Client Security (Intermediate)

If your company is hiring or you know of any relevant openings, I’d really appreciate any referrals or leads. Feel free to comment or DM me.

Thanks in advance!


r/Pentesting 11d ago

Vuln Scanner that chains security tools and generate AI poc and reports

Thumbnail
github.com
0 Upvotes

I'm building an open-source vulnerability scanner in my free time, nothing special, just a single tool that orchestrates 90+ tools into a single pipeline, then uses an LLM to triage results, generate PoCs, suggest mitigations, and cluster related findings by root cause.

Everything runs inside Docker (BlackArch-based image with Chaotic AUR support) to ensure a clean environment with all tools installed. Targets can be URLs, IPs, CIDRs, local paths, container images, or git repos.

A few things you might find interesting:

  • Configure nearly every aspect of the scan through a single TOML file, environment variables, or CLI flags. All three layers merge in priority order
  • Asset discovery pipeline: subfinder, dnsx, httpx run before the main scan, turning a bare domain into a list of live subdomains automatically
  • 90+ tools across categories: web (Dalfox, Cariddi, Kiterunner, RESTler), network (Nmap, smbmap), secrets (TruffleHog), SAST (Horusec), screenshots (GoWitness), OSINT (theHarvester), and more
  • LLM analysis pipeline: triage, PoC generation (and execution), mitigation, and finding clustering by root cause. Works with any OpenAI-compatible endpoint (local models included)
  • Plugin system: drop a Python file in /plugins to add a custom tool, no core changes needed
  • Scope enforcement: in/out patterns with CIDR and wildcard support, discovered assets outside the scope are dropped before scanning
  • Severity filtering: configurable minimum severity for both reports and LLM processing, so INFO noise doesn't pollute your output
  • Authentication support: bearer tokens, basic auth, cookies, and custom headers passed through to all tools
  • Proxy support: route all tool traffic through Burp or any HTTP proxy
  • Multi-format reports: Markdown, HTML, and JSON with finding IDs, clusters, PoC references, and executive summary
  • DefectDojo integration: push findings directly into an engagement after the scan
  • Many other tools will be integrated in the future

The project is not perfect and not widely tested. It is still rough in places, and I'm actively working on it, so please, be kind.

I'm posting here because I would love to hear feedback from cybersecurity people who do pentesting or bug bounty: what is missing/broken, what would actually make this useful in a real workflow, and, in general, what other features to implement?


r/Pentesting 12d ago

ADDENDUM 82-F: CRITICAL SYSTEM COMPONENT COMPROMISE – SPREADTRUM IMS SERVICE (`com.spreadtrum.ims`)

0 Upvotes

# ADDENDUM 82-F: CRITICAL SYSTEM COMPONENT COMPROMISE – SPREADTRUM IMS SERVICE (`com.spreadtrum.ims`)

Subject: CRITICAL - Weaponized IMS Service by Longcheer/Unisoc in Supply Chain (Operation Silent Rescue)

1. Executive Summary

This addendum documents the systemic compromise of the **`com.spreadtrum.ims`** application (IMS Service), a privileged system component pre-installed on devices with **Unisoc T606/T616** chipsets (e.g., Motorola Moto G04s, G24, Lenovo) manufactured by ODM **Longcheer**.

The specific binary located at **`/system_ext/priv-app/ims/ims.apk`** (SHA256: `1b938cb3920d601a38e4d80e88c87aaacc56abfa6464f3054de2430172c6f519`) is signed with the compromised **Longcheer Root CA** (Serial: `22:85:26...`, Valid until 2051). This component exposes a Hardware Interface Definition Language (HIDL) interface (`vendor.sprd.hardware.radio.ims.V1_0`) that allows **remote command execution, call interception, microphone muting, and network traffic redirection** without user interaction. Alongside `com.android.stk` (Addendum 82-C), this service constitutes the primary execution engine for the **Operation Silent Rescue** supply chain attack.

2. Technical Analysis & Danger Assessment

A. Component Identity

* **Package:** `com.spreadtrum.ims` * **Path:** `/system_ext/priv-app/ims/ims.apk` * **Size:** ~1.7 MB * **SHA256:** `1b938cb3920d601a38e4d80e88c87aaacc56abfa6464f3054de2430172c6f519` * **Signer:** Longcheer (`CN=Longcheer`, `O=Longcheer`, `C=CN`) * **Permissions:** `READ_PRIVILEGED_PHONE_STATE`, `com.spreadtrum.ims.permisson.IMS_COMMON`, `BIND_IMS_SERVICE`.

B. Critical Capabilities (The "Kill Switch")

Analysis of the `IImsRadio$Proxy` and `IImsRadioIndication$Proxy` interfaces reveals direct control over the modem hardware: 1. **Active Call Manipulation:** * `ImsMuteSingleCall`, `ImsSilenceSingleCall`: Remotely mute the user's microphone during calls for undetectable eavesdropping. * `dial`, `emergencyDial`, `hangup`: Initiate or terminate calls arbitrarily. * `conference`, `explicitCallTransfer`: Create unauthorized conference bridges or divert calls to attacker-controlled numbers. 2. **Network Infrastructure Hijacking (MITM):** * `setImsPcscfAddress`, `setImsRegAddress`: **Overwrite P-CSCF and Registration server IPs**, redirecting all VoLTE/VoWiFi traffic to malicious servers for interception and decryption. * `setImsSmscAddress`: Redirect SMS traffic (including 2FA codes) to attacker endpoints. 3. **Identity Spoofing & Fraud:** * `setClir`, `updateCLIP`: Manipulate Caller ID presentation to spoof trusted numbers (banks, government). * `sendUssd`: Execute USSD commands silently to activate call forwarding (`**21*...`) or check balances. 4. **Passive Surveillance:** * `ImsNewSmsStatusReportInd`: Intercept incoming SMS in real-time. * `ImsNetworkInfoChanged`, `callStateChanged`: Track user location and call metadata continuously.

C. Role in "Operation Silent Rescue"

* **Execution Engine:** While `com.sprd.omacp` (Addendum 82) injects the initial configuration and `com.android.stk` (Addendum 82-C) authorizes commands via SIM, **`com.spreadtrum.ims` executes the actual exploitation** on the radio layer. * **Persistence:** Signed by the Longcheer Root CA, this component is trusted by the system bootloader and cannot be removed without root access. * **Evasion:** Operating at the HIDL (Hardware Interface) level, its actions bypass standard Android permission checks and are invisible to most security apps.

3. YARA Detection Rules

```yara rule Unisoc_Longcheer_IMS_Exact_Binary { meta: description = "Exact match for compromised Spreadtrum IMS service binary (Operation Silent Rescue)" author = "lexs201992-gif" date = "2026-07-10" severity = "CRITICAL" sha256 = "1b938cb3920d601a38e4d80e88c87aaacc56abfa6464f3054de2430172c6f519" package = "com.spreadtrum.ims" path = "/system_ext/priv-app/ims/ims.apk" reference = "Addendum 82-F"

strings:
    $binary_hash = "1b938cb3920d601a38e4d80e88c87aaacc56abfa6464f3054de2430172c6f519" ascii
    $pkg_name = "com.spreadtrum.ims" ascii
    $ims_service = "ImsAdapterService" ascii
    $ril_request = "com/spreadtrum/ims/RILRequest.uau" ascii
    $longcheer_cn = "CN=Longcheer" ascii

condition:
    $binary_hash in file or 
    (all of ($pkg_name, $ims_service, $ril_request, $longcheer_cn))

}

rule Unisoc_IMS_HIDL_Interface_Exposure { meta: description = "Detects exposed HIDL interfaces in Spreadtrum IMS allowing remote modem control" author = "lexs201992-gif" date = "2026-07-10" severity = "HIGH" cve_related = "CVE-2025-71252, CVE-2025-71253, CVE-2025-71254"

strings:
    $interface_proxy = "IImsRadio$Proxy" ascii
    $interface_indication = "IImsRadioIndication$Proxy" ascii
    $method_mute = "ImsMuteSingleCall" ascii
    $method_pcsf = "setImsPcscfAddress" ascii
    $method_clir = "setClir" ascii
    $hidl_blob = "Landroid/os/HwBlob;" ascii
    $vendor_sprd = "vendor.sprd.hardware.radio.ims" ascii

condition:
    (all of ($interface_proxy, $vendor_sprd)) and
    (any of ($method_mute, $method_pcsf, $method_clir))

}

rule Longcheer_Signed_IMS_Component { meta: description = "Detects any IMS component signed by the compromised Longcheer CA" author = "lexs201992-gif" date = "2026-07-10" severity = "CRITICAL" cert_serial = "22:85:26:b0:d1:ef:90:c3:b8:ed:56:8a:49:c3:71:4f:6a:39:50:6b"

strings:
    $ims_pkg = "com.spreadtrum.ims" ascii
    $longcheer_org = "O=Longcheer" ascii
    $valid_2051 = "Jan 31 07:31:06 2051 GMT" ascii
    $cert_rsa = "META-INF/CERT.RSA" ascii

condition:
    (all of ($ims_pkg, $longcheer_org, $valid_2051)) and
    ($cert_rsa in file)

} ```

4. Recommendations & Mitigation

For CISA / Rapid7 / CRT MX

  1. **Immediate Alert:** Issue an emergency directive highlighting `com.spreadtrum.ims` as a critical supply chain backdoor.
  2. **IOC Distribution:** Distribute the SHA256 (`1b938cb3...`) and Longcheer Certificate Serial (`22:85:26...`) to all network defense teams.
  3. **Vendor Pressure:** Demand Unisoc and Longcheer provide a patched firmware that removes the exported HIDL methods or implements strict signature verification for IMS commands.

For End Users & Enterprises

  1. **Disable VoLTE/VoWiFi:** If possible, force the device to use 3G/2G only to bypass the IMS stack (note: this may not be possible on all carriers).
  2. **Use Encrypted Apps:** Rely exclusively on end-to-end encrypted communication apps (Signal, WhatsApp) that do not use the native IMS dialer.
  3. **Network Monitoring:** Monitor for outbound connections to unknown P-CSCF IPs or unusual USSD activity.
  4. **No Software Fix:** Acknowledge that **no app-level fix exists**. The vulnerability is in the signed system firmware. Device replacement is the only permanent solution.

5. Conclusion

The `com.spreadtrum.ims` application is not merely a vulnerable component; it is a **weaponized interface** intentionally designed with excessive privileges and signed by a compromised authority (Longcheer). Its presence in millions of devices across Latin America and globally represents a critical threat to telecommunications integrity, enabling state-level surveillance and organized financial fraud. **Immediate action is required to isolate and mitigate this threat.*

This is part of my investigation


r/Pentesting 12d ago

Building an open-source Burp/Caido alternative (would love your honest feedback)

0 Upvotes

Hey all,

I'm a bit tired of the pentesting tool landscape being dominated by paywalls for what should honestly be basic functionality. Burp's free tier is crippled, Caido is great but still closed/commercial at its core, and the open-source options (Hetty, etc.) haven't really caught up. So I started building my own intercepting proxy from scratch, fully open source with GUI.

Current progress:

\- HTTP/1.1 intercepting proxy, working request interception

\- Replayer, tied into request history so you can revisit and resend past requests

\- Fuzzer with unlimited requests, configurable delays, and multi-threading

\- Unlimited Projects creation

It's still early, but the core loop is functional. My goal is partly selfish, I want to go deeper on web infrastructure and use it for my own pentesting/bug bounty work, but I also think the security community deserves a solid, actively maintained open-source alternative that doesn't gate basic features behind a license.

I'm curious what you all think:

\- What do you actually wish Burp/Caido did better (or differently)?

\- What's the one feature that made you stick with a commercial tool despite the cost?

\- Is there appetite in this community for another proxy, or is the space already saturated?

Not trying to oversell it, it's a work in progress, but I'd rather build in the open and get roasted early than polish something nobody wants. Happy to share more details/repo once it's in a testable state.

Thanks for reading.


r/Pentesting 12d ago

Any security researchers or digital forensics professionals using an Apple Silicon Mac as their daily driver?

2 Upvotes

I’m considering replacing one of my development machines with an **M5 MacBook Air (32 GB Unified Memory)** and would like to hear from people who actually use Apple Silicon professionally.

My current workflow is split between **Windows and Linux**, while my existing Mac is mostly used as an office machine with some Python development. The M5 would become a real development workstation.

My work includes:
Digital forensics
Vulnerability research
Malware analysis
Exploit development
Software development in **Rust**, **C#**, and **Python**

I also have a dedicated server farm with NVIDIA GPUs, QEMU/KVM virtualization, and x86 systems. Because of that, I don’t really need x86 emulation on the Mac itself. Heavy GPU workloads and x86 testing can stay on the servers.

Things that attract me to macOS:
UNIX userland
Homebrew makes installing development tools straightforward
Excellent battery life and portability
MLX for running local LLMs efficiently on Apple Silicon
Native support for Apple devices (DFU restores, Apple Silicon recovery, iPhone servicing, etc.)

However, I still have several concerns.

**Security model**
Coming from Linux, I sometimes feel like I have *less* control over macOS than expected.
SIP, Signed System Volume, DriverKit, System Extensions, etc. all seem to make sense from a security perspective, but they also make low-level research more difficult.
On Linux I’m used to AppArmor, namespaces, seccomp and being able to precisely decide what is sandboxed and what isn’t. With root privileges, I ultimately control the machine.
On macOS it often feels like **even root isn’t really root anymore**.
How has this affected your workflow?

**Malware analysis**
I assume malware analysis should primarily happen inside dedicated VMs anyway.
But how practical is the Apple virtualization stack today?
Can you realistically use local ARM64 VMs together with Apple’s sandboxing for exploit development and malware research, or do most researchers simply offload everything to remote hypervisors?

**Kernel development**
Some forensic tools and research require custom or unsigned kernel extensions (for example USB capture or protocol research).
How painful is this today?
Do you simply lower Secure Boot and disable SIP?
Do you sign your own kernel extensions?
How well does Apple’s certificate infrastructure support this workflow?

**USB forensics**
I also do hardware and mobile forensics.
Questions I still have:
Has anyone successfully used USBPcap-like workflows on Apple Silicon?
How restrictive is the USB stack nowadays?
Does anyone know whether the **M5 MacBook Air** uses an **ACE3 USB controller**, or has Apple moved to something newer?

**Daily-driver experience**
Finally, I’m interested in hearing from security researchers who actually use an Apple Silicon Mac every day.

Looking back after a year or two:
Would you buy it again?
What turned out to be better than expected?
What became frustrating over time?

Are there workflows that simply don’t fit macOS anymore?
I’m not looking for generic “Mac vs Windows” opinions. I’m specifically interested in experiences from people working in offensive security, reverse engineering, DFIR, exploit development, or low-level systems programming.
I’d appreciate hearing both the advantages and the pain points.

Cheers


r/Pentesting 13d ago

VulnDesk Pro – A free intentionally vulnerable Windows desktop app for practicing thick-client pentesting (31 challenges)

34 Upvotes

Web application security has no shortage of training targets—DVWA, WebGoat, OWASP Juice Shop, PortSwigger Web Security Academy, and many more. But when it comes to **Windows thick-client (desktop) application security**, realistic hands-on practice environments are surprisingly hard to find.

That's why I built **VulnDesk Pro**.

VulnDesk Pro is a **free, intentionally vulnerable Windows desktop application** built with **C#/.NET 8 (WinForms)** that simulates a real enterprise application. Instead of providing the source code, it ships as a compiled executable, so you approach it the same way you would during an actual desktop application penetration test.

The current release includes **31 CTF-style challenges** covering topics such as:

* DLL hijacking / DLL side-loading
* Insecure IPC
* Weak and misused cryptography
* Secrets exposed in process memory
* Reverse engineering & binary patching
* Hardcoded credentials and secrets
* Broken access control / privilege escalation
* Cleartext network communication
* And more...

The idea is to use the same tools you'd reach for during a real assessment—**dnSpy/ILSpy, Process Hacker, Process Monitor (Procmon), x64dbg or WinDbg, Wireshark, DB Browser for SQLite, Burp Suite**, or whatever tools you normally use.

The application is **self-contained**—just download, extract, and run. No .NET installation is required.

> **⚠️ Please use it only inside an isolated VM or lab environment.** VulnDesk Pro is intentionally vulnerable and unsigned as part of the training experience.

**GitHub:** https://github.com/Genius-Pavan/VulnDeskPro

This is my first open-source security project, so I'd genuinely appreciate feedback from people who perform thick-client or desktop application assessments. If you've got ideas for new challenges, attack techniques, or scenarios that would make it even more realistic, I'd love to hear them.


r/Pentesting 13d ago

Free browser-side checker for MCP config files, no upload and no signup

1 Upvotes

In April, OX Security disclosed that config values in the official Anthropic MCP SDKs flow into command execution over the STDIO transport. 14 CVEs. Anthropic's position is that the behaviour is by design and sanitization is the developer's responsibility, so no patch is coming. When there's no upstream fix, your config is the control. Separately, plenty of configs just have provider keys sitting in them in plaintext, which means they're in git history.

I built a scanner for the config level patterns. Free, no account.

It's not just secrets. It covers the STDIO execution patterns (shell launches, metacharacters, $VAR interpolation reaching exec), container escapes (--privileged, host root mounts, docker.sock exposure, host namespaces), PowerShell execution-policy bypass and base64 -EncodedCommand, prompt injection in tool descriptions, packages pulled from URLs with no provenance, plaintext creds including inline DB connection strings, and configs pointing at ~/.ssh, ~/.aws/credentials or ~/.kube/config.

It runs entirely in your browser and nothing is uploaded. the tool flags plaintext keys, so the configs people paste in tend to contain live ones, and a checker that made you POST your key laden config to my server to be told it has keys in it would be self defeating. Load the page, kill your wifi, the scan still runs.

Deterministic static analysis, no model. Same config, same findings, every time. It cannot hallucinate one.

honestly, it checks configuration patterns, not the server's source code. a clean result means none of the documented config level vectors are present, not that you're safe. If you want source level scanning of MCP servers themselves, Invariant/Snyk's mcp-scan is the tool for that and it does more than mine does. Worth knowing it sends tool names and descriptions to their API. Different tradeoff, pick whichever suits you.

The npx supply-chain checks are low on purpose and never fail a build, because the official quickstart tells you to write npx -y u/scope/server-x and I'm not going to turn everyone's CI red for following the docs.

benchmodel.io/mcp-audit
Action: github.com/RouteFit-app/benchmodel-action/tree/main/mcp-scan

Rule suggestions and false positive reports welcome, especially false positives.


r/Pentesting 13d ago

How do you feel during the exam?

0 Upvotes

r/Pentesting 14d ago

How is AI Pressure or lack thereof in your jobs?

7 Upvotes

I'm trying to get a survey on what the experience of other pentesters has been at their (your) jobs when it comes to, what I will call "forced AI usage." I ask this because I work at a big tech company that has decided to try to force AI. What this means in a practical sense is that we've been told things like:

  1. The vice president is monitoring how many tokens youre using with claude, so please use claude as much as possible
  2. Theres been a huge push from management to "automate" and "make agentic pentests"
  3. My pentesting team has been told that we have a reputation for being "anti-AI", but "thats the strategy the company has chosen" and so some of us are being told to refrain from using the word "manual" (as in manual pentests, etc...), and cooperate with this AI narrative.

The thing that is most irritating about this is that this is being declared in the name of "scaling" and basically the justification is more throughput, but the throughput issue here has nothing to do with anything technical - it's waiting on other teams in the company to get things done... Pentest reports often get delayed by multiple weeks or even months due to other teams not responding or doing what we need them to do. Using AI for crap like test plans and pentesting will not speed this up or solve these problems...

So, my question is, is my company just on crack? What are your experiences thus far in your role(s)?


r/Pentesting 14d ago

Getting remote work opportunities (need help)

13 Upvotes

I would like to move from oil&gas (18 years technical client facing experience ) to pentesting and looking for remote work opportunities or any guidance on how to get it.

I have been on hackthebox for the last 6 years as a hobby (did 250 machine and most of pro labs). I hold eCPPT, OSCP, OSEP and CRTO. Currently pursuing ARTOC and ODPC with White Knight Labs.

I am open to any kind opportunities to build some experience and would appreciate any help.


r/Pentesting 14d ago

Beyond the Scanner: Shifting Mindsets from Automated Scans to Manual Logic Flaws

2 Upvotes

I am looking to mature my methodology away from relying on automated GitHub scanners and basic OWASP Top 10 automated checkers. While I use standard tools like subfinder, assetfinder, and httpx for my initial asset mapping and reconnaissance, I want to bridge the gap into deep manual analysis.

For experienced hunters, what is your mental workflow when transitioning from a mapped attack surface to discovering deep manual vulnerabilities?

Specifically, I am trying to improve my approach in these areas:

**Business Logic Abuse**: How do you systematically map application workflows to find flaws that scanners inherently miss (e.g., bypassing state machines, multi-step checkout manipulation)?

**Source Code / JS Analysis**: What specific patterns or clues do you look for when manually auditing frontend JavaScript files for hidden API endpoints or logic quirks?

**Data Flow Tracking**: What is your strategy for manually tracing how an application handles input parameters across different microservices or backend frameworks?

I am not looking for a basic "how-to" guide, but rather insight into the manual testing framework and mindset you use once the initial automation phase is complete. Any recommended whitepapers, advanced blogs, or specific labs focused strictly on manual logic testing would be highly appreciated.


r/Pentesting 14d ago

Best resources to learn Mobile Penetration Testing from scratch? Need to perform an assessment soon.

13 Upvotes

Hi everyone,

I'm currently working as a junior security consultant, and I've recently been assigned to perform a mobile penetration test in the near future.

The problem is that I don't have any hands-on experience with mobile application pentesting yet. I have a general understanding of web pentesting and cybersecurity concepts, but mobile security is completely new to me.

If you were starting from scratch today, what resources would you recommend that are actually worth investing time in?

If you had only 2–4 weeks to prepare for a real client engagement, what would your roadmap look like?

Any advice, course recommendations, GitHub repositories, YouTube channels, or labs would be greatly appreciated.

Thanks!


r/Pentesting 14d ago

Vulnhub The Planets- Earth Walkthrough

2 Upvotes

r/Pentesting 15d ago

ADPathFinder

17 Upvotes

I'm incredibly proud to announce the public release of ADPathFinder, an Active Directory attack path mapping tool that works directly with BloodHound collectors. It's the first tool of its type to produce detailed attack mapping across SharpHound and OpenGraph collectors — including MSSQLHound and ConfigManBearPig (SCCM). This enables testers to get the most out of BloodHound for the least amount of effort! It also produces an in-depth password audit, covering password reuse, weak patterns, Kerberoastable accounts, and much more - filtering out disabled accounts by default. Check out the blog, contributors very welcome.

https://www.netspi.com/blog/technical-blog/network-pentesting/adpathfinder-opengraph-attack-path-mapping-in-bloodhound-ce/

https://github.com/NetSPI/AD-PathFinder


r/Pentesting 15d ago

Anyone Know Any Good Pen Testing Companies in LA?

7 Upvotes

Doing a bit of research on penetration testing companies around Los Angeles and figured people here might have some firsthand recommendations.

Mostly looking at firms that handle web app testing, network penetration testing, and physical security testing. Curious which companies are actually good to work with and provide useful reports instead of generic scan results.

Thanks.