Try Everything!

Bandit Level 0 -> Level 1

jaws99 — Wed, 23 Jul 2025 03:17:09 +0900

Level Goal

The password for the next level is stored in a file called readme located in the home directory. Use this password to log into bandit1 using SSH. Whenever you find a password for a level, use SSH (on port 2220) to log into that level and continue the game.

Commands you may need to solve this level

ls , cd , cat , file , du , find

`ls` stands for list. Lists the contents of a directory, displaying the names of files and directories.
`cat` stands for concatenate. Displays the contents of a file or concatenates multiple files.
For this level, you’ll primarily use ls and cat. The other commands may be useful in later levels.

Write up

After logging into the Bandit server as `bandit0`, we start in the home directory by default. Use the `ls` command to list the files in the current directory:

bandit0@bandit:~$ ls
readme

This shows a file named `readme`. To view its contents, use the `cat` command:

bandit0@bandit:~$ cat readme
Congratulations on your first steps into the bandit game!!
Please make sure you have read the rules at https://overthewire.org/rules/
If you are following a course, workshop, walthrough or other educational activity,
please inform the instructor about the rules as well and encourage them to
contribute to the OverTheWire community so we can keep these games free!

The password you are looking for is: ZjLjTmM6FvvyRnrb2rfNWOZOTa6ip5If

The readme file contains the password for the next level. Use this password to log in for Level 1.

Next Level : Level 1 -> 2

Bandit Level 0

jaws99 — Wed, 23 Jul 2025 03:04:07 +0900

Goal

The goal of this level is for you to log into the game using SSH. The host to which you need to connect is bandit.labs.overthewire.org, on port 2220. The username is bandit0 and the password is bandit0. Once logged in, go to the Level 1 page to find out how to beat Level 1.

Commands you may need to solve this level

ssh

ssh stands for Secure Shell and is a program for logging into a remote machine. It provide secure encrypted communications between two hosts.

Write up

To solve this level, we can use the `ssh` command to log into the Bandit server at `bandit.labs.overthewire.org` on port 2220, using the username `bandit0` and password `bandit0`.

The `ssh` command enables secure login to a remote server. The standard syntax is:

ssh [username]@[hostname] -p [port]

Using this syntax, run the following command in your terminal:

ssh bandit0@bandit.labs.overthewire.org -p 2220

After running the command, you’ll be prompted for a password. Enter `bandit0`. If successful, you will be logged into the remote server and see a shell prompt.

