Aakarsh Mishra

if you know whoami , then you probably don't know whoami -

[Alam @bahauddinalam]

-----BEGIN RSA PRIVATE KEY-----
4
-----END RSA PRIVATE KEY-----

[BSides Indore @BSidesIndore]

🚨 3 Students. 3 Passes. 1 Chance. 🎟️

How to Enter:

❤️ Like this post
👤 Follow @bsidesindore
💬 Comment & tag 2 friends
📲 Share this post to your Story & tag @bsidesindore

🏆 3 Winners. 3 Student Passes.

👇 Tag your friends, enter now, and let the giveaway begin!

#giveaway

[PHYR3WALL 🇺🇲 @phyr3wall]

I've been building my AI-powered offensive security harness for the past few weeks. It's successfully solved every active HTB box (minus the insane machines). To help others learn and build alongside me, I'm giving away your choice of a 1-Month Claude Pro subscription or 1-Month HTB VIP+.
Follow -> Like -> Retweet to enter

[𝐟𝐞𝐝𝐞𝐯𝐚𝐥𝐯 @fedevalv_]

Pepe finding out that you’re allowed to fight in the Real Madrid dressing room after he retired

[Coffin @lostsec_]

The hype around Claude Code security will fade in a few months, just like what happened with Xbow AI. AI tools can assist, but they can’t replace human creativity, intuition and real attacker mindset. In bug bounty hunting, the edge still belongs to humans who think differently.

[Aakarsh Mishra @AakarshMishra15]

@ITSecurityguard That’s very true, and I agree with you @ITSecurityguard.

AI is a powerful tool for security researchers.
But hacking isn’t checklist automation, it’s curiosity, experimentation, and understanding systems deeply.
That part isn’t getting replaced anytime soon.

Worth reading!!

[Patrik Grobshäuser @ITSecurityguard]

I finally let Claude do my pentest this week. Full 5-day engagement, zero human input. Here's what the client got: 😏

https://t.co/1PPuxhs4V9

#bugbounty #pentesting #AI #cybersecurity #infosec #claudeai

[Anmol K Sachan @FR13ND0x7F]

🧵 I built a free AI/ML pentesting roadmap from scratch.

Everything you need to go from zero → bug bounty on LLMs.

Bookmark this. (thread)

[Md Ismail Šojal 🕷️ @0x0SojalSec]

Resources for learning more about WebSocket Hacking. 📕

- https://t.co/aF7QujHcBL

- https://t.co/ZuDoX3TIpa> https://t.co/dlLgz99gtd

- https://t.co/2Kb6vIsETc

- https://t.co/m6MGSmpN2u #bugbounty

- https://t.co/5XIW7Ii53a

#infosec #cybersec #bugbountytips

[Nicolas Krassas @Dinosn]

GitHub - 0xMarcio/cve: Latest CVEs with their Proof of Concept exploits. https://t.co/gIxgiCswFo

[Coffin @lostsec_]

Found API keys or tokens but not sure where to test them? Try this site. it offers a wide range of services so you can quickly validate different types of API keys in one place.

[Muqsit 𝕏 @mqst_]

🧰 Beginners Guide: Comprehensive Reverse Engineering Tutorials for Beginners

PDF: https://t.co/vbqCpQQfLy

author: @0xInfection

#infosec #reverseengineering

[𝕏 Bug Bounty Writeups 𝕏 @bountywriteups]

CVE-2025–56676 | Critical Vulnerability in Zender Gateway Allows Account Takeover
https://t.co/vzjqScY4dt

#bugbounty #bugbountytips #bugbountytip

[Aakarsh Mishra @AakarshMishra15]

@HACKER_TEAM49 @coffinxp7 @bug_vs_me Be a man!!

[Elorm Daniel @elormkdaniel]

A system was completely locked up by malware. Antivirus failed. We had no access to the hard drive…
But we had one thing: a full packet capture.
Here’s how I used Wireshark to trace the infection, extract the malware, and analyze its behavior.👇

The Setup:
The infected host: 12.183.1.55
I had the full .pcap from the time of infection.

My goals:
Identify where the malware came from

Extract the file from the packet data

Analyze what the malware did

Look for signs of worm-like propagation

[Aakarsh Mishra @AakarshMishra15]

@Edx103 Cheers to your success brother 🎉

[X @TheMsterDoctor1]

Here’s a full blueprint on how to hunt and reproduce those same types of bugs, especially for PII/data leaks:

⸻

✅ 1. Mass PII Exposure (Billing, Finance, Address, Payment)

Targets:
•/invoices/, /billing/, /account/, /payment/, /orders/, /checkout/
•APIs: /api/user, /api/invoice, /api/payment-method

How to Hunt:

A. IDOR on User-Specific Endpoints

GET /api/invoice?id=1001
GET /account/billing/1002

Use Burp Suite → Repeater → brute different IDs. If no auth token is required or the response leaks PII = Critical.

B. Find Public Files (PDF, CSV, ZIP)

