Jan 8, 2020 07:37 PM
(This post was last modified: Jan 8, 2020 07:38 PM by luucy.)
This will require you to have some knowledge of back-end programming, you'll be creating a whitelist of unique links to send out to your victims and a blacklist for blocking data center ip addresses.
1.) Gain an understanding of the ip ranges that your victim's email providers are using. You can do this by Googling something like "Google ip ranges" (Replacing Google with the company that your victim is using for email. If you are advertising your page on an ad platform it's important to learn your advertiser platforms ip ranges.
2.) Write a database table called whitelist which has a UUID, IP Address (default to null), session time (in seconds, default to null), and connect time (default to null).
3.) Write a database table called blacklist which has a UUID and IP Address.
4.) Write an endpoint on your HTTP/S server which is called /redirect or something similar. Have it take in a GET parameter called UUID. When someone connects to the endpoint it will check the blacklist for their IP (and redirect them to a different site if blacklisted). If not blacklisted it will use the UUID passed in the GET request to check the whitelist table in the database. If whitelisted it will update the connect time to the current date and set a cookie containing their UUID and redirect to the main page of your site.
5.) Write middleware for your HTTP/S server which checks every request if the user is blacklisted, if not then check if the UUID is in the whitelist table and if the session time is greater than the total time since the first connect time assuming you want to limit the amount of time they can visit your page. If the session time is is less than the time since they first visited the page or the IP address doesn't match what's in the whitelist table for that UUID then you redirect to a different site and add them to the blacklist.
6.) Write a script which takes in a list of your victim emails, generates a UUID for each of them, and imports them into the whitelist table and outputs the UUID's into a file to be processed by your mass mailer.
7.) Mass mail using an email template with a UUID variable to be used to create a unique link for each victim. If the victim reports the email as spam and the provider tries to check the site they should be redirected to a valid website. If the victim reports the link in the email to SpamHaus they won't do anything because there is nothing hosted on the site because their IP address isn't whitelisted.
Pro tip 1: If you are hosting any content on your HTTP/S server that will be used in the email campaign ensure your middleware isn't wrapped around the routes hosting the content. Otherwise your victims will not be able to load the CSS or Images hosted!
Pro tip 2: Add a robots.txt with the following code
This will ensure that all compliant bots don't visit your site if they scrape the link from the email and their ip range isn't blocked. If you don't do this it could result in your victims being locked out of the page.
Enjoy,
Lucy 🎉
1.) Gain an understanding of the ip ranges that your victim's email providers are using. You can do this by Googling something like "Google ip ranges" (Replacing Google with the company that your victim is using for email. If you are advertising your page on an ad platform it's important to learn your advertiser platforms ip ranges.
2.) Write a database table called whitelist which has a UUID, IP Address (default to null), session time (in seconds, default to null), and connect time (default to null).
3.) Write a database table called blacklist which has a UUID and IP Address.
4.) Write an endpoint on your HTTP/S server which is called /redirect or something similar. Have it take in a GET parameter called UUID. When someone connects to the endpoint it will check the blacklist for their IP (and redirect them to a different site if blacklisted). If not blacklisted it will use the UUID passed in the GET request to check the whitelist table in the database. If whitelisted it will update the connect time to the current date and set a cookie containing their UUID and redirect to the main page of your site.
5.) Write middleware for your HTTP/S server which checks every request if the user is blacklisted, if not then check if the UUID is in the whitelist table and if the session time is greater than the total time since the first connect time assuming you want to limit the amount of time they can visit your page. If the session time is is less than the time since they first visited the page or the IP address doesn't match what's in the whitelist table for that UUID then you redirect to a different site and add them to the blacklist.
6.) Write a script which takes in a list of your victim emails, generates a UUID for each of them, and imports them into the whitelist table and outputs the UUID's into a file to be processed by your mass mailer.
7.) Mass mail using an email template with a UUID variable to be used to create a unique link for each victim. If the victim reports the email as spam and the provider tries to check the site they should be redirected to a valid website. If the victim reports the link in the email to SpamHaus they won't do anything because there is nothing hosted on the site because their IP address isn't whitelisted.
Pro tip 1: If you are hosting any content on your HTTP/S server that will be used in the email campaign ensure your middleware isn't wrapped around the routes hosting the content. Otherwise your victims will not be able to load the CSS or Images hosted!
Pro tip 2: Add a robots.txt with the following code
Code
User-agent: *
Disallow: /This will ensure that all compliant bots don't visit your site if they scrape the link from the email and their ip range isn't blocked. If you don't do this it could result in your victims being locked out of the page.
Enjoy,
Lucy 🎉
![[Image: efd2Awe.png]](https://i.imgur.com/efd2Awe.png)