Drew hoodoer

## List of IP Reputation Checking Services.txt
https://whatismyipaddress.com/blacklist-check

https://ipcheck.proofpoint.com/

https://www.ipvoid.com/ip-blacklist-check/


https://talosintelligence.com/reputation_center

https://www.cyren.com/security-center/cyren-ip-reputation-check

## Landing Page.html
Hello! Two step CSRF coming up...
<iframe src="step1.html" width="0" height="0">
</iframe>
<iframe src="step2.html"  width="0" height="0">
</iframe>

## csrfPoc.js
function start()
{
	alert("Start?");
}


function sendRequests()
{
	// Setup the payment

## landingPage.html
<html>
    <head>
        <script language="javascript">

            window.onload = function() {
                document.getElementById("csrfForm1").submit();
                // to make 2nd form wait for 1st, put the following in a function and use as a callback for a new timer
                document.getElementById("csrfForm2").submit();
            }

## gobusterCommands.txt
Using the proxy (burp) can result in rediculously huge project files. You've been warned.

gobuster  dir  -u https://SOMEURL.com -w /some/word/list.txt -p http://localhost:8080 -k -l


gobuster  dir  -u https://SOMEURL.com -w /some/word/list.txt -k -l

If you can use --wildcard if it's choking on responses, however if it's sending back 302's for nonexistant,
just change up the accepted status codes:
gobuster  dir  -u https://SOMNEURL.com -w /som/word/list.txt -k -l -s 200,204,301,307,401,403

## updateGitProjects.sh
#!/bin/bash

for i in `ls -d */`; do cd $i && git pull && cd ..; done

## Set cookie from console
For session high-jacking:
javascript:void(document.cookie="COOKIENAME=COOKIEVALUE");

## wireguardRoutingSnippet.txt
ufw route allow in on wg0s out on eth0

## Chromium startup parameters
chromium  --no-sandbox  --proxy-server="http://127.0.0.1:8080" --disable-xss-auditor &

## Tor ghost auto IP switching.txt
So use a simple watch -n 30 torghost switch

That'll get you regular new IP addresses.

To log the IP addresses isn't as clean, do this (make sure you proxy through burp, and have Burp configured to use Tor proxy)
watch -n 15 -t curl --proxy http://127.0.0.1:8080 -s ipinfo.io/ip >> torSourceIPs.txt

Due to weird formatting, you'll often not actually see those IP addresses if you cat the file, but they're there if you open it in sublime or something.

You can grep them out cleanly with this:
	https://whatismyipaddress.com/blacklist-check

	https://ipcheck.proofpoint.com/

	https://www.ipvoid.com/ip-blacklist-check/


	https://talosintelligence.com/reputation_center

	https://www.cyren.com/security-center/cyren-ip-reputation-check
	Hello! Two step CSRF coming up...
	<iframe src="step1.html" width="0" height="0">
	</iframe>
	<iframe src="step2.html" width="0" height="0">
	</iframe>
	function start()
	{
	alert("Start?");
	}



	function sendRequests()
	{
	// Setup the payment
	<html>
	<head>
	<script language="javascript">

	window.onload = function() {
	document.getElementById("csrfForm1").submit();
	// to make 2nd form wait for 1st, put the following in a function and use as a callback for a new timer
	document.getElementById("csrfForm2").submit();
	}
	Using the proxy (burp) can result in rediculously huge project files. You've been warned.

	gobuster dir -u https://SOMEURL.com -w /some/word/list.txt -p http://localhost:8080 -k -l


	gobuster dir -u https://SOMEURL.com -w /some/word/list.txt -k -l

	If you can use --wildcard if it's choking on responses, however if it's sending back 302's for nonexistant,
	just change up the accepted status codes:
	gobuster dir -u https://SOMNEURL.com -w /som/word/list.txt -k -l -s 200,204,301,307,401,403
	#!/bin/bash

	for i in `ls -d */`; do cd $i && git pull && cd ..; done
	So use a simple watch -n 30 torghost switch

	That'll get you regular new IP addresses.

	To log the IP addresses isn't as clean, do this (make sure you proxy through burp, and have Burp configured to use Tor proxy)
	watch -n 15 -t curl --proxy http://127.0.0.1:8080 -s ipinfo.io/ip >> torSourceIPs.txt

	Due to weird formatting, you'll often not actually see those IP addresses if you cat the file, but they're there if you open it in sublime or something.

	You can grep them out cleanly with this: