Approaching a target to hack can feel like climbing a mountain. You may face large scopes, confusing applications, complex user hierarchies…the list goes on. The key to hacking in today’s world of large and/or complicated targets is a combination of two things:
- A work environment that encourages productivity.
- A workflow or checklist of steps to have an efficient yet complete engagement.
The following steps are a good blueprint to get you down the path of supercharged hacking!
Step 1: Preparing your workspace
The first step to having a supercharged workflow is your workspace. There are three quick things to keep in mind when preparing yourself and your workspace:
- Desk setup
- Distractions
- Mindset
Desk setup
Having the tools you need to do the job is vital to the task’s completion. This remains true when you sit down to hack. The ideal setup will include a spacious workspace with as little clutter as possible. If there is too much clutter on your desk or workspace, it is proven that this will distract you. You should have only the necessities. Ideally, a comfortable chair that keeps you at the right height is equally important. Any decorations or personal items on your desk should be in the background, out of your way. Some studies say adding a “flow” to your workspace is a hidden secret. For instance, create a space where incoming tasks are on your left, your PC or workstation is in the middle, and completed tasks are to the right.
Distractions
Your workflow can’t be supercharged if you are constantly being interrupted. Placing any phones or electronics and other distractions away would be ideal. These electronic distractions should also be silenced. This effort will increase the chance that you stay focused while working. Some people enjoy different types of music or background noise while working. Everyone is different in this regard, but keep in mind that if there is background music, it should not require your constant attention. It should be something you can start and leave alone. Giving yourself breaks is important, but always ensure your working time is as productive as possible.
Mindset
Your mindset can completely change how you see a challenge. So you must go into your hacking sessions with a good mindset. But what makes a good mindset? Well, I would argue that the following list is a good place to start:
- Setting personal goals for your day.
- Remembering your long-term growth is more important than short-term results.
- Making mission statements.
- Enjoy the process and enjoy learning!
- Control your internal language.
The first two things on the list are a solid start. Making small personal daily goals you enjoy chasing will only increase your drive. At the same time, remember that your long-term growth as a supercharged hacker is more important than any specific day’s results! Everyone has bad days, but having a consistent growth mindset is essential. Making a mission statement for yourself ensures that you know the “why” behind why you are hacking in the first place. Enjoying your work is something so few people seem to get now. Find a way to get yourself in a mindset where you enjoy your workflow and the continuous learning that comes with it! All of the above can be increased by ensuring that your internal dialogue with yourself is positive. You decide your mindset!
Step 2: Recon
Now let’s get to hacking! The first step will be performing thorough reconnaissance on your target. Depending on the scope of your target, this could vary a bit, but I am going to split this section into two parts. The first part of our recon workflow will be finding as many in-scope assets as possible. Finding as much of the in-scope infrastructure as possible is key to the rest of the workflow. The second part will be for each specific asset we find and what types of technology are present on each asset. I will have checklists for each section so you can check things off as you go. The idea is to start at the broadest scope possible and then narrow it down. So if you have an open scope program, use the large scope checklist, take the domains from there, use the medium scope checklist, and so on.
Infrastructure/Asset discovery
Large scope (open scope)
Medium scope (*.example.com)
Technology analysis (for enumerated domains)
- Identify cloud assets (cloudenum)
- Identify web server, technologies, and databases in use (httpx, wappalyzer)
- Try to locate interesting files (/robots.txt , /sitemap.xml, /.git, etc)
- Search comments on web pages (Burp Engagement Tools)
- Directory/parameter fuzzing (ffuf and wordlist)
- Identify WAFs (whatwaf, wafw00f)
- Google dorking (GHDB)
- GitHub dorking (githound, gitdorks_go)
- Passive directory enumeration (waymore, gau)
- Spidering endpoints (gospider, xnLinkFinder)
- Check potentially vulnerable parameters (gf-patterns)
- Locate sensitive endpoints (logins, admin panels)
- Get all JS files (subjs, xnLinkFinder)
- JS hardcoded APIs and secrets (nuclei-tokens, trufflehog)
- JS analysis (subjs, JSA, xnLinkFinder, getjswords)
- Run automated scanner (nuclei)
- Test CORS (CORScanner, corsy)
Step 3: In-depth application analysis
User management testing
Registration
- Duplicate registration testing (overwriting an existing user)
- Weak password policies (tip: check if a password allows just spaces)
- Fuzz for folders created for new users
- Allowing vital profile actions (ex: changing password) without verifying email
- Test re-registering with same/different passwords
- Try to register with the target’s email
- Check OAuth with social media registration
- Check state parameter on social media registration
- Try to capture integration requests (possible account takeover)
- Check redirections on the registration page after login (tip: try repeating the register request while already logged in)
- Check for cross-site scripting (XSS) on the name or email
Authentication
- Username enumeration
- Account recovery function
- “Remember me” function
- SQL Injections
- Auto-complete testing
- Lack of password confirmation on change email, password, or 2FA (try change response)
- User account lockout mechanism on brute force attack
- Check for password wordlist (cewl and burp-goldenNuggets)
- Test Oauth login functionality for Open Redirection
- Test response tampering in SAML authentication
- In OTP check guessable codes and race conditions, response manipulation for bypass, or brute force attacks
- If JWT, check common flaws
- Try logging in with easy or default credentials
Sessions
- Test tokens for meaning and predictability
- Insecure transmission of tokens
- Check logs for live tokens
- Session termination and fixation checks
- Test for cross-site request forgery (CSRF)
- Check the scope of important cookies
- Decode cookie if possible (ex: base64)
- Check HTTPOnly and Secure flags
- Use the same cookie from a different asset to get a session
- Check controls using multiple accounts
- Insecure access control methods (request parameters, Referer header, etc)
- Check concurrent logins
- Path traversal in cookies
- Try to perform a privileged user’s actions with an unprivileged cookie
Profile
- Find IDs for a user, then test to try to access or change other users
- Try CSRF against user account-specific actions
- Change username or email to an existing username or email
- File upload testing on any profile pictures
- Check profile picture URL for ids or tokens
- Try to delete an account, then recover it with the forgot password functionality
- Try parameter pollution to add two values of the same field
- Check if you can add roles manually
Forgot/Reset password
- Invalidate session on logout and password reset check
- Check password reset tokens for uniqueness and expiration
- If IDs or sensitive data are present in the reset link, try changing them (possible IDOR in the reset link)
- Request 2 reset passwords links and use the older
- Check for sequential tokens
- Host header injection for token leakage
- Email crafting like victim@gmail.com@target.com
- Capture reset token and use with another email/userID
- Check encryption in reset password token
- Token leak in the referer header
- Append second email param and value
- Understand how a token is generated (timestamp, username, birthdate,…)
- Response manipulation
Input handling
- Try to discover hidden parameters (arjun)
- Fuzz all request parameters
- Identify all reflected data
- Check for cross-site scripting (reflected, stored, DOM)
- HTTP header injection in GET & POST
- Remote code execution (RCE) via Referer Header
- SQL injection via User-Agent Header
- Check for any redirections
- Stored attacks (cross-site scripting, file uploads, etc.)
- Check/Fuzz for command injection
- Path traversal, LFI, and RFI checks
- Script injection
- File inclusion
- LDAP injection
- SSI Injection
- XPath injection
- XML external entity (XXE) checks (change content-type to text/xml)
- SQL injection (tip: start checks with ‘ and ‘–+-)
- NoSQL injection
- HTTP Request Smuggling
- SSRF in previously discovered open ports
Application logic testing
- Identify possibly vulnerable logic
- Test transmission of data
- Test for reliance on client-side input validation
- Handling of incomplete input
- Transaction logic
- Change IDs related to any action
- Tamper/Reuse gift or discount codes
- Try parameter pollution to use gift code two times in the same request
- Parameter pollution on social media sharing links
- Change POST-sensitive requests to GET
Step 4: Take good notes
Organization
Why are organization and note-taking so important? Well, if you are trying to supercharge your hacking workflow but don’t remember what steps you have done or the results of those tests, then you are bound to repeat tests and forget information. This leads to a lot of repeat testing, as well as missed findings! That doesn’t sound very supercharged! Staying organized as you complete your workflow is just as vital to your hacking as the other steps. Organizing your thoughts also makes reporting your tests and findings easier! The larger the scope for a target is, the more lost you risk becoming unless you come prepared. So always ensure make sure as you test to keep as detailed notes (and screenshots) as you can.
What tools?
There is an astonishing amount of productivity tools out there today that include note-taking functionality. So which one do you use? Well, the answer is easy, whichever one works best for you! With so many tools out there, they all are very good and which one you use is 100% up to you. There are a few that are popular:
Conclusion
The above workflow and checklists are a good start to supercharging your hacking, but as with many things, the learning and improving never ends. The goal is to take these steps and use them as a starting point. Where you take them from there is entirely up to you. Maybe you add some more tests or completely new sections, or maybe you add workflows for mobile apps. The goal of the workflow is to get started on your journey. Where you decide to further supercharge your hacking workflow is completely up to you!
Written by:
Gunnar Andrews
My online alias is G0lden. I am a hacker out of the midwest United States. I came into the hacking world through corporate jobs out of college, and I also do bug bounties. I enjoy finding new ways to hunt bugs and cutting-edge new tools. Making new connections with fellow hackers is the best part of this community for me!
Related resources
Why not check out the following?