$ ssh bandit0@bandit.labs.overthewire.org -p 2220
                         _                     _ _ _
                        | |__   __ _ _ __   __| (_) |_
                        | '_ \ / _` | '_ \ / _` | | __|
                        | |_) | (_| | | | | (_| | | |_
                        |_.__/ \__,_|_| |_|\__,_|_|\__|


                      This is an OverTheWire game server.
            More information on http://www.overthewire.org/wargames

bandit0@bandit.labs.overthewire.org's password:

Welcome to OverTheWire!
------------
  Enjoy your stay!

bandit0@bandit:~$

Next Level : Level 0 -> 1

Bandit Level 12 -> Level 13

jaws99 — Thu, 3 Oct 2024 17:15:37 +0900

Level Goal

The password for the next level is stored in the file data.txt, which is a hexdump of a file that has been repeatedly compressed. For this level it may be useful to create a directory under /tmp in which you can work. Use mkdir with a hard to guess directory name. Or better, use the command “mktemp -d”. Then copy the datafile using cp, and rename it using mv (read the manpages!)

Commands you may need to solve this level

grep, sort, uniq, strings, base64, tr, tar, gzip, bzip2, xxd, mkdir, cp, mv, file

`xxd` is used to create a hex dump of a file or standard input.
`tar`, `bzip2`, and `gzip` are used for working with archives and compressing files.

Helpful Reading Material

Hex dump on Wikipedia

Write up

bandit12@bandit:~$ ls
data.txt
bandit12@bandit:~$ cat data.txt
00000000: 1f8b 0808 dfcd eb66 0203 6461 7461 322e  .......f..data2.
00000010: 6269 6e00 013e 02c1 fd42 5a68 3931 4159  bin..>...BZh91AY
00000020: 2653 59ca 83b2 c100 0017 7fff dff3 f4a7  &SY.............
......

There is a hexdump file that we can read.

bandit12@bandit:~$ xxd -r data.txt > data.bin
-bash: data.bin: Permission denied

Using the `xxd -r` option, we can convert the hexdump file into binary. However, we don't have permission to write the file in this directory.

bandit12@bandit:~$ mktemp -d
/tmp/tmp.cbKQ3E12KS
bandit12@bandit:~$ cd /tmp/tmp.cbKQ3E12KS
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ cp ~/data.txt ./
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ ls
data.txt
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ xxd -r data.txt > data.bin
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ ls
data.bin  data.txt

By using the `mktemp` command, we can create a directory with write permissions.

bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ file data.bin
data.bin: gzip compressed data, was "data2.bin", last modified: Thu Sep 19 07:08:15 2024, max compression, from Unix, original size modulo 2^32 574
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ mv data.bin data.bin.gz
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ gzip -d data.bin.gz
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ ls
data.bin  data.txt
------------------------------------------------------
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ file data.bin
data.bin: bzip2 compressed data, block size = 900k
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ mv data.bin data.bin.bz2
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ bzip2 -d data.bin.bz2
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ ls
data.bin  data.txt
-------------------------------------------------------
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ file data.bin
data.bin: gzip compressed data, was "data4.bin", last modified: Thu Sep 19 07:08:15 2024, max compression, from Unix, original size modulo 2^32 20480
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ mv data.bin data.bin.gz
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ gzip -d data.bin.gz
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ ls
data.bin  data.txt
--------------------------------------------------------
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ file data.bin
data.bin: POSIX tar archive (GNU)
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ mv data.bin data.bin.tar
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ tar -xf data.bin.tar
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ ls
data5.bin  data.bin.tar  data.txt
---------------------------------------------------------
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ file data5.bin
data5.bin: POSIX tar archive (GNU)
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ mv data5.bin data5.bin.tar
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ tar -xf data5.bin.tar
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ ls
data5.bin.tar  data6.bin  data.bin.tar  data.txt
-----------------------------------------------------------
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ file data6.bin
data6.bin: bzip2 compressed data, block size = 900k
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ mv data6.bin data6.bin.bz
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ bzip2 -d data6.bin.bz
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ ls
data5.bin.tar  data6.bin  data.bin.tar  data.txt
-------------------------------------------------------------
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ file data6.bin
data6.bin: POSIX tar archive (GNU)
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ mv data6.bin data6.bin.tar
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ tar -xf data6.tar
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ ls
data5.bin.tar  data6.bin.tar  data8.bin  data.bin.tar  data.txt
------------------------------------------------------------------
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ file data8.bin
data8.bin: gzip compressed data, was "data9.bin", last modified: Thu Sep 19 07:08:15 2024, max compression, from Unix, original size modulo 2^32 49
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ mv data8.bin data8.bin.gz
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ gzip -d data8.bin.gz
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ ls
data5.bin.tar  data6.bin.tar  data8.bin  data.bin.tar  data.txt
-----------------------------------------------------------------
bandit12@bandit:/tmp/tmp.cbKQ3E12KS$ cat data8.bin
The password is FO5dwFsc0cbaIiH0h8J2eUks2vdTDwAn

After completing repetitive file decompression, we can finally retrieve the password.

Next Level : Level 13 -> 14

Bandit Level 11 -> Level 12

jaws99 — Fri, 13 Sep 2024 17:52:36 +0900

Level Goal

The password for the next level is stored in the file data.txt, where all lowercase (a-z) and uppercase (A-Z) letters have been rotated by 13 positions

Commands you may need to solve this level

grep, sort, uniq, strings, base64, tr, tar, gzip, bzip2, xxd

`tr` is used to translate or delete characters from the input text.

Helpful Reading Material

Rot13 on Wikipedia

Write up

bandit11@bandit:~$ ls
data.txt
bandit11@bandit:~$ cat data.txt
Gur cnffjbeq vf 7k16JArUVv5LxVuJfsSVdbbtaHGlw9D4

There is a file encoded in ROT13, which replaces each letter with the 13th letter after it in the alphabet. When we use the `cat` command to view its content, it shows an unreadable combination of strings, similar to the previous challenge.

By checking the ROT13 Wikipedia page, we find a way to implement ROT13 using the `tr` command. The expression 'A-Za-z' 'N-ZA-Mn-za-m' maps uppercase letters A-Z to N-ZA-M, and lowercase letters similarly. Reversing this code will rerotate it back to the original text.

bandit11@bandit:~$ cat data.txt | tr 'N-ZA-Mn-za-m' 'A-Za-z'
The password is 7x16WNeHIi5YkIhWsfFIqoognUTyj9Q4

By relocating both uppercase and lowercase letters, we can finally retrieve the password!

Next Level : Level 12 -> 13

Bandit Level 10 -> Level 11

jaws99 — Wed, 11 Sep 2024 16:55:32 +0900

Level Goal

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

Commands you may need to solve this level

grep, sort, uniq, strings, base64, tr, tar, gzip, bzip2, xxd

`base64` is used to encode or decode a file or standard input and output the result to standard output.

Helpful Reading Material

Base64 on Wikipedia

Write up

bandit10@bandit:~$ ls
data.txt
bandit10@bandit:~$ cat data.txt
VGhlIHBhc3N3b3JkIGlzIGR0UjE3M2ZaS2IwUlJzREZTR3NnMlJXbnBOVmozcVJyCg==

There is a file encoded in base64, and when we use the `cat` command to view its content, it shows an unreadable combination of strings.

-d, --decode
	decode data

By using `man base64` or `base64 --help` to view the options, we'll find that the `-d` option is used to decode the data.

bandit10@bandit:~$ base64 -d data.txt
The password is dtR173fZKb0RRsDFSGsg2RWnpNVj3qRr

With this, we can easily find the password.

bandit10@bandit:~$ echo 'The password is dtR173fZKb0RRsDFSGsg2RWnpNVj3qRr' | base64
VGhlIHBhc3N3b3JkIGlzIGR0UjE3M2ZaS2IwUlJzREZTR3NnMlJXbnBOVmozcVJyCg==

Using `base64` to encode data doesn't require any options; the encoded output will still represent the same content as the original file.

Next Level : Level 11 -> 12

Bandit Level 9 -> Level 10

jaws99 — Mon, 9 Sep 2024 18:34:20 +0900

Level Goal

The password for the next level is stored in the file data.txt in one of the few human-readable strings, preceded by several ‘=’ characters.

Commands you may need to solve this level

grep, sort, uniq, strings, base64, tr, tar, gzip, bzip2, xxd

`strings` is used to display the printable characters from files.

Write up

bandit9@bandit:~$ ls
data.txt
bandit9@bandit:~$ cat data.txt
P>1#w^) a  %b2ck7 l1 X 8_#@ 5HXaP0ٿ֗#mB}hF4 ڐc 4s%5    P3%A<.d 
|諭< k!G#rP23/         . 4˒Pm!(Ys^1(QЕt~ ݰo8 }"I2Ӥі-Er4].n qtg8Wq{ $"M ~^u-omc]/ʔE 0J9^ .;64.3 ,F~V~! 3^ rG~nxדSLșwC=Bo eډ"̺56v1 k y0G8 \[oTIY.jJy + o "h2ՙ^$ C T2!}GϏlESu ce0 , %>fH<ؒ {y W4 o#Jw aK=CzY@R|u `
\ 4 " I+0{o砪" q킃@2Svb %w M r_8 C¯ ! /|S/F A݂R2A^K>7]]1 lxZe ߋWaB|��= $9u`}ǐ wx9s=, Ԇ
>a Jt{V o|*^ | ^ j) =O$<2 fϲ \a!;========== the i gnEi"ǵa ;'^rO VQ 5F oT? r9   (e} 7p{zyl:b`��/` ۀn}^ 2nġS{I/} I,WzD<> &iQ*G ca٤Mew S nЪL2@F bF W 4>^^TdjL BY+m _eh ξ5|.PWAF=16VA`
p )#Y[0uTN3A&؛+^Y9:ֻ F jBJ2$> Ք n;\Z` 01Si* y: v.BԄd " b9X;/^8@- hl?J.
......

