Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removed OnlyFans #1775

Merged
merged 3 commits into from
Apr 21, 2023
Merged

Removed OnlyFans #1775

merged 3 commits into from
Apr 21, 2023

Conversation

w3Abhishek
Copy link
Contributor

@w3Abhishek w3Abhishek commented Apr 19, 2023

Recently, @ThePornHelper raised an issue related to OnlyFans false negative. After going through the issue, I tried checking for some popular onlyfans creators on sherlock and as per the issue raised all of them were giving false negative.

So, I checked with the current method of checking the username availability. It the following API url:

https://onlyfans.com/api2/v2/users/grandmasterchefjojo

It returns a 400 error code and doesn't work at all.

Why it's happening? It requires a token be passed in the headers to for it to work.

After this, I tried using BurpSuite to find any other way to check availability and unfortunately there aren't any.

Even the wrong onlyfans.com/thisusernamedoesntexist777 URL also returns 200 in HTTP response.

So, it's better to remove OnlyFans from supported sites list and add it to removed_sites.json

Thanks.

Abhishek Verma added 3 commits April 20, 2023 03:09
Recently, @ThePornHelper raised an issue related to OnlyFans false negative. After going through the issue, I tried checking for some popular onlyfans creators on sherlock and as per the issue raised all of them were giving false negative.

So, I checked with the current method of checking the username availability. It the following API url:

`https://onlyfans.com/api2/v2/users/grandmasterchefjojo`

It returns a 400 error code and doesn't work at all.

Why it's happening? It requires a token be passed in the headers to for it to work.

After this, I tried using BurpSuite to find any other way to check availability and unfortunately there aren't any.

Even the wrong onlyfans.com/thisusernamedoesntexist777 URL also returns 200 in HTTP response.

So, it's better to remove OnlyFans from supported sites list and add it to removed_sites.json

Thanks.
Recently, @ThePornHelper raised an issue related to OnlyFans false negative. After going through the issue, I tried checking for some popular onlyfans creators on sherlock and as per the issue raised all of them were giving false negative.

So, I checked with the current method of checking the username availability. It the following API url:

`https://onlyfans.com/api2/v2/users/grandmasterchefjojo`

It returns a 400 error code and doesn't work at all.

Why it's happening? It requires a token be passed in the headers to for it to work.

After this, I tried using BurpSuite to find any other way to check availability and unfortunately there aren't any.

Even the wrong onlyfans.com/thisusernamedoesntexist777 URL also returns 200 in HTTP response.

So, it's better to remove OnlyFans from supported sites list and add it to removed_sites.json

Thanks.
Recently, @ThePornHelper raised an issue related to OnlyFans false negative. After going through the issue, I tried checking for some popular onlyfans creators on sherlock and as per the issue raised all of them were giving false negative.

So, I checked with the current method of checking the username availability. It the following API url:

`https://onlyfans.com/api2/v2/users/grandmasterchefjojo`

It returns a 400 error code and doesn't work at all.

Why it's happening? It requires a token be passed in the headers to for it to work.

After this, I tried using BurpSuite to find any other way to check availability and unfortunately there aren't any.

Even the wrong onlyfans.com/thisusernamedoesntexist777 URL also returns 200 in HTTP response.

So, it's better to remove OnlyFans from supported sites list and add it to removed_sites.json

Thanks.
Copy link
Member

@sdushantha sdushantha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @w3Abhishek for using the time to work on this issue, really appreciate it! Looks ready to merge! 🚀

@sdushantha sdushantha merged commit c9c97e5 into sherlock-project:master Apr 21, 2023
@w3Abhishek w3Abhishek mentioned this pull request Apr 21, 2023
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants