▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑 Easy and fast steps to host website on cpanel :
fb.com/UndercOdeTestingCompany

🦑 𝕃𝔼𝕋𝕊 𝕊𝕋𝔸ℝ𝕋 :

1) First login to cpanel account by defining: http://www.domain-name/cpanel or http://www.domain-name:2082

2) Click on the option “File Manager”

3) Upload the file from the top menu.

Note: Only 1 file at a time can be uploaded. So archive the web site folder into .zip format.

4) Extract the zip file within public_html.

> Remember your index.html file should be inside public_html folder.

5) Simple way of uploading website file is by transferring files using filezilla.

Thats aLL
For More see Pictures for this tutorial on our fcb Grp
> fb.com/groups/UndercodeTesting
▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑 HMA PREMIUM ACCOUNT :
T.me/UndercOdeTesting
Tested just if you get error with login on your location try another

> alexbeast100@gmail.com:buster55

> alfred_j007@yahoo.com:kaykay




> ali.benmoghlia1986@gmail.com:gigivara


> alitaqvi@live.com:anfalsr5


> alondwae73@gmail.com:alondwae21


> alonewasdead@gmail.com:s4kitalic


> alvaritob97@gmail.com:alyson1997



>amankhurana1897@gmail.com:aman1897



> aminebenmouina@gmail.com:1521994amine1994


> andrej.tokarev.95@mail.ru:TTADTWPGMDA



> andy_edy85@yahoo.com:leoronaldo




> annaneayoub@live.fr:ayoub19a






>apecalex1@hotmail.com:jando110269




> armandotredici@libero.it:090188



> ashsenigma@gmail.com:damper7400



> bangbig888@gmail.com:7b6701d1



> bart40140@hotmail.fr:Alex201192



> blackpanda01@gmail.com:tomcat11



> bojan.bojovski@gmail.com:kokoskamkd123



> bonn200660@gmail.com:nuitjour2006



> brandonadler375@gmail.com:myps3rocks



> brian138x@yahoo.com:rockstar00



> brian_07@live.com:150857Brian



> candasd@yahoo.com:148300



> captured plan details":"1 Month"



> captured plan details":"P3Y"


> ced0@free.fr:Boubou56



>chanvanc@yahoo.com:goodboy



>cinsei1984@gmail.com:cc198484



> cj_goalie31@hotmail.com:hockey101




> coltro.nico@gmail.com:banana03





> cosmicpopsickle@hotmail.co.uk:Popsickle




> cozythemozy@hotmail.co.uk:Jesus2k8





> crazy8x11@gmail.com:alternate1



> dami_leoortiz@hotmail.com:39836286




> daniel.nickandros@gmail.com:yousuck1

powred by brothersAccount
@UndercOdeOfficial
▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁
🦑NORD VPN ACCOUNTS :
t.me/UndercOdeTesting

Tested just if you get error with login on your location try another

🦑 𝕃𝔼𝕋𝕊 𝕊𝕋𝔸ℝ𝕋 :

