Skip to content

Commit 9c0ffe6

Browse files
theinfosecguytheinfosecguy
authored
Merge pull request #1 from KathanP19/master
Added to Fork
2 parents 741bab1 + 83037be commit 9c0ffe6

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

43 files changed

+1384
-36
lines changed

‎.all-contributorsrc‎

Lines changed: 123 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,123 @@
1+
{
2+
"files": [
3+
"README.md"
4+
],
5+
"imageSize": 100,
6+
"commit": false,
7+
"contributors": [
8+
{
9+
"login": "remonsec",
10+
"name": "Mehedi Hasan Remon",
11+
"avatar_url": "https://avatars2.githubusercontent.com/u/54717234?v=4",
12+
"profile": "https://github.com/remonsec",
13+
"contributions": [
14+
"tutorial"
15+
]
16+
},
17+
{
18+
"login": "theinfosecguy",
19+
"name": "Keshav Malik",
20+
"avatar_url": "https://avatars3.githubusercontent.com/u/33570148?v=4",
21+
"profile": "https://www.theinfosecguy.me",
22+
"contributions": [
23+
"tutorial"
24+
]
25+
},
26+
{
27+
"login": "0xd3vil",
28+
"name": "Vivek Kumar Yadav",
29+
"avatar_url": "https://avatars3.githubusercontent.com/u/32324065?v=4",
30+
"profile": "https://0xd3vil.github.io/",
31+
"contributions": [
32+
"tutorial"
33+
]
34+
},
35+
{
36+
"login": "SMHTahsin33",
37+
"name": "smhtahsin33",
38+
"avatar_url": "https://avatars0.githubusercontent.com/u/60981314?v=4",
39+
"profile": "https://smhtahsin33.me",
40+
"contributions": [
41+
"tutorial"
42+
]
43+
},
44+
{
45+
"login": "Virdoexhunter",
46+
"name": "Deepak Dhiman",
47+
"avatar_url": "https://avatars1.githubusercontent.com/u/68891432?v=4",
48+
"profile": "https://github.com/Virdoexhunter",
49+
"contributions": [
50+
"tutorial"
51+
]
52+
},
53+
{
54+
"login": "maverickNerd",
55+
"name": "maverickNerd",
56+
"avatar_url": "https://avatars3.githubusercontent.com/u/49231687?v=4",
57+
"profile": "https://github.com/maverickNerd",
58+
"contributions": [
59+
"tutorial"
60+
]
61+
},
62+
{
63+
"login": "Harsha-Ambati",
64+
"name": "Harsha Vardhan",
65+
"avatar_url": "https://avatars3.githubusercontent.com/u/47480010?v=4",
66+
"profile": "http://harsha.ambati05@gmail.com",
67+
"contributions": [
68+
"tutorial"
69+
]
70+
},
71+
{
72+
"login": "bishal0x01",
73+
"name": "Bishal Shrestha",
74+
"avatar_url": "https://avatars3.githubusercontent.com/u/26160488?v=4",
75+
"profile": "https://github.com/bishal0x01",
76+
"contributions": [
77+
"tutorial"
78+
]
79+
},
80+
{
81+
"login": "Cyber-Pirate",
82+
"name": "Cyber-Pirate",
83+
"avatar_url": "https://avatars1.githubusercontent.com/u/69442715?v=4",
84+
"profile": "https://github.com/Cyber-Pirate",
85+
"contributions": [
86+
"tutorial"
87+
]
88+
},
89+
{
90+
"login": "h4ckboy19",
91+
"name": "Naman Shah",
92+
"avatar_url": "https://avatars1.githubusercontent.com/u/61796314?v=4",
93+
"profile": "https://github.com/h4ckboy19",
94+
"contributions": [
95+
"tutorial"
96+
]
97+
},
98+
{
99+
"login": "Anugrahsr",
100+
"name": "ANUGRAH S R",
101+
"avatar_url": "https://avatars3.githubusercontent.com/u/44763564?v=4",
102+
"profile": "https://anugrahsr.netlify.com/",
103+
"contributions": [
104+
"tutorial"
105+
]
106+
},
107+
{
108+
"login": "SocioDroid",
109+
"name": "Aishwarya Kendle",
110+
"avatar_url": "https://avatars1.githubusercontent.com/u/47445489?v=4",
111+
"profile": "https://github.com/SocioDroid",
112+
"contributions": [
113+
"tutorial"
114+
]
115+
}
116+
],
117+
"contributorsPerLine": 7,
118+
"projectName": "HowToHunt",
119+
"projectOwner": "KathanP19",
120+
"repoType": "github",
121+
"repoHost": "https://github.com",
122+
"skipCi": true
123+
}

