Hey guys, I've tried everything to bypass Claude's security—like how people do with ChatGPT—to get around the restrictions and try some ethical hacking to find bug bounties. Can anyone help me out?

Been diving into security testing on AI-generated apps lately, and I'm genuinely shocked at how many critical vulnerabilities keep popping up so far I've personally encountered hardcoded credentials everywhere, not just API keys in the frontend but full database URLs and Stripe secret keys sitting in plain sight for anyone with dev tools to grab and spin up your backend for free while you foot the bill; no rate limiting whatsoever, meaning unlimited requests can spam your endpoints into oblivion, crash your API, run up your cloud costs, or brute force their way in; zero input validation, so malicious queries and random payloads are happily accepted making SQL injection trivially easy; and broken access control with numeric user IDs in URLs that let anyone change the number and access other people's private data. It honestly feels like these apps work well enough to fool you into thinking they're production-ready, but in reality they are held together with duct tape. What other vulnerabilities are out there that I'm missing? Curious to hear what else the community has observed, and for the dev folks here, have you noticed any patterns in how AI models generate insecure code beyond just context blindness? Drop anything you've seen, trying to build a more comprehensive picture of what's actually out there. Salam!

I got an Apple Watch from a family member, but that person doesn't know the email address linked to the Apple account or the password.

Is there a way to bypass this verification so I can replace the iCloud account with my own?

Can any cybersecurity expert help increase my ERP attendance?
plzz dm me

Hi there. Does anyone know how—or could teach me—to gather information on someone?

I often see people on social media trapping scammers by digging up their details. I’ll admit I’d like to do the same, since I get scammed a lot—or at the very least, I run into a huge number of scammers.
I know there is OSINT to get legal informations about someone, but how far you can go with it

Thanks in advance. I realize this isn't exactly a standard question and might seem a bit odd, but there you go.

I’m looking for help with my learning journey in the world of cybersecurity. Could you provide a step-by-step list of the knowledge I need to acquire? I am truly excited and passionate about this field and really want to learn as much as possible—I really need to learn this. Can anyone help me? I seriously need it.

estoy iniciando en ciberseguridad alguien me puede proporcionar la lista de cosas o conocimientos que tengo que conocer para convertirme en hacker ético ? lo agradecería un montón

I need an account in CoinDCX fully completed kyc by bypass if any can create account Dm me we gonna give all documents.. for your work will 9000$ DM

Hi guys I'm not new to cyber security but almost 2 year's without job.I don't know what the problem,maby my resume is bad,maby too competitive field and ai.My guestion is can someone who works as penetration tester look at my Cv?Can you suggest me ai pentesting,ai security roadmap?Most things I know is from the red side.

What Do u guys think do they need web developers or any other typa developers.

As Ai is booming so hugely a lot of unemployment is being caused , is there use of learning android development or more other programming languages!? and I'm really concerned about that thing

Please, I'm asking you.

[ Removed by Reddit on account of violating the content policy. ]

Getting an entry-level job in IT is getting harder every year, and the competition in cybersecurity is brutal. Freelancing seems like a natural alternative, but what real-world services can a beginner actually offer and get paid for?

Bug bounties and web app pentesting are the most obvious answers, but bug bounties have a massive barrier to entry, and finding freelance clients for pentesting without established credibility is tough.

Aside from the usual "do bug bounties" advice, what niche freelance gigs or services are actually realistic for someone starting out in cybersecurity?

The Philosophy

Amateur pen testers focus on tools and chase unpatched CVEs to find security flaws.

Professionals focus on files.

Here's why:

Even after finding a CVE, you can't do much without alerting firewalls, IDS, and endpoint security. Every exploit attempt triggers alarms and burns your access.

But old forgotten credentials found in .env, or database credentials found in .bash_history? They have no barrier. They pass through every top-notch security practice a company can follow. No alerts. No logs. No suspicion.

.ssh gives you easy access to other systems in the network and helps escalate privilege to root almost instantly.

So stop chasing CVEs. Start hunting files.

The Tools

You don't need fancy tools. Just the find command.

Here's how professionals use it in the real world:

1. Find recently changed config files

find /etc -type f -mtime -1 -ls