santostherebel@yahoo.com:Punisher82 | Expiration Date = 2020-11-04 00:36:32
keebler135@gmail.com:trinity00 | Expiration Date = 2020-01-28 20:51:20
tepdoesminecraft@gmail.com:minecraft007 | Expiration Date = 2020-02-11 12:16:20
m.g.maerschalk@gmail.com:Frittenfett23 | Expiration Date = 2022-01-07 12:35:17
deanfanning12@hotmail.com:platinumroof53 | Expiration Date = 2021-06-02 21:57:04
hernan.castros@gmail.com:oxfordmo | Expiration Date = 2021-11-15 03:48:52
toshkab@gmail.com:mismis23 | Expiration Date = 2020-07-30 14:07:52
acdaniels2017@gmail.com:Reddog77 | Expiration Date = 2020-11-20 11:42:16
dezzylanham@gmail.com:acft1tm1vb | Expiration Date = 2020-09-01 14:28:32
detlevq@yahoo.co.uk:24442614 | Expiration Date = 2022-01-23 13:27:09
alilovesya25@gmail.com:muggla09 | Expiration Date = 2020-04-19 04:59:34
billygatesmofo@gmail.com:liverpool5 | Expiration Date = 2020-01-30 03:30:17
suhailchandhok@gmail.com:maiden87 | Expiration Date = 2022-04-12 15:44:06
jarrettdan95@yahoo.com.au:yugioh8866 | Expiration Date = 2020-04-30 09:50:19
matte_thule16@hotmail.com:metrakit11 | Expiration Date = 2020-01-16 19:31:27
ceciliafitzgerald@xtra.co.nz:turnbul1 | Expiration Date = 2020-07-17 02:33:54
hewson72@hotmail.com:02Camaro | Expiration Date = 2020-09-15 05:13:09
Fran72159@hotmail.com:Igore759 | Expiration Date = 2022-08-16 14:02:57
m.alanjery@hotmail.com:mka9898232 | Expiration Date = 2020-12-01 23:20:59
Marcel_Schulze96@web.de:dedlwa39 | Expiration Date = 2020-02-07 23:31:17
lookinsum1997@gmail.com:412497samloo | Expiration Date = 2022-10-04 06:27:15
madianne22@outlook.com:Roxybuster09 | Expiration Date = 2020-08-03 00:00:00
aaronjbreuer@yahoo.com:k2M93pyW | Expiration Date = 2020-04-30 14:09:45
michaelfyk@gmail.com:pikle3310 | Expiration Date = 2020-01-18 18:52:16
ashwinthan@gmail.com:icpu2007 | Expiration Date = 2022-03-17 13:42:23
rbcasselberry@yahoo.com:Tanner85 | Expiration Date = 2020-03-27 13:21:57
nrcerf@gmail.com:2391ndst | Expiration Date = 2021-06-17 06:02:12
aaron1998evans@gmail.com:aaron1998 | Expiration Date = 2020-03-31 19:33:12
lewis.w.94@hotmail.co.uk:arsenal5 | Expiration Date = 2020-01-19 15:57:37
seth.ritter2@gmail.com:CVFootball63 | Expiration Date = 2024-06-07 00:24:43
leiflicious@gmail.com:342akdsksl87 | Expiration Date = 2021-07-14 05:55:58
g.forsyth70@gmail.com:jack1997 | Expiration Date = 2022-04-07 19:01:39
thea.ogle@gmail.com:girraffe | Expiration Date = 2020-12-01 08:53:38
colebeason2@live.com:charlet13 | Expiration Date = 2020-02-22 11:23:24
goldenzeus2021@yahoo.com:zeus2021 | Expiration Date = 2020-01-28 13:55:48
ciprianiorga@hotmail.com:cior3652 | Expiration Date = 2021-02-15 05:08:11
gianni_rosano@hotmail.com:rosano17 | Expiration Date = 2021-12-28 00:58:27
jimmy54714@aol.com:Gamefreek1 | Expiration Date = 2020-02-27 00:25:59
mattwcameron80@gmail.com:pout1980 | Expiration Date = 2020-07-08 02:44:25
ritchea95@yahoo.com:Jakobritchea95 | Expiration Date = 2022-02-13 01:34:14
tonybiviano@hotmail.com:pass1955 | Expiration Date = 2022-04-28 18:48:26
sk_randhawa@hotmail.com:Austin316 | Expiration Date = 2020-05-20 08:36:33
c.mclymont@hotmail.com:01328981 | Expiration Date = 2020-11-08 17:16:55
jessejuranka@gmail.com:mannure12 | Expiration Date = 2020-02-08 18:24:31
zorgish@hotmail.com:Tissekatt1 | Expiration Date = 2020-01-16 11:03:02
mjablonsky@hotmail.com:long26isl | Expiration Date = 2022-06-08 03:15:09
Oky.Santoso@gmail.com:callaway | Expiration Date = 2020-01-21 02:36:14
mattman079@hotmail.com:College079 | Expiration Date = 2020-07-03 14:27:36
bjones9870@gmail.com:britton9870 | Expiration Date = 2021-12-22 18:40:59
xbones123@hotmail.com:nikolai55 | Expiration Date = 2020-11-13 09:22:17
anna.fabing@hotmail.com:Immergruen1412 | Expiration Date = 2020-03-03 13:07:18
melliekate@yahoo.com.au:melon101 | Expiration Date = 2021-02-03 01:42:11
porchic911@mac.

com:porsche1 | Expiration Date = 2020-06-25 00:51:59

lvaughan31@hotmail.com:yoghurt2 | Expiration Date = 2021-12-11 05:43:49
lilibelle4432@yahoo.com:belle4432 | Expiration Date = 2020-09-24 23:00:13
jebus9011@hotmail.com:Tab102515 | Expiration Date = 2020-08-13 03:41:03
nathanmalone.pnw@gmail.com:Mypasswordis12 | Expiration Date = 2020-01-21 08:23:50
dyingtolive68@hotmail.com:password6 | Expiration Date = 2022-09-19 11:31:01
timohalstenbach@googlemail.com:Deutschebank1 | Expiration Date = 2021-12-19 18:16:50
rajeev.ravi@gmail.com:daedalus | Expiration Date = 2020-06-22 11:38:33
paul.lenathen@gmail.com:pl298172 | Expiration Date = 2020-02-15 07:29:04
joehelm@hotmail.co.uk:ploppy11 | Expiration Date = 2020-08-06 22:15:19
chasekennard@yahoo.com:Burton123 | Expiration Date = 2020-02-02 15:32:53
willeblomgren@hotmail.com:kalleanka12 | Expiration Date = 2020-01-23 15:38:22