There is a file where we need to find strings that appear next to several "=" characters. However, when we use the `cat` command to view the content, it contains many non-human-readable strings.

bandit9@bandit:~$ strings data.txt
#mB}hF
3%A<.
~^u-
0J9^
;64.3
,F~V
IY.j
T yb

Therefore, the `strings` command is ideal for this challenge, as it lets us view only the human-readable strings in the file.

bandit9@bandit:~$ strings data.txt  | grep "="
=aA"f
\a!;========== the
PWAF=1
         M),\}=
2Y6=
G';?e=
========== passwordf
========== isc
*=N6
m=</
E=Bty
=sw
"M1=
========== FGUW5ilLVJrxX9kMYMmlN4MgbpfMiqey
!&=u&4$
*XA=

There are a few possible options for the password: "the," "passwordf," "isc," and "FGU*." However, based on the patterns we've seen in OverTheWire, we can conclude that the last one is the correct password.

Next Level : Level 10 -> 11

Bandit Level 8 -> Level 9

jaws99 — Sun, 8 Sep 2024 19:04:14 +0900

Level Goal

The password for the next level is stored in the file data.txt and is the only line of text that occurs only once

Commands you may need to solve this level

grep, sort, uniq, strings, base64, tr, tar, gzip, bzip2, xxd

