axs2k/anubis
Reinforcement Learning • Updated
• 3
text stringlengths 5 3.08k | embedding sequence | tokens sequence | database stringclasses 5 values | file stringlengths 5 9 | chunk int64 0 192 |
|---|---|---|---|---|---|
[CLS] phishing methodologymethodology1. recon the victim1. select the victim domain. 2. perform some basic web enumeration searching for login portals used by the victim and decide which one you will impersonate. 3. use some osint to find emails. 2. prepare the environment1. buy the domain you are going to use for the phishing assessment2. configure the email service related records ( spf, dmarc, dkim, rdns ) 3. configure the vps with gophish3. prepare the campaign1. prepare the email template2. prepare the web page to steal the credentials4. launch the campaign! generate similar domain names or buy a trusted domaindomain name variation techniqueskeyword : the domain name contains an important keyword of the original domain ( e. g., zelster. com - management. com ). hypened subdomain : change the dot for a hyphen of a subdomain ( e. g., www - zelster. com ). new tld : same domain using a new tld ( e. g., zelster. org ) homoglyph : it replaces a letter in the domain name with letters that look similar ( e. g., zelfser. com ). transposition : it swaps two letters within the domain name ( e. g., zelster. com ). singularization / pluralization : adds or removes “ s ” at the end of the domain name ( e. g., zeltsers. com ). omission : it removes one of the letters from the domain name ( e. g., zelser. com ). repetition : it repeats one of the letters in the domain name ( e. g., zeltsser. com ). replacement : like homoglyph but less stealthy. it replaces one of the letters in the domain name, perhaps with a letter in proximity of the original letter on the keyboard ( e. g, zektser. com ). subdomained : introduce a dot inside the domain name ( e. g., ze. lster. com ). insertion : it inserts a letter into the domain name ( e. g., zerltser. com ). missing dot : append the tld to the domain name. ( e. g., zelstercom. com ) automatic toolsdnstwist | [
0.3702225983142853,
-0.11527068167924881,
0.04921624809503555,
0.3202267587184906,
-0.6187260746955872,
-0.12288230657577515,
-0.5233007073402405,
0.41072750091552734,
0.4721844494342804,
0.716263473033905,
0.22979018092155457,
-0.6318180561065674,
0.2707885503768921,
0.31109321117401123,
... | [
101,
13569,
12227,
16134,
11368,
6806,
3527,
6483,
2487,
1012,
28667,
2239,
1996,
6778,
2487,
1012,
7276,
1996,
6778,
5884,
1012,
1016,
1012,
4685,
2070,
3937,
4773,
4372,
17897,
8156,
6575,
2005,
8833,
2378,
27388,
2109,
2011,
1996,
6778,
... | hack_tricks | 10.txt | 0 |
##urlcrazywebsiteshttps : / / dnstwist. it / https : / / dnstwister. report / https : / / www. internetmarketingninjas. com / tools / free - tools / domain - typo - generator / bitflippingin the world of computing, everything is stored in bits ( zeros and ones ) in memory behind the scenes. this applies to domains too. for example, windows. com becomes 01110111... in the volatile memory of your computing device. however, what if one of these bits got automatically flipped due to a solar flare, cosmic rays, or a hardware error? that is one of the 0's becomes a 1 and vice versa. applying this concept to dns request, it's possible that the domain requested that arrives to the dns server isn't the same as the domain initially requested. for example a 1 bit modification in the domain windows. com can transform it into windnws. com. attackers may register as many bit - flipping domains as possible related to the victim in order to redirect legitimate users to their infrastructure. for more information read url a trusted domainyou can search in url for a expired domain that you could use. in order to make sure that the expired domain that you are going to buy has already a good seo you could search how is it categorized in : http : / / www. fortiguard. com / webfilterhttps : / / urlfiltering. paloaltonetworks. com / query / discovering emailshttps : / / github. com / laramies / theharvester ( 100 % free ) https : / / phonebook. cz / ( 100 % free ) https : / / maildb. io / https : / / hunter. io / https : / / anymailfinder. com / in order to discover more valid email addresses or verify the ones you have already discovered you can check if you can brute - force them smtp servers of the victim. learn how to verify / discover email address here. moreover, don't forget that if the users use any web portal to access their mails, you can check if it's vulnerable to username brute force, and exploit the vulnerability if possible. configuring gophishinstallationyou can download it from url and decompress it inside / opt / gophish and execute / opt / | [
0.07750155031681061,
-0.4057018756866455,
-0.05608614906668663,
0.4636824131011963,
-0.44682908058166504,
-0.468203604221344,
-0.3171080946922302,
0.5048789381980896,
0.16298773884773254,
1.063327431678772,
0.26178768277168274,
-0.5559447407722473,
0.3681957721710205,
-0.03675076737999916,... | [
3126,
15472,
20409,
2100,
8545,
5910,
7616,
11039,
25856,
2015,
1024,
1013,
1013,
1040,
23808,
9148,
3367,
1012,
2009,
1013,
16770,
1024,
1013,
1013,
1040,
23808,
9148,
6238,
1012,
3189,
1013,
16770,
1024,
1013,
1013,
7479,
1012,
4274,
2028... | hack_tricks | 10.txt | 1 |
gophish / gophish you will be given a password for the admin user in port 3333 in the output. therefore, access that port and use those credentials to change the admin password. you may need to tunnel that port to local : ssh - l 3333 : 127. 0. 0. 1 : 3333 < user > @ < ip > configurationtls certificate configurationbefore this step you should have already bought the domain you are going to use and it must be pointing to the ip of the vps where you are configuring gophish. domain = " < domain > " wget url + x certbot - autosudo apt install snapdsudo snap install coresudo snap refresh coresudo apt - get remove certbotsudo snap install - - classic certbotsudo ln - s / snap / bin / certbot / usr / bin / certbotcertbot certonly - - standalone - d " $ domain " mkdir / opt / gophish / ssl _ keyscp " / etc / letsencrypt / live / $ domain / privkey. pem " / opt / gophish / ssl _ keys / key. pemcp " / etc / letsencrypt / live / $ domain / fullchain. pem " / opt / gophish / ssl _ keys / key. crtmail configurationstart installing : apt - get install postfixthen add the domain to the following files : / etc / postfix / virtual _ domains / etc / postfix / transport / etc / postfix / virtual _ regexpchange also the values of the following variables inside / etc / postfix / main. cfmyhostname = < domain > mydestination = $ myhostname, < domain >, localhost. com, localhostfinally modify the files / etc / hostname and / etc / mailname to your domain name and restart your vps. now, create a dns a record of mail. < domain > pointing to the ip address of the vps and a dns mx record pointing to mail. < domain > now lets test to send an email : apt install mailutilsecho " this is the body of the email " | mail - s " this is the subject line " [ email protected ] gophi | [
-0.09584644436836243,
-0.2241470366716385,
-0.014247466810047626,
0.12679198384284973,
-0.7501558661460876,
-0.45510536432266235,
-0.43737882375717163,
0.5308509469032288,
0.13847129046916962,
0.8361965417861938,
-0.5482646226882935,
-0.5291095972061157,
0.7853465676307678,
-0.454703748226... | [
2175,
21850,
4095,
1013,
2175,
21850,
4095,
2017,
2097,
2022,
2445,
1037,
20786,
2005,
1996,
4748,
10020,
5310,
1999,
3417,
21211,
2509,
1999,
1996,
6434,
1012,
3568,
1010,
3229,
2008,
3417,
1998,
2224,
2216,
22496,
2000,
2689,
1996,
4748,
... | hack_tricks | 10.txt | 2 |
##sh configurationstop the execution of gophish and lets configure it. modify / opt / gophish / config. json to the following ( note the use of url " admin _ server " : { " listen _ url " : " 127. 0. 0. 1 : 3333 ", " use _ tls " : true, " cert _ path " : " gophish _ admin. crt ", " key _ path " : " gophish _ admin. key " }, " phish _ server " : { " listen _ url " : " 0. 0. 0. 0 : 443 ", " use _ tls " : true, " cert _ path " : " / opt / gophish / ssl _ keys / key. crt ", " key _ path " : " / opt / gophish / ssl _ keys / key. pem " }, " db _ name " : " sqlite3 ", " db _ path " : " gophish. db ", " migrations _ prefix " : " db / db _ ", " contact _ address " : " ", " logging " : { " filename " : " ", " level " : " " } } configure gophish servicein order to create the gophish service so it can be started automatically and managed a service you can create the file / etc / init. d / gophish with the following content : #! / bin / bash # / etc / init. d / gophish # initialization file for stop / start of gophish application server # # chkconfig : - 64 36 # description : stops / starts gophish application server # processname : gophish # config : / opt / gophish / config. json # from url define script variablesprocessname = gophishprocess = gophishappdirectory = / opt / gophishlogfile = / var / log / gophish / gophish. logerrfile = / var / log / gophish / gophish. errorstart ( ) { echo'starting'$ { processname } '...'cd $ { appdirectory } nohup. / $ process > > $ logfile | [
-0.12716136872768402,
-0.46651050448417664,
-0.4774862825870514,
0.3416081368923187,
-0.7823657393455505,
-0.23653484880924225,
-0.3066209852695465,
0.6843766570091248,
0.9029823541641235,
0.4995335340499878,
-0.19109384715557098,
-0.13631343841552734,
0.7631897926330566,
-0.44284310936927... | [
4095,
22354,
14399,
1996,
7781,
1997,
2175,
21850,
4095,
1998,
11082,
9530,
8873,
27390,
2063,
2009,
1012,
19933,
1013,
23569,
1013,
2175,
21850,
4095,
1013,
9530,
8873,
2290,
1012,
1046,
3385,
2000,
1996,
2206,
1006,
3602,
1996,
2224,
1997... | hack_tricks | 10.txt | 3 |
2 > > $ errfile & sleep 1 } stop ( ) { echo'stopping'$ { processname } '...'pid = $ ( / bin / pidof $ { process } ) kill $ { pid } sleep 1 } status ( ) { pid = $ ( / bin / pidof $ { process } ) if [ [ " $ pid "! = " " | " $ pid "! = " " ] ] ; then echo $ { processname }'is running...'else echo $ { processname }'is not running...'fi } case $ 1 in start | stop | status ) " $ 1 " ; ; esacfinish configuring the service and checking it doing : mkdir / var / log / gophishchmod + x / etc / init. d / gophishupdate - rc. d gophish defaults # check the serviceservice gophish startservice gophish statusss - l | grep " 3333 \ | 443 " service gophish stopconfiguring mail server and domainwaitthe older a domain is the less probable it's going to be caught as spam. then you should wait as much time as possible ( at least 1week ) before the phishing assessment. note that even if you have to wait a week you can finish configuring everything now. configure reverse dns ( rdns ) recordset a rdns ( ptr ) record that resolves the ip address of the vps to the domain name. sender policy framework ( spf ) recordyou must configure a spf record for the new domain. if you don't know what is a spf record read this page. you can use url to generate your spf policy ( use the ip of the vps machine ) this is the content that must be set inside a txt record inside the domain : v = spf1 mx a ip4 : ip. ip. ip. ip? alldomain - based message authentication, reporting & conformance ( dmarc ) recordyou must configure a dmarc record for the new domain. if you don't know what is a dmarc record read this page. you have to create a new dns txt record pointing the hostname _ dmarc. < domain > | [
0.3057299256324768,
0.2515788972377777,
-0.10079869627952576,
0.5253509283065796,
-0.20311979949474335,
-0.6285825371742249,
-0.6690904498100281,
0.16870495676994324,
0.6889278888702393,
0.8213364481925964,
0.013961294665932655,
-0.16530105471611023,
0.42399629950523376,
0.0405252799391746... | [
1016,
1028,
1028,
1002,
9413,
12881,
9463,
1004,
3637,
1015,
1065,
2644,
1006,
1007,
1063,
9052,
1005,
7458,
1005,
1002,
1063,
2832,
18442,
1065,
1005,
1012,
1012,
1012,
1005,
14255,
2094,
1027,
1002,
1006,
1013,
8026,
1013,
14255,
3527,
... | hack_tricks | 10.txt | 4 |
with the following content : v = dmarc1 ; p = nonedomainkeys identified mail ( dkim ) you must configure a dkim for the new domain. if you don't know what is a dmarc record read this page. this tutorial is based on : url need to concatenate both b64 values that the dkim key generates : v = dkim1 ; h = sha256 ; k = rsa ; p = miibijanbgkqhkig9w0baqefaaocaq8amiibcgkcaqea0wpibdqptzyk81njjqcrchichzxop8a1wjbsontka2x9qxczs + ixkvw + + qswdtdyu3q0ofnr0yd / tmg / y2bbgoegee + ytug2aegw8xx42nljq2d1pb2lrqpw4ixefronxu5hfksm7dyzml1gz1u0pr5x4izch0wophiq326qjxjzm79e1nth3xj " " y9n / dt3 + fvnibmupzxe216tdfuifkm6tl6o / axnsbswms1th812euno8xrpsdxjzflb9q3vbmkvwig4p538mholgzudebg563vv66u8d7uuzgyxyt4ws8nvm3qbmg0qkpwzakp + badlkosb9j2nupk4aj9kb5swidaqabtest your email configuration scoreyou can do that using url just access the page and send an email to the address they give you : echo " this is the body of the email " | mail - s " this is the subject line " [ email protected ] you can also check your email configuration sending an email to [ email protected ] and reading the response ( for this you will need to open port 25 and see the response in the file / var / mail / root if you send the email a as root ). check that you pass all the tests : = = = = = = = = = = = = = = = = = = = | [
-0.07936142385005951,
-0.5732943415641785,
0.24818359315395355,
0.5757335424423218,
0.11141268163919449,
-0.19654853641986847,
-0.4647172689437866,
0.03715990111231804,
0.5883604288101196,
1.508926510810852,
0.24644725024700165,
0.21588854491710663,
0.5738891363143921,
-0.2259213626384735,... | [
2007,
1996,
2206,
4180,
1024,
1058,
1027,
1040,
7849,
2278,
2487,
1025,
1052,
1027,
3904,
9527,
8113,
14839,
2015,
4453,
5653,
1006,
1040,
21138,
1007,
2017,
2442,
9530,
8873,
27390,
2063,
1037,
1040,
21138,
2005,
1996,
2047,
5884,
1012,
... | hack_tricks | 10.txt | 5 |
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = summary of results = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = spf check : passdomainkeys check : neutraldkim check : passsender - id check : passspamassassin check : hamalternatively, you can send a message to a gmail address that you control, view the received email ’ s headers in your gmail inbox, dkim = pass should be present in the authentication - results header field. authentication - results : mx. google. com ; spf = pass ( google. com : domain of [ email protected ] designates - - - as permitted sender ) [ email protected ] ; dkim = pass [ email protected ] ; removing from spamhouse blacklistthe page www. mail - tester. com can indicate you if you your domain is being blocked by spamhouse. you can request your domain / ip to be removed at : url from microsoft blacklistyou can request your domain / ip to be removed at url & launch gophish campaignsending profileset some name to identify the sender profiledecide from which account are you going to send the phishing emails. suggestions : noreply, support, servicedesk, salesforce... you can leave blank the username and password, but make sure to check the ignore certificate errorsit's recommended to use the " send test email " functionality to test that everything is working. i would recommend to send the test emails to 10min mails addresses in order to avoid getting blacklisted making tests. email templateset some name to identify the templatethen write a subject ( nothing estrange, just something you could expect to read in a regular email ) make sure you have checked " add tracking image " write the email template ( you can use variables like in the following example ) : < html > < head > < title > < / title > < / head > < body > < p class = " msonormal " > < span style = " font - size : 10. 0pt ; font - family | [
0.3744626045227051,
-0.2673829197883606,
0.20685537159442902,
1.0083547830581665,
-0.6182175278663635,
-0.06501943618059158,
-0.6199203729629517,
0.7037044167518616,
0.4979247748851776,
0.8011704683303833,
-0.19074136018753052,
0.2066163569688797,
0.47197413444519043,
-0.4218187928199768,
... | [
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1027,
1265... | hack_tricks | 10.txt | 6 |
": & quot ; verdana & quot ;, sans - serif ; color : black \" > dear { {. firstname } } { {. lastnam(...TRUNCATED) | [0.36701977252960205,-0.5800145268440247,-0.3517020642757416,0.491944283246994,0.02000923454761505,-(...TRUNCATED) | [1024,1004,22035,2102,1025,2310,26992,2050,1004,22035,2102,1025,1010,20344,1011,14262,10128,1025,360(...TRUNCATED) | hack_tricks | 10.txt | 7 |
"##phish / static / endpoint and then access them from / static / < filename > for the redirection y(...TRUNCATED) | [-0.17783038318157196,-0.3615454435348511,-0.3810688555240631,0.2773900628089905,-0.3440962433815002(...TRUNCATED) | [21850,4095,1013,10763,1013,2203,8400,1998,2059,3229,2068,2013,1013,10763,1013,1026,5371,18442,1028,(...TRUNCATED) | hack_tricks | 10.txt | 8 |
"the credentials, the 2fa, the cookie and any information of every interaction your while the tool i(...TRUNCATED) | [0.09712840616703033,-0.33236005902290344,-0.02333000674843788,0.45154431462287903,-0.10084272176027(...TRUNCATED) | [1996,22496,1010,1996,1016,7011,1010,1996,17387,1998,2151,2592,1997,2296,8290,2115,2096,1996,6994,20(...TRUNCATED) | hack_tricks | 10.txt | 9 |