powered by brothersAccount
@UndercOdeOfficial
▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁
mercury1331@hotmail.com:IloveGuns133 | Expiration Date = 2020-04-11 18:22:11
jaewon586@gmail.com:choi0516 | Expiration Date = 2021-12-19 22:30:49
niccolasmatranga@yahoo.com:Uber1337 | Expiration Date = 2020-04-30 09:35:49
lewisproctor7@gmail.com:rooney07 | Expiration Date = 2022-01-26 15:19:12
kala_shearer@hotmail.com:Belle123 | Expiration Date = 2020-10-14 02:55:52
cenmat@live.it:Halo3odst | Expiration Date = 2021-01-07 02:44:40
alawoeu@yahoo.fr:ua250555 | Expiration Date = 2020-02-14 06:16:33
pauleros2@gmail.com:Good4you | Expiration Date = 2021-02-15 05:41:07
laurie.purcell@gmail.com:lpp25361 | Expiration Date = 2022-07-13 03:50:55
adam@moonset.org:Roflcopter1 | Expiration Date = 2020-02-07 14:49:34
ryanlegamaro@gmail.com:Rlegamaro7446 | Expiration Date = 2020-01-17 18:33:58
cupra66@hotmail.fr:evann1910 | Expiration Date = 2020-03-17 21:09:03
brianjenneson@bigpond.com:Canada12 | Expiration Date = 2021-01-02 00:00:00
jm17ocon@gmail.com:Mickeyocon1 | Expiration Date = 2020-01-22 23:36:07
maxmatheson1@outlook.com:Tennis900 | Expiration Date = 2020-08-22 21:55:19
jonnydeaton@gmail.com:kacheek123 | Expiration Date = 2023-02-14 19:23:11
thomas.carson.is@gmail.com:e1ephant | Expiration Date = 2021-11-21 07:24:10
treyturner74@gmail.com:Corvette14 | Expiration Date = 2021-02-06 09:09:35
bayle.docsavage@gmail.com:pacman00 | Expiration Date = 2020-05-13 14:14:31
ayvar@yahoo.com:ionapole | Expiration Date = 2020-02-10 19:42:29
dragon-yohan@live.fr:91780yoyo | Expiration Date = 2022-08-28 15:28:23
tekkitteam@hotmail.com:Giorgio02 | Expiration Date = 2020-09-24 14:34:10
kobilee98@hotmail.com:Delldell12 | Expiration Date = 2022-03-28 02:53:15
calumi@icloud.com:Bluntfoot22 | Expiration Date = 2021-12-27 23:29:18
alinyear2002@hotmail.com:bd050111 | Expiration Date = 2021-12-19 08:58:44
rodriguez.amber@gmail.com:Felton1989 | Expiration Date = 2021-05-11 15:08:43
erlend.12@hotmail.com:buster13 | Expiration Date = 2022-10-12 11:10:04
eeagle1@gmail.com:skel8287 | Expiration Date = 2020-07-14 15:17:25
manofsorrows@hotmail.com:Sonata305 | Expiration Date = 2022-04-07 08:43:27
tom_vermeeren7@live.nl:Tzedc1503 | Expiration Date = 2022-07-06 17:01:29
1981przemko@gmail.com:Jolusia27 | Expiration Date = 2020-02-27 07:26:06
zayed11002@gmail.com:zayedhamad1 | Expiration Date = 2021-01-21 00:00:24
ucrazyiam@hotmail.com:2soccer2 | Expiration Date = 2020-02-02 04:12:38
thotrum@gmail.com:cogient1 | Expiration Date = 2022-05-21 10:52:34
alza3eeem_s@hotmail.com:s751990s | Expiration Date = 2022-02-22 23:33:22
bpatno@hotmail.com:Bearsfan1 | Expiration Date = 2021-09-08 00:00:00
ian.cunliffe1982@gmail.com:liverpool05 | Expiration Date = 2020-01-28 05:57:45
raul.palomo@gmail.com:ijam5690 | Expiration Date = 2021-05-23 09:45:02
askevoll@gmail.com:Huseby26 | Expiration Date = 2022-06-18 12:46:01
mikedodus@gmail.com:doobus17M | Expiration Date = 2021-05-03 08:13:00
jiabryant10@gmail.com:jiason13 | Expiration Date = 2020-02-03 22:21:07
pdaenen192@gmail.com:yinyang7 | Expiration Date = 2022-05-02 20:11:29
kent.causey@icloud.

com:Bulldog33 | Expiration Date = 2021-06-18 05:09:23