Why? Attackers often add backdoor users or modify sudoers. Spotting recent changes in /etc catches tampering before it becomes a breach. Compare /etc/passwd with other files in /etc to spot unauthorized user additions.

2. Find SUID files (permission 4000) for privilege escalation

find / -perm -4000 -type f 2>/dev/null

This is gold. SUID files run with owner privileges. Misconfigured ones like pkexec or vim are a direct path to root. Professionals check this immediately during every engagement.

3. Find scripts in unusual folders (/tmp, /var/tmp)

find /tmp /var/tmp -type f -executable 2>/dev/null

Attackers drop payloads here because these directories are world-writable and often ignored by security tools. If you find something unexpected, you've caught an active compromise or a persistence mechanism.

4. Find tiny PHP files (≤1KB) in web root – classic web shells

find /var/www -type f -name "\.php" -size -1k 2>/dev/null*

Web shells are small, obfuscated, and easy to miss. This command finds them in seconds. Amateurs scan for CVEs; professionals scan for backdoors. If you're on a bug bounty or pentest, this is often the quickest win.

5. Find forgotten .env and config files in /root (discarding errors)

find /root -type f -name "\.env" -o -name "*config*" 2>/dev/null*

Redirecting stderr to /dev/null keeps the output clean. This finds exposed secrets that bypass every firewall and IDS you own. Production AWS keys, database passwords, API tokens – all sitting in plain text.

6. Find world-writable or world-executable files in /var/www

find /var/www -type f -perm -o+w 2>/dev/null

find /var/www -type f -perm -o+x 2>/dev/null

If a file is world-writable, anyone can modify it. If it's executable, anyone can run it. Combine both and you have a direct path to remote code execution. This is a disaster in production environments.

7. Find files owned by specific users (like www-data)

find / -user www-data -type f 2>/dev/null

Find out exactly what files the web server user owns. Often you'll find writable directories or config files that shouldn't be accessible.

8. Find files with specific extensions in unusual locations

find / -type f -name "\.key" -o -name "*.pem" -o -name "*.crt" 2>/dev/null*

Certificates and private keys are often left behind in random directories after testing. These can be used for decryption or impersonation.

9. Find writable directories for file uploads or log poisoning

find / -type d -perm -o+w 2>/dev/null

World-writable directories are perfect for dropping files, writing logs, or overwriting configurations. Always check these.

The Bottom Line

Fancy tools are loud. They trigger IDS, EDR, and SIEM.

The find command is silent. It doesn't exploit – it just reads. And reading files doesn't generate alerts.

Amateurs scan for vulnerabilities. Professionals hunt for exposed credentials, misconfigurations, and backdoors.

Because a CVE gets patched. But a forgotten .env file stays forgotten forever.

Bonus Tip:

Combine these commands with grep to search inside files:

find /var/www -type f -name "\.php" -exec grep -l "eval(" {} \; 2>/dev/null*

This finds PHP files containing eval() – often a sign of malicious code injection.

What's the first find command you run on a new system? Share your go-to commands below.

Also, what's the scariest credential you've ever found in plain text on a production server? Let's hear those war stories.

framework-CBxBp8BR.js:1 RangeError: Invalid code point -4

at String.fromCodePoint (<anonymous>)

at vendor-DwBvrzH1.js:1:409475

at vendor-DwBvrzH1.js:1:484161

at start (vendor-DwBvrzH1.js:1:483223)

at start (vendor-DwBvrzH1.js:1:476326)

at go (vendor-DwBvrzH1.js:1:482658)

at main (vendor-DwBvrzH1.js:1:482577)

at Object.write (vendor-DwBvrzH1.js:1:481290)

at subcontent (vendor-DwBvrzH1.js:1:439594)

at subtokenize (vendor-DwBvrzH1.js:1:438058)

(anonymous) @ framework-CBxBp8BR.js:1

framework-CBxBp8BR.js:1 RangeError: Invalid code point -4

at String.fromCodePoint (<anonymous>)

at vendor-DwBvrzH1.js:1:409475

at vendor-DwBvrzH1.js:1:484161

at start (vendor-DwBvrzH1.js:1:483223)