‎Account_Takeovers_Methodologies/Chaining_low_impact_bugs_with_xss.md‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
# Chaining Session Hijacking with XSS
2+
```
3+
1.I have add a session hijacking method in broken auth and session managment.
4+
2.If you find that on target.
5+
3.Try anyway to steal cookies on that target.
6+
4.Here I am saying look for xss .
7+
5.If you find xss you can stole the cookies of victim and using session hijacking you can takeover the account of victim.
8+
```
9+
10+
### Author
11+
* [@Virdoex_hunter](https://twitter.com/Virdoex_hunter)

‎Account_Takeovers_Methodologies/No_rate_limit_on_login_with_weak_password_policy.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
```
2+
So if you find that target have weak password policy try to go for no rate limit attacks in poc shows by creating very weak password of your account.
3+
4+
(May or may not be accepted)
5+
```
6+
### Author
7+
* [@Virdoex_hunter](https://twitter.com/Virdoex_hunter)

‎Account_Takeovers_Methodologies/Password_reset_poisoning_leads_to_token_theft.md‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
# PASSWORD RESET POISIONING LEADS TO TOKEN THEFT
2+
```
3+
1.Go to password reset funtion.
4+
2.Enter email and intercept the request.
5+
3.Change host header to some other host i.e,
6+
Host:target.com
7+
Host:attacker.com
8+
4.Forward this if you found that in next request attacker.com means you successfully theft the token.:)
9+
```
10+
11+
### Author
12+
* [@Virdoex_hunter](https://twitter.com/Virdoex_hunter)

‎Account_Takeovers_Methodologies/Using_Auth_Bypass.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
```
2+
Go to my Auth Bypass folder and there is a file otp bypass response manipulation that leads to account takeovers.
3+
```
4+
5+
### Author
6+
* [@Virdoex_hunter](https://twitter.com/Virdoex_hunter)

‎Account_Takeovers_Methodologies/Using_CSRF.md‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
# Always try to get csrf on:
2+
```
3+
1.Change Password function.
4+
2.Email change
5+
3.Change Security Question
6+
```
7+
### Author
8+
* [@Virdoex_hunter](https://twitter.com/Virdoex_hunter)

‎Account_Takeovers_Methodologies/Using_sensitive_data_exposure.md‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
```
2+
This is depends on your luck.
3+
4+
Sometimes using git recon and google recon you may found files that contains critical information like user tokens, usernames and their password.
5+
```
6+
7+
### Author
8+
* [@Virdoex_hunter](https://twitter.com/Virdoex_hunter)
9+

‎Account_Takeovers_Methodologies/token_leaks_in_response.md‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
* So there are multiple ways to do it but all are same.
2+
3+
* So I will sharing my method that I have learnt here .
4+
5+
* Endpoints:(Register,Forget Password)
6+
7+
* Steps(For Registration):
8+
```
9+
1.for registeration intercept the signup request that contains data you have entered.
10+
2.Click on action -> do -> intercept response to this request.
11+
3.Click forward.
12+
4.Check response it that contains any link,any token or otp.
13+
```
14+
------------------------
15+
* Steps(For password reset):
16+
```
17+
1.Intercept the forget password option.
18+
2.Click on action -> do -> intercept response to this request.
19+
3.Click forward.
20+
4.Check response it that contains any link,any token or otp.
21+
```
22+
23+
### Author
24+
* [@Virdoex_hunter](https://twitter.com/Virdoex_hunter)
25+
26+
27+
28+
29+
30+
31+
32+
33+
34+
35+
Resources:Google,Twitter,Medium
36+
Please follow me on twitter @Virdoex_hunter.

‎Authentication_Bypass/OTP_Bypass_through_Response_Manipulation.md‎

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
# OTP Bypass response manipulation( Register or login or password reset )
2+
3+
### Steps:
4+
5+
```
6+
1.Register 2 accounts with any 2 mobile number(first enter right otp)
7+
2.Intercept your request
8+
3.click on action -> Do intercept -> intercept response to this request.
9+
4.check what the message will display like status:1
10+
5.Follow the same procedure with other account but this time enter wrong otp
11+
6.Intercept respone to the request
12+
7.See the message like you get status:0
13+
8.Change status to 1 i.e, status:1 and forward the request if you logged in means you just done authentication bypass.
14+
```
15+
16+
17+
18+
19+
20+
21+
22+
23+
24+
25+
26+
27+
28+
29+
Happy Hacking.:)
30+
Resource Google,Youtube,Twitter
31+
32+
Impact:auth bypass,account takeover etc.
33+

‎BrokenLinkHijacking.md‎ renamed to ‎BrokenLinkHijacking/BrokenLinkHijacking.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,19 @@
88
Ouput will be like Something.
99

1010
`─BROKEN─ https://www.linkedin.com/company/ACME-inc-/ (HTTP_999)`
11+
12+
3. Now you need to check if company has the page or not , if no then register as the company or try to get that username or url.
13+
14+
## Alternate Step
15+
1. Go to [Online Broken Link Checker](https://ahrefs.com/broken-link-checker) Or [Alternative Online Broken Link Checker](https://brokenlinkcheck.com/)
16+
2. Input the domain name
1117

1218
# Reference
1319

1420
[https://edoverflow.com/2017/broken-link-hijacking/](https://edoverflow.com/2017/broken-link-hijacking/)
1521

1622
[https://medium.com/@bathinivijaysimhareddy/how-i-takeover-the-companys-linkedin-page-790c9ed2b04d](https://medium.com/@bathinivijaysimhareddy/how-i-takeover-the-companys-linkedin-page-790c9ed2b04d)
23+
24+
### Author:
25+
* [@KathanP19](https://twitter.com/KathanP19)
26+
* [@cyph3r_asr](https://twitter.com/cyph3r_asr)

0 commit comments

Comments
 (0)