erin_roesler@hotmail.com:alderson | Expiration Date = 2020-01-29 20:24:25
oussy93@hotmail.fr:Nonos93500 | Expiration Date = 2022-07-02 04:15:56
amubarak1981@hotmail.com:111126688 | Expiration Date = 2021-08-06 15:44:58
emilyjaneodonoghue@gmail.com:acc0untant | Expiration Date = 2021-07-02 11:59:02
mathew.pereira@live.com:counter33 | Expiration Date = 2022-07-18 01:09:10
killa796@hotmail.com:gr4ndth3ft | Expiration Date = 2020-10-16 15:41:08
esaslavsky@hotmail.com:123456789 | Expiration Date = 2021-08-15 02:32:09
sandmangritz1@hotmail.com:mrgritz1 | Expiration Date = 2020-07-23 09:53:00
ange.202@gmail.com:cae10own | Expiration Date = 2020-11-11 08:04:16
michaelip90@hotmail.com:mipset0416 | Expiration Date = 2020-12-22 02:35:34
stan.rivera@sbcglobal.net:Hawaii5o | Expiration Date = 2021-12-26 05:31:08
todddavid123@yahoo.com:jack1999 | Expiration Date = 2022-07-29 16:44:31
jbakertx62@yahoo.com:yamihere | Expiration Date = 2022-01-21 22:14:18
nojoturkie@gmail.com:Technology98 | Expiration Date = 2021-09-30 19:11:36
csiboneal@gmail.com:bo477838 | Expiration Date = 2020-07-19 00:08:19
alexander.k.ruesch@gmail.com:jakkin13 | Expiration Date = 2020-11-26 16:20:29
kaluko636@gmail.com:kalukos14 | Expiration Date = 2020-02-04 04:52:05
blake.smartguy@gmail.com:goF15h1ng | Expiration Date = 2020-02-23 13:33:31
rwilding94@gmail.com:lemonade0 | Expiration Date = 2022-08-14 00:22:58
ojiver@hotmail.de:Martina0 | Expiration Date = 2020-07-04 17:16:48
alidaparente@hotmail.com:guychick | Expiration Date = 2020-03-30 04:14:51
jk72594@hotmail.com:hackmexD94 | Expiration Date = 2022-02-27 04:11:24
brnrdroda@gmail.com:Hockey666 | Expiration Date = 2020-08-24 11:32:53
krystal_cl3ar@hotmail.com:Jadelee5 | Expiration Date = 2020-01-24 00:24:19
moltebergk@gmail.com:1234test | Expiration Date = 2020-04-21 13:41:28
mdking97@gmail.com:9k12ak12337 | Expiration Date = 2020-06-30 00:50:06
93gnbuffill@gmail.com:Nelson13 | Expiration Date = 2020-02-11 02:39:02
kiangjeff@gmail.com:c3044651 | Expiration Date = 2023-10-11 05:33:17
scottmann911@gmail.com:sammy123 | Expiration Date = 2020-10-03 05:17:00
brendao_apr31996@yahoo.com:jadecloe3 | Expiration Date = 2020-01-20 23:07:13
mikehaydel@hotmail.com:vaw5teck | Expiration Date = 2021-11-21 23:12:01
magnus3570@gmail.com:mani2004 | Expiration Date = 2020-01-22 12:17:41
erik@wtnet.de:Sanhain0302 | Expiration Date = 2020-02-02 18:03:03
corykao@hotmail.com:rain1721 | Expiration Date = 2020-10-11 09:07:27
almd0201@gmail.com:imrose12 | Expiration Date = 2021-12-23 20:19:55
forevertoxxic@gmail.com:stargate5684 | Expiration Date = 2020-09-22 00:15:08
ernesset@gmail.com:Susanne1000 | Expiration Date = 2020-11-01 09:22:17
cb112012@hotmail.com:Gutter11 | Expiration Date = 2022-03-29 22:57:33
stian.tj@hotmail.com:Hello1994 | Expiration Date = 2020-02-07 21:25:26
anthonyamigon05@gmail.com:1Antysecas | Expiration Date = 2020-06-30 02:27:13
merevesz@gmail.com:corky123 | Expiration Date = 2020-09-07 05:14:51
woodplanck@gmail.com:acaciatree9 | Expiration Date = 2021-07-22 08:31:51
markune18@gmail.com:axf5d42e | Expiration Date = 2020-01-30 08:14:12
vrg.isti@gmail.com:42quattro | Expiration Date = 2021-01-05 15:07:16
xallan21@live.fr:Sltallan21 | Expiration Date = 2022-06-02 20:11:27
tracita96@gmail.com:lucygirl | Expiration Date = 2022-04-11 02:22:50
emily.walshx1206@gmail.com:toby1212 | Expiration Date = 2022-02-03 00:39:22
jacobash91@gmail.com:Shimano65 | Expiration Date = 2020-02-16 00:43:06
olegny1@gmail.com:dennis85 | Expiration Date = 2021-04-10 12:36:55
bend2pa@gmail.com:maxrules8 | Expiration Date = 2022-02-28 03:07:37
charlie@thelifestyle-agency.com:alcap0ne | Expiration Date = 2020-10-20 01:36:34
sebastian.anving94@gmail.com:Horred12 | Expiration Date = 2022-12-05 23:28:18
thomasbusteed@gmail.com:Forever1 | Expiration Date = 2022-07-20 01:49:52
marciobehle@gmail.com:md11a380 | Expiration Date = 2020-02-11 07:16:05
aneesh_v@hotmail.com:namita1974 | Expiration Date = 2020-06-23 19:55:08
gppedraza61@gmail.com:phlgna61 | Expiration Date = 2021-08-22 18:22:51