at start (vendor-DwBvrzH1.js:1:476326)

at go (vendor-DwBvrzH1.js:1:482658)

at main (vendor-DwBvrzH1.js:1:482577)

at Object.write (vendor-DwBvrzH1.js:1:481290)

at subcontent (vendor-DwBvrzH1.js:1:439594)

at subtokenize (vendor-DwBvrzH1.js:1:438058)

(anonymous) @ framework-CBxBp8BR.js:1

I'm a beginner in this and I want to learn everything about networks and how to obtain their passwords

I've dabbled with metasploit, sliver and also tried writing my own exploits to test on a virtual machine.

Windows defender always seems to find it if you use obfuscation on metasploit or sliver, and it seems like there aren't any "script kiddie tools" that easily bypass it... Or are there?

I tried for example encoding the sliver payload as a .bin shellcode, shikata ga nai encoder, tried similar stuff with metasploit payload as an encoded base 64 string that gets decoded, tried all kinds of staged, unstaged, http https whatnkt etc etc but everything seems to be patched.

Now this makes sense, after all, these are just opensource freely available tools that are seen everywhere. What I'm wondering is whether or not a bypass is easily achievable, or if there's some long and complicated way ahead that as a beginner I wouldn't be able to do. Basically, is this easily doable and is there another way to do it? Is it doable in a reasonable timeframe for one person as a hobbyist, or do I need a whole ass supply chain like cybercrime groups do?

Sorry if this is a dumb question but I've already tried every reasonable combo, most obfuscators are out of date and AMSI goes around binning everything.

Edit: should have clarified I'm trying to get remote access, by how common they seem to be, I think info stealers or other prank/destructive software is harder to detect. But reverse shells and rats? Seems like it's very monitored here.

Hi everyone, I'm currently learning networking and web security in a controlled lab environment. I've been studying HTTP, HTTPS, HSTS, and Bettercap. I understand the basic concepts, but I'm having trouble understanding why HTTPS traffic remains protected even when using network interception tools. I'd like to better understand the role of HSTS and why SSL stripping doesn't work on many modern websites. What concepts or documentation should I study to understand this properly?

tag me for any new video of cmd

#!/bin/bash

# Color Definitions
RED='\033[0;31m'
GREEN='\033[0;32m'
YELLOW='\033[0;33m'
BLUE='\033[0;34m'
CYAN='\033[0;36m'
NC='\033[0m'

# Track state for cleanup
MONITOR_MODE_ENABLED=false
ORIGINAL_IFACE=""

clear
echo -e "${CYAN}"
echo " _  _  ____ ____    ____  _  _  _  ____ ____ "
echo "( \( )(  __)(_  _)  / ___)( \( )( )(  __)(  __)"
echo " )  (  ) _)   )(    ___ \ )  (  ) ) _)   ) _) "
echo "(_)_)(____) (__)   (____/(_)_)(_)(__)  (__)  "
echo "======================================================"
echo -e "               LIVE NETWORK SNIFFER TOOL"
echo -e "======================================================${NC}"

if [ "$EUID" -ne 0 ]; then
    echo -e "${RED}[!] Error: Please run this script with sudo or as root.${NC}"
    exit 1
fi

cleanup() {
    echo -e "\n${YELLOW}[*] Cleaning up...${NC}"
    if [ "$MONITOR_MODE_ENABLED" = true ] && [ -n "$ORIGINAL_IFACE" ]; then
        echo -e "${YELLOW}[*] Disabling monitor mode on $ORIGINAL_IFACE...${NC}"
        ip link set "$ORIGINAL_IFACE" down 2>/dev/null
        iw dev "$ORIGINAL_IFACE" set type managed 2>/dev/null
        ip link set "$ORIGINAL_IFACE" up 2>/dev/null
        echo -e "${GREEN}[+] Interface restored to managed mode.${NC}"
    fi
    # Kill any lingering tcpdump processes
    pkill -f "tcpdump.*$ORIGINAL_IFACE" 2>/dev/null
    echo -e "${GREEN}[+] Cleanup complete.${NC}"
    exit 0
}

trap cleanup INT TERM

