Someone give me instructions so that my phishing lives longer on the air, please. It would be of great help to me. I'm doing the spam by text message
-
XSS.stack #1 – первый литературный журнал от юзеров форума
Tips for my scam to last much longer online
- Автор темы batman777
- Дата начала
allow only mobile traffic, use antibots, and allow ip per country you send to.
- Автор темы
- Добавить закладку
- #3
Would you help me I have no idea how to do what you tell me
pm with your contact.
- Автор темы
- Добавить закладку
- #5
i send pm you
create session tokens for each spamming session. every email/sms sent gets their own unique token along with another token for the actual campaign. only display the phishing page when someone visits their unique token and after an hour have it expire, remove it from the db so it can't be viewed again.
if they don't enter data within the first hour, they won't enter it later either. after a few hours, shut down the entire campaign token, since if they haven't visited the url within the first few hours, they won't visit it later and if they do, it's probably being analyzed for malicious content and/or has been reported. don't redirect out if either individual session/campaign token are expired as it can be a red flag for the browser, just display a fake legal page. once individual session token is expired, block IP as well.
add header checks for web crawlers to block them. block known ip ranges for crawlers/bots. check IP for vpn/proxy, etc. if you're sms spamming, check IP ISP and only allow residential/mobile data.
check for unusual data being entered that matches someone checking your site's folder indexes, entering unique characters into username/GET parameters in url, etc and auto ban IP and disable session token if so... since someone was snooping around looking for vulnerabilities/errors/responses/etc...
host all of the main files on a CDN so you can easily create new disposable domains as you create new campaigns and either mirror the pages or iframe. this way you don't have to constantly reupload everything once one page gets caught and only sacrifice the bounce domain.
URI encode the html, obfuscate it, host all images/etc as base64 to help prevent client side browser sandbox catching it automatically with heuristic techniques. use js for your POST request to send credentials to your CDN domain for data collection, that way no PHP is needed and the entire phish is a single html page for easy migration and can spreading with agility/numerous ways.
...etc, just think about your target audience, who you're trying to avoid and how to determine if it's them.
if they don't enter data within the first hour, they won't enter it later either. after a few hours, shut down the entire campaign token, since if they haven't visited the url within the first few hours, they won't visit it later and if they do, it's probably being analyzed for malicious content and/or has been reported. don't redirect out if either individual session/campaign token are expired as it can be a red flag for the browser, just display a fake legal page. once individual session token is expired, block IP as well.
add header checks for web crawlers to block them. block known ip ranges for crawlers/bots. check IP for vpn/proxy, etc. if you're sms spamming, check IP ISP and only allow residential/mobile data.
check for unusual data being entered that matches someone checking your site's folder indexes, entering unique characters into username/GET parameters in url, etc and auto ban IP and disable session token if so... since someone was snooping around looking for vulnerabilities/errors/responses/etc...
host all of the main files on a CDN so you can easily create new disposable domains as you create new campaigns and either mirror the pages or iframe. this way you don't have to constantly reupload everything once one page gets caught and only sacrifice the bounce domain.
URI encode the html, obfuscate it, host all images/etc as base64 to help prevent client side browser sandbox catching it automatically with heuristic techniques. use js for your POST request to send credentials to your CDN domain for data collection, that way no PHP is needed and the entire phish is a single html page for easy migration and can spreading with agility/numerous ways.
...etc, just think about your target audience, who you're trying to avoid and how to determine if it's them.
interesting,
Hmm, very interesting suggestion. The only downside is that you might loose some who are coming from notebooks.
if you use traffic from sms spam then will be only mobile traffic, so no need for allowing other type of traffic.
"I'm doing the spam by text message" -> he said is doing sms so acording to his words will help.
of course, nothing can help regarding manual reports but for bots is a nice solution, it helps, all depends of page if is old, domains used( old is better ), never put files directly on root folder and so on.
Последнее редактирование:
for allow only mobile , you can detect pc or mobile from user agent or from screen wide
allow ip per country : you can use cloudflare to block countries you are not targeting
use robots.txt to to block google spiders to crawel your site
any anitbot solution will filter traffic based on devices, type and will allow traffic per country.
Yeb that's true he also could use cloudflare