m_odonnell_08@hotmail.co.uk:2588buff | Expiration Date = 2020-01-22 00:03:03
davila.dmitri@gmail.com:Dmdavil0 | Expiration Date = 2022-09-10 06:43:48
clairemcenhill@hotmail.com:kohtoh33 | Expiration Date = 2020-09-30 17:51:48
dustin_mustach@yahoo.com:Dnmdaman123 | Expiration Date = 2021-12-26 12:13:31
rcm8251@gmail.com:mountaindew3 | Expiration Date = 2023-03-01 19:20:22
precious_1@dodo.com.au:lillypilly | Expiration Date = 2021-03-04 10:55:20
rufinor2000@gmail.com:iloff123 | Expiration Date = 2022-07-19 16:50:05
mattatta33@yahoo.com:datskune08 | Expiration Date = 2020-02-26 05:26:03
emilyhatchett7@gmail.com:s3ls4eva | Expiration Date = 2020-01-25 21:45:14
darenlpickens@gmail.com:Dallas41 | Expiration Date = 2021-03-16 01:01:10
bornathome@gmail.com:shadow21 | Expiration Date = 2023-04-28 01:09:26
daniel.gadegaard.andersen@gmail.com:Gadegaard1 | Expiration Date = 2020-02-01 19:50:45
larsthaar@gmail.com:Visbak123 | Expiration Date = 2022-05-25 12:43:29
ayasofia89@gmail.com:calin2404 | Expiration Date = 2022-07-17 05:03:45
aekinserhough@gmail.com:kitten12345 | Expiration Date = 2022-05-12 12:45:55
lenoxgjohnson@gmail.com:bo2thebo | Expiration Date = 2020-06-25 02:06:25
lpropedo16@gmail.com:gsxr1000 | Expiration Date = 2020-10-16 11:19:26
banckhd@gmail.com:panzer05 | Expiration Date = 2020-05-23 11:27:19
dinwilliam88@hotmail.com:hq27pu2o | Expiration Date = 2021-08-26 08:22:49
jkpunjabi@hotmail.com:sarim5samun2 | Expiration Date = 2021-05-17 04:27:10
jaguerra1982@gmail.com:jordan82 | Expiration Date = 2022-04-18 01:01:35
cheesy.dong@yahoo.com:weavel2947 | Expiration Date = 2022-04-28 06:56:06
wcfordspares@gmail.com:claire27 | Expiration Date = 2020-01-20 16:17:16
ccase18@gmail.com:Baseball84 | Expiration Date = 2020-01-17 22:42:15
mahesha88@hotmail.com:watermelon88 | Expiration Date = 2020-11-13 02:30:40
kennycheung@msc.org.mo:Msc741014 | Expiration Date = 2020-07-22 12:06:39
saul.lino.sil@gmail.com:980623As | Expiration Date = 2020-01-17 06:06:56
fish10444@hotmail.com:henry1022 | Expiration Date = 2020-02-12 23:32:21
matthewhunt45@gmail.com:laon2008 | Expiration Date = 2021-11-20 03:45:45
jwylie22@hotmail.com:dookie22 | Expiration Date = 2020-02-06 01:16:32
daikaiou@hotmail.com:badbug01 | Expiration Date = 2022-08-27 00:00:00
ratush@gmail.com:kolya911 | Expiration Date = 2020-11-18 20:31:22
rajp@live.com.au:rajp1968 | Expiration Date = 2021-12-28 00:27:22
brad.kiefer25@gmail.com:foxracing25 | Expiration Date = 2020-06-30 14:19:45
kostya.mirosh@gmail.com:alonzo33 | Expiration Date = 2020-09-09 09:28:19
pandaboy626@gmail.com:frost626 | Expiration Date = 2020-03-23 14:06:05
lindenjedwards@gmail.com:Movingup8 | Expiration Date = 2021-06-24 15:59:43
cfarrell1980@gmail.com:atha7FUt | Expiration Date = 2022-06-04 20:02:29
clarissacameron@hotmail.co.uk:beauty03 | Expiration Date = 2022-09-19 13:05:33
brendynellis@yahoo.com:Striker1998 | Expiration Date = 2020-10-17 09:31:23
mathieubo1@live.fr:mateu09000 | Expiration Date = 2023-03-16 12:34:05
marcus.ovhed@hotmail.com:Sani2579 | Expiration Date = 2020-01-19 04:59:57
mariohug61@gmail.com:Supermario64 | Expiration Date = 2020-01-21 18:16:44
andrewjoo7@gmail.com:blueman7 | Expiration Date = 2022-09-22 23:23:30
jkpenn89@outlook.com:marlee05 | Expiration Date = 2020-02-14 05:59:29
olebjore@hotmail.com:12qwaszx | Expiration Date = 2021-07-29 10:01:52
leighclark123@gmail.com:laser157 | Expiration Date = 2020-07-12 00:20:14
marpar187@yahoo.com:tool1877 | Expiration Date = 2020-05-27 04:48:04
smacchesney@gmail.com:ruffryders | Expiration Date = 2020-12-08 03:54:51
axelbramell@hotmail.com:chambre9 | Expiration Date = 2020-04-30 19:38:10
razAck@gmail.com:AfshaanA | Expiration Date = 2021-08-08 20:33:54
maxikangs@gmail.com:khamul33 | Expiration Date = 2020-08-26 12:49:49
zak.live@yahoo.fr:zak66350 | Expiration Date = 2021-11-30 21:42:51
nate.auger17@gmail.com:nate12147 | Expiration Date = 2020-02-14 05:25:13
austin.belew@hotmail.com:gamefreak92 | Expiration Date = 2020-12-24 17:01:05

