GTFOBins is a curated list of Unix binaries that can be used to bypass local security restrictions in misconfigured systems.

The project collects legitimate functions of Unix binaries that can be abused to get the f**k break out restricted shells, escalate or maintain elevated privileges, transfer files, spawn bind and reverse shells, and facilitate the other post-exploitation tasks.

It is important to note that this is not a list of exploits, and the programs listed here are not vulnerable per se, rather, GTFOBins is a compendium about how to live off the land when you only have certain binaries available.

GTFOBins is a collaborative project created by Emilio Pinna and Andrea Cardaci where everyone can contribute with additional binaries and techniques.

If you are looking for Windows binaries you should visit LOLBAS.

Si vous gérer des serveurs ou différents services pour le compte de clients, il peut-être intéressant de mettre à leur disposition une page récapitulant l'état de fonctionnement de ces services.

C'est ce que propose SystemStatus, un script PHP sous licence Creative Commons qui s'installe très rapidement sur un serveur et qui permet de configurer un ensemble de systèmes à surveiller. Ensuite, lorsqu'un problème arrive ou qu'un ticket de maintenance est créé, le status change.

Mauya!

We tried to learn other languages, but since we didn't find a for them it might not say "Welcome". We extend our deepest apologies.
How do I use this thing?

See the input box by the logo? Just type in a command and see the magic happen!

Try osx/say, linux/du, or simply man.

Some commands are widely available with the same interface, some other have variants per operating system. Currently the tldr-pages project splits comman into 4 categories: common, linux, osx, and sunos.

du, for example, is available under both linux and osx.
What is ?

This is a web client for a project called tldr-pages; they are a community effort to simplify the beloved man pages with practical examples.

Links of malware hack check tools :

• Loki
• phpscanner
• php-malware-finder
• php-malware-scanner
• Yasca
• acunetix
• RIPS-scanner
• nikto2
• phpsecaudit
• sectools
• phpsec

Loki

Simple IOC Scanner
Scanner for Simple Indicators of Compromise

phpscanner

PHP scanner written in Python for identifying PHP backdoors and php malicious code. This tool is mainly reusing below mentioned tools. To use this tool, you need to install yara library for Python from the source.

php-malware-finder

Does its very best to detect obfuscated/dodgy code as well as files using PHP functions often used in malwares/webshells. Detection is performed by crawling the filesystem and testing files against a set of YARA rules.

php-malware-scanner

Scans the current working directory and display results with the score greater than the given value. Released under the MIT license.

Yasca (GitHub)

an open source program which looks for security vulnerabilities, code-quality, performance, and conformance.

acunetix Web Security Scanner

Acunetix WVS automatically checks your web applications for SQL Injection, XSS & other web vulnerabilities.

RIPS

A static source code analyser for vulnerabilities in PHP .scripts

nikto2

an open source web server scanner which performs comprehensive tests against web servers for multiple items, including potentially dangerous files/program.

ClamAV extension for PHP (php-clamav) - a fork of the php-clamavlib project allows to incorporate virus scanning features in your PHP scripts.

Older projects: securityscanner, phpsecaudit.

Check also the following security websites:

sectools.org

phpsec.org PHP Security Consortium

    Founded in January 2005, the PHP Security Consortium (PHPSC) is an international group of PHP experts dedicated to promoting secure programming practices within the PHP community. Members of the PHPSC seek to educate PHP developers about security through a variety of resources, including documentation, tools, and standards.

Go See it on GitHub

https:// clone URL it to Desktop:
git clone https://github.com/bashawesome/bashunixshell-awesome.git
SSH clone URL it to Desktop:
git clone git@github.com:bashawesome/bashunixshell-awesome.git

Burp Suite is the leading software for web security testing_
Thousands of organizations use Burp Suite to find security exposures before it’s too late.

wget http://repo.ajenti.org/debian/key -O- | apt-key add -

shellshocker
What is #shellshock?

Shellshock (CVE-2014-6271, CVE-2014-6277, CVE-2014-6278, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187) is a vulnerability in GNU's bash shell that gives attackers access to run remote commands on a vulnerable system. If your system has not updated bash in since Tue Sep 30 2014: 1:32PM EST (See patch history), you're most definitely vulnerable and have been since first boot. This security vulnerability affects versions 1.14 (released in 1994) to the most recent version 4.3 according to NVD.

You can use this website to test if your system is vulnerable, and also learn how to patch the vulnerability so you are no longer at risk for attack.

You can test if a system is vulnerable by using the form below. Just provide a http or https url and test away!
Url

Please test responsibly. All tests details are logged. Do not test against websites that you do not have permission to test against. All data is archived in case of abuse.

Here is an example script that is vulnerable. Place this in your /cgi-bin/shockme.cgi and try hitting it with the shock tester.

!/bin/bash

echo "Content-type: text/html"
echo ""
echo "https://shellshocker.net/"

Last updated Friday September 26th at 4:43PM EST: This website tester will now wait for a valid response before returning the state of the vulnerability. If the server responds with a 500 we assume you're vulnerable and we display the response immediately without waiting. If we get any other response code we will wait 3 seconds for a reply from your server and display if you're vulnerable or not.
Testing Your System

To test your system, you can simply run this one liner below to find if you're vulnerable.

curl https://shellshocker.net/shellshock_test.sh | bash

You can view the source of shellshock_test.sh on GitHub.

If you want to test each exploit individually without running the script above, feel free! They are listed below.
Exploit 1 (CVE-2014-6271)

There are a few different ways to test if your system is vulnerable to shellshock. Try running the following command in a shell.

env x='() { :;}; echo vulnerable' bash -c "echo this is a test"

If you see "vulnerable" you need to update bash. Otherwise, you should be good to go.
Exploit 2 (CVE-2014-7169)

Even after upgrading bash you may still be vulnerable to this exploit. Try running the following code.

env X='() { (shellshocker.net)=>\' bash -c "echo date"; cat echo; rm ./echo

If the above command outputs the current date (it may also show errors), you are still vulnerable.
Exploit 3 (???)

Here is another variation of the exploit. Please leave a comment below if you know the CVE of this exploit.

env X=' () { }; echo hello' bash -c 'date'

If the above command outputs "hello", you are vulnerable.
Exploit 4 (CVE-2014-7186)

bash -c 'true <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF <<EOF' ||
echo "CVE-2014-7186 vulnerable, redir_stack"

A vulnerable system will echo the text "CVE-2014-7186 vulnerable, redir_stack".
Exploit 5 (CVE-2014-7187)

(for x in {1..200} ; do echo "for x$x in ; do :"; done; for x in {1..200} ; do echo done ; done) | bash ||
echo "CVE-2014-7187 vulnerable, word_lineno"

A vulnerable system will echo the text "CVE-2014-7187 vulnerable, word_lineno".
Exploit 6 (CVE-2014-6278)

shellshocker='() { echo You are vulnerable; }' bash -c shellshocker

You shouldn't see "You are vulnerable", if you're patched you will see "bash: shellshocker: command not found"
Exploit 7 (CVE-2014-6277)

bash -c "f() { x() { ;}; x() { ;} <<a; }" 2>/dev/null || echo vulnerable

If the command outputs "vulnerable", you are vulnerable.

If you've tested your system, please leave a comment below. Don't forget to include your bash version and what OS you're running. Type bash --version for bash, and cat /etc/release for your OS.