`sort` is used to output a sorted concatenation of all files to the standard output.
`uniq` is used to filter out adjacent duplicate lines from the input.

Helpful Reading Material

Piping and Redirection

Write up

bandit8@bandit:~$ ls
data.txt
bandit8@bandit:~$ cat data.txt
riAxnw3RnsFuQiOD8BlZbR6TlERU9866
pJyx6KXXkALfk2n5VSyWS4fqKvnyuN8G
tAw9D85F6PkUdTdlCwmRWYlQNPbkcVox
WWKtMcgokvQfZKjkt2yfJDtMMclL3cMn
fYJtDkXtfgl2A0r3iOlMNrmmCePl568B
.....

There is a file where we need to find a word that appears only once, but the content is too long to search manually. This time, we can't use the `grep` command because we don't know a specific pattern to match. However, we have a clue: the text appears only one time.

bandit8@bandit:~$ uniq -c data.txt
	1 riAxnw3RnsFuQiOD8BlZbR6TlERU9866
	1 pJyx6KXXkALfk2n5VSyWS4fqKvnyuN8G
	1 tAw9D85F6PkUdTdlCwmRWYlQNPbkcVox
	1 WWKtMcgokvQfZKjkt2yfJDtMMclL3cMn
	1 fYJtDkXtfgl2A0r3iOlMNrmmCePl568B
	.......

The `uniq` command is suitable for this challenge. By using the `-c` option, we can see how many times each line occurs. However, since `uniq` only filters adjacent matching lines, we need to sort the file first to make it effective.

bandit8@bandit:~$ sort data.txt | uniq -c
	10 0KCctkqCfY7BIOWqolXsHDaboXVTKZ49
	10 1SKCEfQ151hWOx9JkeIAmOQdXiC813h1
	10 3hHLofjM7m3sdyiKJF5QsMqvEIfFh5b1
 	10 3hW8tLnDV8acjhTQi44CKXEzHsJb3sqz
	10 3nUXvAjKo7yu6fYykYu7nGGKDMuNMWZf
	10 42qjuz5hdLlItNwdJYsDRpkbbvoEYiWK
	 1 4CKMh1JI91bUIZZPXDqGanal4xvAg0JM
	10 5g2sV4OokwqDv29Pfo6C7twjKcOk4WQV
	10 5YlL2xxyEUqV6tF0P6NoHt8LOY2EGEcO
	10 6lMDNhQjlOoCOZ5F8ULK2g0uT0rCdnoQ
	......