m_odonnell_08@hotmail.co.uk:2588buff | Expiration Date = 2020-01-22 00:03:03
davila.dmitri@gmail.com:Dmdavil0 | Expiration Date = 2022-09-10 06:43:48
clairemcenhill@hotmail.com:kohtoh33 | Expiration Date = 2020-09-30 17:51:48
dustin_mustach@yahoo.com:Dnmdaman123 | Expiration Date = 2021-12-26 12:13:31
rcm8251@gmail.com:mountaindew3 | Expiration Date = 2023-03-01 19:20:22
precious_1@dodo.com.au:lillypilly | Expiration Date = 2021-03-04 10:55:20
rufinor2000@gmail.com:iloff123 | Expiration Date = 2022-07-19 16:50:05
mattatta33@yahoo.com:datskune08 | Expiration Date = 2020-02-26 05:26:03
emilyhatchett7@gmail.com:s3ls4eva | Expiration Date = 2020-01-25 21:45:14
darenlpickens@gmail.com:Dallas41 | Expiration Date = 2021-03-16 01:01:10
bornathome@gmail.com:shadow21 | Expiration Date = 2023-04-28 01:09:26
daniel.gadegaard.andersen@gmail.com:Gadegaard1 | Expiration Date = 2020-02-01 19:50:45
larsthaar@gmail.com:Visbak123 | Expiration Date = 2022-05-25 12:43:29
ayasofia89@gmail.com:calin2404 | Expiration Date = 2022-07-17 05:03:45
aekinserhough@gmail.com:kitten12345 | Expiration Date = 2022-05-12 12:45:55
lenoxgjohnson@gmail.com:bo2thebo | Expiration Date = 2020-06-25 02:06:25
lpropedo16@gmail.com:gsxr1000 | Expiration Date = 2020-10-16 11:19:26
banckhd@gmail.com:panzer05 | Expiration Date = 2020-05-23 11:27:19
dinwilliam88@hotmail.com:hq27pu2o | Expiration Date = 2021-08-26 08:22:49
jkpunjabi@hotmail.com:sarim5samun2 | Expiration Date = 2021-05-17 04:27:10
jaguerra1982@gmail.com:jordan82 | Expiration Date = 2022-04-18 01:01:35
cheesy.dong@yahoo.com:weavel2947 | Expiration Date = 2022-04-28 06:56:06
wcfordspares@gmail.com:claire27 | Expiration Date = 2020-01-20 16:17:16
ccase18@gmail.com:Baseball84 | Expiration Date = 2020-01-17 22:42:15
mahesha88@hotmail.com:watermelon88 | Expiration Date = 2020-11-13 02:30:40
kennycheung@msc.org.mo:Msc741014 | Expiration Date = 2020-07-22 12:06:39
saul.lino.sil@gmail.com:980623As | Expiration Date = 2020-01-17 06:06:56
fish10444@hotmail.com:henry1022 | Expiration Date = 2020-02-12 23:32:21
matthewhunt45@gmail.com:laon2008 | Expiration Date = 2021-11-20 03:45:45
jwylie22@hotmail.com:dookie22 | Expiration Date = 2020-02-06 01:16:32
daikaiou@hotmail.com:badbug01 | Expiration Date = 2022-08-27 00:00:00
ratush@gmail.com:kolya911 | Expiration Date = 2020-11-18 20:31:22
rajp@live.com.au:rajp1968 | Expiration Date = 2021-12-28 00:27:22
brad.kiefer25@gmail.com:foxracing25 | Expiration Date = 2020-06-30 14:19:45
kostya.mirosh@gmail.com:alonzo33 | Expiration Date = 2020-09-09 09:28:19
pandaboy626@gmail.com:frost626 | Expiration Date = 2020-03-23 14:06:05
lindenjedwards@gmail.com:Movingup8 | Expiration Date = 2021-06-24 15:59:43
cfarrell1980@gmail.com:atha7FUt | Expiration Date = 2022-06-04 20:02:29
clarissacameron@hotmail.co.uk:beauty03 | Expiration Date = 2022-09-19 13:05:33
brendynellis@yahoo.com:Striker1998 | Expiration Date = 2020-10-17 09:31:23
mathieubo1@live.fr:mateu09000 | Expiration Date = 2023-03-16 12:34:05
marcus.ovhed@hotmail.com:Sani2579 | Expiration Date = 2020-01-19 04:59:57
mariohug61@gmail.com:Supermario64 | Expiration Date = 2020-01-21 18:16:44
andrewjoo7@gmail.com:blueman7 | Expiration Date = 2022-09-22 23:23:30
jkpenn89@outlook.com:marlee05 | Expiration Date = 2020-02-14 05:59:29
olebjore@hotmail.com:12qwaszx | Expiration Date = 2021-07-29 10:01:52
leighclark123@gmail.com:laser157 | Expiration Date = 2020-07-12 00:20:14
marpar187@yahoo.com:tool1877 | Expiration Date = 2020-05-27 04:48:04
smacchesney@gmail.com:ruffryders | Expiration Date = 2020-12-08 03:54:51
axelbramell@hotmail.com:chambre9 | Expiration Date = 2020-04-30 19:38:10
razAck@gmail.com:AfshaanA | Expiration Date = 2021-08-08 20:33:54
maxikangs@gmail.com:khamul33 | Expiration Date = 2020-08-26 12:49:49
zak.live@yahoo.fr:zak66350 | Expiration Date = 2021-11-30 21:42:51
nate.auger17@gmail.com:nate12147 | Expiration Date = 2020-02-14 05:25:13
austin.belew@hotmail.com:gamefreak92 | Expiration Date = 2020-12-24 17:01:05

▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑NETFLIX WORKING MODS TESTED
t.me/UndercOdeTesting


3 Servers Each one for many contries
> works as well i recommeded to use any usa vpn sucj nord

> https://sv4.spiderdown.com/fa11a8290bbbf6c75d2536f6177ed0e4/Netflix/Netflix-SV0.apk



> https://sv4.spiderdown.com/fa11a8290bbbf6c75d2536f6177ed0e4/Netflix/Netflix-SV1.apk


>https://sv4.spiderdown.com/fa11a8290bbbf6c75d2536f6177ed0e4/Netflix/Netflix-SV2.apk


@UNDERCODEOFFICIAL
▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

Recently post from UndercOde wa grps

▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑 Some categories of vulnerabilities :Lastest :
t.me/UndercOdeTesting

🦑 𝕃𝔼𝕋𝕊 𝕊𝕋𝔸ℝ𝕋 :


An injection of code happens when an attacker sends invalid and untrusted data to the application as part of a command or query. The attacker has the malicious intention to trick the application into executing unintended behavior to collect data or create damage.

Some of the more common injections are:

1) SQL

2) OS command

3) ORM

4) LDAP

5) Expression Language (EL) or OGNL injection

6) Example of an attack

7) According to OWASP, one of the most common examples is the SQL query consuming untrusted data.

> string-query-sql-1

8) This query can be exploited by modifying the “id” parameter value as

9) This makes a request to the application to return all records from the account table, other similar and more severe injections can modify the data, and even cause a loss of data.

🦑 How to prevent it?

> The main reason for injections to happen is the lack of validation and sanitation of data consumed by the application. The recommendations to prevent injection depends on the technology you are using. In general, you have to make sure that your development team is following security requirements when writing code.

Some pointers to prevent the injection of code:

1) Keep data separate from queries. This is the main key to prevention.

2) Use safe APIs to eliminate the use of an interpreter. This lowers the risk of SQL injections.

3) Create a “white list” for server-side input validation.

4) Use LIMIT and other SQL controls to prevent mass disclosure in case of an attack.

@UNDERCODEOFFICIAL
▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑HOW CUSTOM DOMAINE NAME ON GITHUB TUTORIAL :
instagram.com/UndercOdeTestingCompany

🦑 𝕃𝔼𝕋𝕊 𝕊𝕋𝔸ℝ𝕋 :

1) Create a GitHub account on github.com.

2) Download either GitHub for Mac or GitHub for Windows, depending on your operating system. Open the app and log in using the account you just created.