gau https://t.co/axAPlulNpQ | grep -Ei "\.pdf|\.csv|\.zip" | tee files.txt

Then:

cat files.txt | xargs -I % curl -s "%" | grep -Ei "email|name|address|iban|card|amount"

C. Google Dorking for Internal Billing Docs

site:https://t.co/axAPlulNpQ inurl:invoice filetype:pdf
site:https://t.co/axAPlulNpQ inurl:billing filetype:csv

✅ 2. Account Takeover via DOM XSS or CSS Injection

How to Hunt DOM XSS:

Tools:
•XSStrike
•Burp + DOM Invader (via Burp extension)
•Manual payload injection into:
•URLs
•Fragment #
•DOM sink params like location.hash, document.URL

Payloads:

"><script>alert(document.domain)</script>
"><img src=x onerror=alert(1)>

Inject into:

https://t.co/RYKqExAvG7...
https://t.co/xuCA4IImK4...

CSS Injection → Data Exfil:
•Inject into CSS-controlled fields (themes, names, etc.)
•Use CSS exfil toolkit: https://t.co/qzL7rnY4Ry

✅ 3. Massive Leak Recon Strategy

Use this recon pipeline:

subfinder -d https://t.co/axAPlulNpQ -o subs.txt
cat subs.txt | httpx -paths /billing,/account,/api/user,/invoice -status-code -title -mc 200 | tee live_targets.txt

Then:

ffuf -u https://t.co/brXEVPiKlW -w endpoints.txt -mc 200 -o hits.json

Wordlist:
•SecLists/Fuzzing/endpoints-fuzz.txt
•Add custom: invoice, contract, statement, download, report, user-info, etc.

⸻

✅ 4. Payload Automation (Burp/Intruder)

Automate with Intruder or Turbo Intruder:
•Position fuzz at invoice_id, user_id
•Payload: 1000-9999
•Grep Match: "email", "card", "amount", "zip", "ssn"

✅ Bonus: What to Report

High/critical impact:
•Access to other users’ invoices
•Downloadable ZIP or PDF with hundreds/thousands of users
•DOM XSS in billing.js or account dashboard
•Public Firebase/Firestore storage leaking users.json
•Exposed /wp-content/uploads/private/contract_2023.csv

PII Hunter tool is ready.

✅ How to Use It

chmod +x pii_hunter.sh
./pii_hunter.sh https://t.co/axAPlulNpQ

It will:
https://t.co/Br2ACtaE47 gau to collect archived URLs
2.Extract any links to .pdf, .csv, .zip, .xls
3.Find PII-related paths (billing, invoice, account, etc.)
4.Test live URLs with httpx
https://t.co/xzjLB5Gk97 any exposed files
6.Grep for indicators of PII like emails, SSNs, card data, etc.

./pii_hunter.sh https://t.co/axAPlulNpQ

#!/bin/bash

# THEMSTER PII HUNTER - Recon & Leak Detection

# Requires: gau, httpx, ffuf, curl, grep, jq

domain=$1

if [ -z "$domain" ]; then
echo "Usage: $0 <domain>"
exit 1
fi

mkdir -p pii-hunter/$domain
cd pii-hunter/$domain

echo "[*] Running gau to get archived URLs..."
gau $domain | tee all_urls.txt

echo "[*] Filtering for sensitive filetypes (pdf, csv, zip, xls)..."
cat all_urls.txt | grep -Ei '\.pdf|\.csv|\.zip|\.xls' | sort -u > sensitive_files.txt

echo "[*] Filtering for billing/invoice/account-related paths..."
cat all_urls.txt | grep -Ei 'billing|invoice|account|contract|statement|payment' | sort -u > pii_paths.txt

echo "[*] Checking live URLs with httpx..."
cat pii_paths.txt | httpx -silent -mc 200 > live_pii.txt

echo "[*] Downloading exposed files (if any)..."
mkdir -p downloads
while read url; do
filename=$(basename "$url")
curl -s "$url" -o downloads/$filename
done < sensitive_files.txt

echo "[*] Scanning files for PII indicators (email, address, SSN, card)..."
grep -E -i -r 'email|@|address|ssn|iban|card|zip|payment|name|phone' downloads/ > suspected_pii.txt

echo "[*] Done. Output saved to: pii-hunter/$domain/"

[Ansh Bhawnani @techhacker98]

The same people concerned about their privacies are happily posting their artistic photos all over the internet.

I mean the evolution is great and exciting but the right way to do it is not to train those public AI models with your personal stuff.

[InfoSec Community @InfoSecComm]

New Write-up on InfoSec Write-ups publication : "All about Blind XSS for beginners" https://t.co/JJS5n9xGKl

[𝕏 Bug Bounty Writeups 𝕏 @bountywriteups]

🌀 One liner to find SSRF

#bugbounty #bugbountytips #bugbountytip #hackerone #bugcrowd #infosec #cybersecurity #pentesting #redteam #informationsecurity #securitycipher #technology #coding #code #recon #ai #llm #owasp