bandit8@bandit:~$ sort data.txt | uniq -u
4CKMh1JI91bUIZZPXDqGanal4xvAg0JM

We can utilize the `uniq` command in two ways. First, by using the `-c` option to check how many times each line occurs. Second, by using the `-u` option to print only the unique lines. This will help us find the password!

Next Level : Level 9 -> 10

Bandit Level 7 -> Level 8

jaws99 — Sat, 7 Sep 2024 19:02:25 +0900

Level Goal

The password for the next level is stored in the file data.txt next to the word millionth

Commands you may need to solve this level

man, grep, sort, uniq, strings, base64, tr, tar, gzip, bzip2, xxd

`grep` is used to search for patterns within files.

Write up

bandit7@bandit:~$ ls
data.txt
bandit7@bandit:~$ cat data.txt
Togo's  zMSk3jmZQL6OHd0BnkBcantGvGbTuyDR
loader  6kP31IsFVItYVYIulUxVorvHQpct2F6A
horseradish's   LAD77UITMQFCxqRiAAO6KNSCRUaqdQJ4
Savoyard        uKtULf3kVyUGKd1KBE0O6JVvXtkrapBe
Keller's        BG48vRqDH3HjHDDk5ZEivyz7Q5Ex4qCU
.................

There is a file where we need to find the word 'millionth,' but the content is too long to search line by line.

bandit7@bandit:~$ cat data.txt | grep millionth
millionth       dfwvzFQi4mU0wfNbFOe9RoWskMLg7eEc

By using the `grep` command to match the pattern, we can quickly find the content and retrieve the password!

Next Level : Level 8 -> 9

Bandit Level 6 -> Level 7

jaws99 — Fri, 6 Sep 2024 14:30:05 +0900

Level Goal

The password for the next level is stored somewhere on the server and has all of the following properties:

owned by user bandit7
owned by group bandit6
33 bytes in size

Commands you may need to solve this level

ls , cd , cat , file , du , find , grep

Write up

-user uname
	File is owned by user uname (numeric user ID allowed).
    
-group gname
	File belongs to group gname (numeric group ID allowed).