> (On Mac): After you login, click advanced and make sure that your name and email are correct. Then, click "Install Command Line Tools", just in case you want to start using the command line later in life.

3) Create a new repository in your GitHub application. Name it your-username.github.io. The name is very important. Note the folder that GitHub is saving the repository to. Make sure the "Push to GitHub?" box is checked.

4) Move your website's files into the folder that GitHub just created when you made the repository. IMPORTANT: Your homepage HTML file must be called "index.html", and it must exist in the top-level directory.

5) Back in the GitHub application, you should see your files in the left column. Make sure they are all checked. If so, enter a message in the text box called "commit summary", something like "initial commit." Then, click the commit button.

6) Click the "Publish repo" button in the top right corner.

7) Give it about 10 minutes, then check your-username.github.io. Your website should be there!

8) Using a custom domain name

9) You can just leave your website at that address (it'll give you some serious street cred in the developer world), but if you have a custom domain you would like to use, it is very simple to make GitHub redirect your page.

10 ) Log in to your domain registrar and find where to change your host records. If you don't know, you can usually Google "(domain registrar) change host records", and your registrar will have an explainer telling you how to do it.

11) Change your domain's A Record to 204.232.175.78. This is GitHub's IP address, which allows GitHub to resolve your URL and serve the correct files.

12) In your website's directory folder on your computer, create a file called "CNAME". On the first line, type your domain name. Save the file.

13) In your GitHub application, you should see the file in the left column. Make sure it is checked and enter your commit message. Have it say something like "Adding CNAME file."

14) Click "Sync branches."

> It can take as long as 48 hours for your domain to resolve to your GitHub page. However, it is usually pretty quick, so check back in an hour or so.

@UNDERCODEOFFICIAL
▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁


🦑 How to prevent Broken Authentication ?
t.me/UndercOdeTesting

🦑 𝕃𝔼𝕋𝕊 𝕊𝕋𝔸ℝ𝕋 :

> The development team must implement the best practices for web security followed by external security audits and testing the code before shipping it out.

Other common pointers include:

1) Do not deploy any default credentials
Store passwords using a modern one-way hash function
Implement weak password checks against a list of the top 10000 worst passwords.

2) Ensure registration, credential recovery, and API pathways are hardened against account enumeration attacks by using the same messages for all outcomes

3) Implement multi-factor authentication to prevent credential stuffing, brute force, and stolen credential attacks.
Log authentication failures and alert administrators when attacks are detected.

4) Limit the attempts for authenticating

5) Secure your password storage

@UNDERCODEOFFICIAL
▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑 Secure Yourself from Sensitive Data Exposure bug 2019 :
t.me/UndercOdeTesting

🦑 𝕃𝔼𝕋𝕊 𝕊𝕋𝔸ℝ𝕋 :

E ncrypted data can be broken into due to weaknesses in:

1) Password hashing storages

2) Key generation process

3) mKey management

4) Protocol usage

5) Some other pointers:

6) Identify which data is sensitive according to privacy laws, regulatory requirements, or business needs.

7) Classify data processed, stored, or transmitted by an application.

8) Apply controls according to the classification.

9) Don’t store sensitive data unnecessarily.

10) Discard data as soon as possible or use PCI DSS compliant tokenization or even truncation. Data that is not retained cannot be stolen.

11) Make sure to encrypt all sensitive data at rest.

12) Ensure up-to-date and strong standard algorithms, protocols, and keys are in place; use proper key management.

13) Encrypt all data in transit with secure protocols such as TLS with perfect forward secrecy (PFS) ciphers, cipher prioritization by the server, and secure parameters.

14) Enforce encryption using directives like HTTP Strict Transport Security (HSTS).

15) Disable caching for responses that contain sensitive data.

16) Ensure that stored passwords have a strong adaptive algorithm such as Argon2, scrypt, bcrypt, or PBKDF2.

17) Verify independently the effectiveness of your settings.


@UNDERCODEOFFICIAL
▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑 Secure Yourself from Sensitive Data Exposure bug 2019 :
t.me/UndercOdeTesting

🦑 𝕃𝔼𝕋𝕊 𝕊𝕋𝔸ℝ𝕋 :

E ncrypted data can be broken into due to weaknesses in:

1) Password hashing storages

2) Key generation process

3) mKey management

4) Protocol usage

5) Some other pointers:

6) Identify which data is sensitive according to privacy laws, regulatory requirements, or business needs.

7) Classify data processed, stored, or transmitted by an application.

8) Apply controls according to the classification.

9) Don’t store sensitive data unnecessarily.

10) Discard data as soon as possible or use PCI DSS compliant tokenization or even truncation. Data that is not retained cannot be stolen.

11) Make sure to encrypt all sensitive data at rest.

12) Ensure up-to-date and strong standard algorithms, protocols, and keys are in place; use proper key management.

13) Encrypt all data in transit with secure protocols such as TLS with perfect forward secrecy (PFS) ciphers, cipher prioritization by the server, and secure parameters.

14) Enforce encryption using directives like HTTP Strict Transport Security (HSTS).

15) Disable caching for responses that contain sensitive data.

16) Ensure that stored passwords have a strong adaptive algorithm such as Argon2, scrypt, bcrypt, or PBKDF2.

17) Verify independently the effectiveness of your settings.


@UNDERCODEOFFICIAL
▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑 How Prevent Broken Access Control :
t.me/UndercOdeTesting

1) Follow the Principle of Least Privilege, where the user should only have access to the minimum privileges that are necessary to perform actions.

2) Nothing more than what their role is intended to do.
Implement access control mechanisms once and re-use them throughout the application.