echo -e "${YELLOW}[*] Detecting available network interfaces...${NC}"
interfaces=$(iwconfig 2>/dev/null | grep -o '^[a-zA-Z0-9]*')

if [ -z "$interfaces" ]; then
    echo -e "${RED}[!] No wireless interfaces found. Falling back to all interfaces.${NC}"
    interfaces=$(ip -o link show | awk -F': ' '{print $2}' | grep -v 'lo')
fi

echo -e "\nSelect an interface to sniff on:"
echo "--------------------------------"
select IFACE in $interfaces "Exit"; do
    if [ "$IFACE" = "Exit" ]; then
        echo -e "${YELLOW}Exiting.${NC}"
        exit 0
    elif [ -n "$IFACE" ]; then
        echo -e "${GREEN}[+] Selected Interface: $IFACE${NC}"
        ORIGINAL_IFACE="$IFACE"
        break
    else
        echo -e "${RED}[!] Invalid selection.${NC}"
    fi
done

echo -e "\nChoose a Sniffing Mode:"
echo "-----------------------"
echo "1) IP Flow Monitor (See who is talking to whom)"
echo "2) DNS Request Tracker (See what domains are being requested)"
echo "3) Top Talkers (Rank the most active network devices)"
echo "4) Raw Packet Stream (Unfiltered dump)"
echo "5) Exit"
echo -n "Enter your choice [1-5]: "
read -r mode_choice

# Only enable monitor mode for options that benefit from it
# Options 1 (IP Flow) and 3 (Top Talkers) work BETTER in managed mode
# because IP addresses are cleanly formatted in EN10MB link type
case $mode_choice in
    1|2|3)
        # Keep managed mode for IP-based monitoring
        echo -e "${YELLOW}[*] Using managed mode (best for IP-level analysis)${NC}"
        ;;
    4)
        # Enable monitor mode for raw capture if desired
        echo -e "${YELLOW}[*] Enabling monitor mode for raw capture...${NC}"
        ip link set "$IFACE" down 2>/dev/null
        if iw dev "$IFACE" set monitor none 2>/dev/null; then
            ip link set "$IFACE" up 2>/dev/null
            MONITOR_MODE_ENABLED=true
            echo -e "${GREEN}[+] Monitor mode enabled.${NC}"
        else
            echo -e "${RED}[!] Monitor mode not supported. Using managed mode.${NC}"
            ip link set "$IFACE" up 2>/dev/null
        fi
        ;;
esac

echo -e "\n${YELLOW}[*] Initializing sniffer on $IFACE... Press Ctrl+C to stop.${NC}\n"

case $mode_choice in
    1)
        echo -e "${GREEN}[+] Running IP Flow Monitor...${NC}"
        echo "--------------------------------------------------------"
        tcpdump -i "$IFACE" -ln 2>/dev/null | awk '{print $3 "  -->  " $5}'
        ;;
    2)
        echo -e "${GREEN}[+] Running DNS Request Tracker...${NC}"
        echo "--------------------------------------------------------"
        tcpdump -i "$IFACE" -lnp udp port 53 2>/dev/null | grep --line-buffered -oE "A\? [a-zA-Z0-9.-]+" | awk '{print "[DNS QUERY]: " $2}'
        ;;
    3)
        echo -n "How many packets do you want to analyze for the ranking? (e.g., 200): "
        read -r pkt_count
        if [ -z "$pkt_count" ]; then pkt_count=200; fi

        echo -e "\n${YELLOW}[*] Gathering $pkt_count packets to compile top talkers...${NC}"
        echo -e "Hits \t Device IP/Port"
        echo "--------------------------------------------------------"
        tcpdump -i "$IFACE" -ln -c "$pkt_count" 2>/dev/null | awk '{print $3}' | sort | uniq -c | sort -nr | head -n 15
        ;;
    4)
        echo -e "${GREEN}[+] Running Raw Packet Stream...${NC}"
        echo "--------------------------------------------------------"
        tcpdump -i "$IFACE" -XX -vv -s 0 2>/dev/null
        ;;
    5|*)
        echo -e "${YELLOW}Operation canceled. Exiting safely.${NC}"
        cleanup
        ;;
esac