-size n[cwbkMG]
	File uses less than, more than or exactly n units of space, rounding up.  The following suffixes can be used:
    	`c'    for bytes

We can use the command `man find` to explore the available options for this task.

bandit6@bandit:~$ find / -user "bandit7"
find: ‘/sys/kernel/tracing’: Permission denied
find: ‘/sys/kernel/debug’: Permission denied
find: ‘/sys/fs/pstore’: Permission denied
find: ‘/sys/fs/bpf’: Permission denied
/sys/fs/cgroup/user.slice/user-11007.slice/user@11007.service
/sys/fs/cgroup/user.slice/user-11007.slice/user@11007.service/cgroup.procs
/sys/fs/cgroup/user.slice/user-11007.slice/user@11007.service/cgroup.threads
/sys/fs/cgroup/user.slice/user-11007.slice/user@11007.service/app.slice
/sys/fs/cgroup/user.slice/user-11007.slice/user@11007.service/app.slice/cgroup.events
/sys/fs/cgroup/user.slice/user-11007.slice/user@11007.service/app.slice/memory.events
/sys/fs/cgroup/user.slice/user-11007.slice/user@11007.service/app.slice/io.pressure
......

When searching through many files, we might encounter `Permission denied` messages, indicating that we don't have permission to read those files. But how can we ignore these messages? By adding `2>/dev/null` to the end of the find command, we tell the shell to redirect error messages to /dev/null, preventing them from appearing on the screen.

bandit6@bandit:~$ find / -user "bandit7" 2>/dev/null
/sys/fs/cgroup/user.slice/user-11007.slice/user@11007.service
/sys/fs/cgroup/user.slice/user-11007.slice/user@11007.service/cgroup.procs
/sys/fs/cgroup/user.slice/user-11007.slice/user@11007.service/cgroup.threads
/sys/fs/cgroup/user.slice/user-11007.slice/user@11007.service/app.slice
/sys/fs/cgroup/user.slice/user-11007.slice/user@11007.service/app.slice/cgroup.events
/sys/fs/cgroup/user.slice/user-11007.slice/user@11007.service/app.slice/memory.events

We've successfully suppressed the 'Permission denied' message.

bandit6@bandit:~$ find / -user "bandit7" -group "bandit6" 2>/dev/null
/var/lib/dpkg/info/bandit7.password

The next condition is that the file belongs to the bandit6 group. We can find one such file.

bandit6@bandit:~$ find / -user "bandit7" -group "bandit6" -size 33c 2>/dev/null
/var/lib/dpkg/info/bandit7.password

To meet all the criteria, we also need to check the file size.

bandit6@bandit:~$ cat /var/lib/dpkg/info/bandit7.password
morbNTDkSW6jIlUc0ymOdMaLnOlFVAaj

Finally, we can find the password!

Next Level : Level 7 -> 8

Bandit Level 5 -> Level 6

jaws99 — Fri, 16 Aug 2024 17:05:36 +0900

Level Goal

The password for the next level is stored in a file somewhere under the inhere directory and has all of the following properties:

human-readable
1033 bytes in size
not executable

Commands you may need to solve this level

ls , cd , cat , file , du , find

Write up

bandit5@bandit:~$ ls
inhere
bandit5@bandit:~$ cd inhere/
bandit5@bandit:~/inhere$ ls
maybehere00  maybehere03  maybehere06  maybehere09  maybehere12  maybehere15  maybehere18
maybehere01  maybehere04  maybehere07  maybehere10  maybehere13  maybehere16  maybehere19
maybehere02  maybehere05  maybehere08  maybehere11  maybehere14  maybehere17
bandit5@bandit:~/inhere$ ls -a maybehere*
maybehere00:
.  ..  -file1  .file1  -file2  .file2  -file3  .file3  spaces file1  spaces file2  spaces file3

maybehere01:
.  ..  -file1  .file1  -file2  .file2  -file3  .file3  spaces file1  spaces file2  spaces file3

In the `inhere` directory, there are many files. How can we find the specific one?

bandit5@bandit:~/inhere$ find . -type f -exec file {} \;
./maybehere07/-file3: data
./maybehere07/spaces file2: ASCII text, with very long lines (9063)
........

bandit5@bandit:~/inhere$ find . -type f -exec file {} \;  | grep -i text
./maybehere07/spaces file2: ASCII text, with very long lines (9063)
./maybehere07/-file2: ASCII text, with very long lines (2487)

First, we can find human-readable file by using the `-type`, `-exec` options and the `grep` command. `find . type -f` means searching for all files from the current directory and all its subdirectories. `-exec file {} \;` means that for each file found, the `file` command is excuted. `{}` is replaced with the file name, and `\;` ends the `-exec` command. Additionally, by using the `grep` command, we can exclude files that are not of the text types.

bandit5@bandit:~/inhere$ find . -type f -size 1033c -exec file {} \;  | grep -i text
./maybehere07/.file2: ASCII text, with very long lines (1000)

Next, by using the `-size` options, we can find files that are exactly 1033 bytes in size. The `-size` options specifies that the file uses less than, more than or exactly a specified number of units of space, with `c` indicating bytes.

bandit5@bandit:~/inhere$ find . -type f ! -perm /111 -size 1033c -exec file {} \;  | grep -i text
./maybehere07/.file2: ASCII text, with very long lines (1000)

Lastly, by using the `-perm` options, we can search for files that have any of the excute permissions set for the owner, group, or others. However, `! -perm` searches for files that do not have any of the excute permissions set for the owner, group, or others. The `!` before the options negates the condition. Therefore, `find ! -perm /111` will find files where none of the excute permissions are set for the owner, group, or others.

bandit5@bandit:~/inhere$ cat ./maybehere07/.file2
HWasnPhtq9AVKe0dmk45nxy20cvUa6EG

Finally, we can find the password!

Next Level : Level 6 -> 7