Avatar
Part time CTF Player learn every day!!
🌠 I Love Hoshimachi Suisei!! 🌠
🌠 I Love Hoshimachi Suisei!! 🌠

OverTheWire Bandit Level 10 → 11 tutorial!!

Login

Log in as bandit10 using the password you just obtained from Level 9 → 10.

ssh bandit10@bandit.labs.overthewire.org -p 2220
# password: FGUW5ilLVJrxX9kMYMmlN4MgbpfMiqey

Why? Each Bandit level is a separate UNIX user. To solve 10 → 11, you must be the bandit10 user.

Task

Task

The password for the next level is stored in data.txt, which contains Base64-encoded data.

A little bit of Theory

  • Base64 is an encoding scheme (not encryption) that maps binary to 64 printable characters.
  • On Linux, use the base64 utility:

    • Decode: base64 -d FILE
    • Encode: base64 FILE
  • Base64 output often ends with = padding to reach a multiple of 4 characters.

Further reading:

Solution

  1. Confirm the file is present

    ls -l
    

    Why? Sanity check that data.txt exists and you’re in the right place.

ls data.txt

  1. (Optional) Peek at the data — looks Base64

    head -c 80 data.txt
    

    Why? You’ll typically see A–Z, a–z, 0–9, +, /, and maybe = padding.

sample

  1. Decode the file with base64 -d

    base64 -d data.txt
    

    Why? Decodes the Base64 text back to the original message containing the password.

decode

  1. Copy the password (no extra spaces/newlines).

  2. Log into the next level (bandit11)

    exit
    ssh bandit11@bandit.labs.overthewire.org -p 2220
    # paste the password you just found when prompted
    

Password

This is the password shown in my run; if yours differs, copy the one from your own terminal output.

dtR173fZKb0RRsDFSGsg2RWnpNVj3qRr

Troubleshooting

  • base64: invalid input → File may have wrapped lines oddly; try base64 --ignore-garbage -d data.txt.
  • Empty/garbled output? → Ensure you didn’t include shell prompt text when copying; re-run base64 -d data.txt.
  • Still unsure it’s Base64? → file data.txt may show ASCII text; Base64 isn’t a “format”, just text—decoding is the test.

Congrats 🎉 You decoded the Base64 message and can now play as bandit11.


Thanks for reading!

Until next time — Otsumachi!! 💖☄️✨

Cinema

all tags

GOT-overwrite aboutme aead ai alphanumeric-shellcode apt argc0 argon2 aslr assembly asymmetric atoi automation backbox bandit base64 bash beginner behemoth binary binary-exploitation binary-to-ascii blackarch blind blind-sqli blogging blue-team bruteforce buffer-overflow buffer-overwrite c caesar canary capabilities checksec command-injection commonmark cookie cron crypto cryptography ctf cutter cyberchef cybersecurity defenders detection dev directory-traversal dnf docs drifter ecc education elf env envp exploitation finale forensics format-string formulaone frequency frequency-analysis gcc gdb getchar gfm ghidra github-pages governance gpg guide hashing hkdf http jekyll jmpbuf kali kasiski kdf kernel keylength kramdown krypton lab ld_preload leviathan lfi lfsr linux linux-syscall llmops log-poisoning ltrace manpage markdown maze memcpy mitigations mitmproxy mlops narnia natas networking newline-injection nonce nop-sled nx object-injection obsidian openssl osint overflow overthewire package-manager pacman parrot path path-hijacking pathname php pie pkc pki pointer-trick pqc priv-esc privilege-escalation provable-security pwn pwntools pyshark python race-condition radare2 rag randomness recon red-team redirect relro requests ret2env ret2libc reverse-engineering reversing ricing roadmap rop rot13 rsa scapy security seed seo serialization session setjmp-longjmp setuid shell shellcode smoke soc sockets sprintf sql-injection srop stack-canary stack-overflow strace strcmp strcpy streamcipher strings strncpy strtoul substitution suid suisei symlink symmetric terminal test threat-intel time-based tls troubleshooting tshark type-juggling ubuntu udp utumno vigenere virtualbox virtualization vmware vortex walkthrough web windows wireshark writing wsl x86
dash theme for Jekyll by bitbrain made with