3) Model access controls should enforce record ownership, rather than accepting that the user can create, read, update or delete any record. For example, a user should only be able to modify or delete data that is their own. If I log in to an application, I should only be allowed to modify my data.

4) Domain access controls are unique to each application, but business limit requirements should be enforced by domain models.

5) Disable web server directory listing, and ensure file metadata such as git is not present within web roots.

6) Monitoring and logging are extremely important when access control fails the incident should be logged and send an alert to admins.

7) Use Rate limiting API and controller access to minimize the harm from automated attack tooling.

8) It is recommended for developers and QA engineers to include functional access control unit and integration tests.

@UNDERCODEOFFICIAL
▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

—————𝖀𝖓D𝖊𝖗𝕮𝖔D𝖊 —————

🦑 WEBSITE HACKING
T.me/UndercodeTesting

🦑Installisation:

Clone :https://github.com/koutto/jok3r

1) Docker Image size
Pull Jok3r Docker Image:

> sudo docker pull koutto/jok3r

2) Run fresh Docker container:

> sudo docker run -i -t --name jok3r-container -w /root/jok3r -e

> DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix --shm-size 2g --net=host koutto/jok3

3) -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix is required in order to be able to start GUI applicationfrom the Docker container (e.g. open web browser to read reports). It requires running xhost +local:root on the host.

4) --shm-size 2g is used to increase the size of the shared memory, it is required to avoid crashs of web browser when reading reports from the Docker container.

--net=host is required to share host's interface. It is needed for reverse connections (e.g. Ping to container when testing for RCE, Getting a reverse shell)

5) To re-run a stopped container:

sudo docker start -i jok3r-container
To open multiple shells inside the container:

> sudo docker exec -it jok3r-container bash

🦑RUN:& USE

1) python3 jok3r.py info --services
Show security checks for a given service:

2) python3 jok3r.py info --checks <service>
Show supported attack profiles for a given service:

3) python3 jok3r.py info --attack-profiles <service>
Show supported products for all services:

4) python3 jok3r.py info --products

WRITTEN BY STEAVE(t.m)
—————-UNDER𝕮𝖔D𝖊————-

▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑 WHY UndercOde hackers and many others use and share Python More that otherlanguage programming ?

> Python is a universal language.

> He is one of the five most used on GitHub.

> The main code for the games World of Tanks, Battlefield 2, and Civilization 4 is written in Python.

> Intel, Cisco, and HP use this language to automate testing of software and web interfaces.

> Python is loved by developers and employees of Google, Facebook, Yandex.

> It speeds up scientific calculations and big data processing.
t.me/UndercodeTesting


▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑 Netgear Vulnerability Lastest @UndercOdeOfficial
> t.me/UndercOdeTesting

🦑 𝕃𝔼𝕋𝕊 𝕊𝕋𝔸ℝ𝕋 :

1) Netgear routers have identified five vulnerabilities. Among other things, it was discovered that they can enter the web interface without authentication, which is present in 17 models of Netgear devices.

2) The problem is simple to operate and resembles a backdoor - to perform any operations in the web-interface it is enough to add the argument "& genie = 1" to the request URL and these operations will be performed without checking the authentication parameters.

3) Another vulnerability allows access to the contents of any files in the file systems of the device, including files with passwords and files on connected external USB-drives.

4) The problem is caused by the lack of checking resource access using indirect paths ("..") in the script genie_restoring.cgi, designed to recover the password. For example, to get the contents of the README.txt file from a mounted drive, you can send the request "http://192.168.1.1/genie_restoring.cgi?id=304966648" passing the arguments "id = 304966648 & next_file = cgi-bin /../ through the POST method. ./tmp/mnt/usb0/part1/README.txt ".

5) Other vulnerabilities are less dangerous, for example, one of the problems allows executing a code with root privileges on the device within two minutes after pressing the Wi-Fi Protected Setup button. Operation is performed through an attempt to connect devices with a name of the MR type "/ sbin / reboot" to the router.

6) A similar vulnerability allows arbitrary code to be executed on a device if it has access to the web interface (it can be used for CRSF attacks) by substituting commands in the device_name parameter (for example, "& device_name = A% 22 +% 26% 26 + touch +% 2Ftmp% 2Fjimmers +% 26% 26 + echo +% 22B ").

7) Netgear has already released a firmware update that urgently needs to be installed for all users of vulnerable devices.

8) He also recommends that you ensure that the web interface is accessible only from the internal network and is blocked for requests from the Internet.

9) It is noteworthy that information about the problems was transmitted to Netgear back in March last year, firmware updates with patches were published in the fall, and information about vulnerabilities was disclosed only now.

▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁

🦑More About Netgear: 2020 tool
> Python module for interacting with Netgear's Arlo camera system.
fb.com/UndercOdeTestingCompany

🦑𝕀ℕ𝕊𝕋𝔸𝕃𝕃𝕀𝕊𝔸𝕋𝕀𝕆ℕ & ℝ𝕌ℕ:

> pip install arlo

--or--

# Install from master branch
$ pip install git+https://github.com/jeffreydwalter/arlo

2) After installing all of the required libraries, you can import and use this library like so:

from arlo import Arlo

from datetime import timedelta, date
import datetime
import sys

USERNAME = 'user@example.com'
PASSWORD = 'supersecretpassword'

try:
# Instantiating the Arlo object automatically calls Login(), which returns an oAuth token that gets cached.
# Subsequent successful calls to login will update the oAuth token.
arlo = Arlo(USERNAME, PASSWORD)


thats all
▁ ▂ ▄ ｕ𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