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

Creating a kind of all.json for other ways of scamming #2417

Open
frankywild opened this issue Oct 13, 2022 · 6 comments
Open

Creating a kind of all.json for other ways of scamming #2417

frankywild opened this issue Oct 13, 2022 · 6 comments
Milestone

Comments

@frankywild
Copy link
Contributor

Hello @jacogr,

I was wondering if it is possible to create something like all.json but for twitter accounts or invite links to telegram such as

[Scam alert] t.me/Polkadot1 or twitter.com/Polkadot_helps

Thanks

cc: @michalisFr

@jacogr
Copy link
Member

jacogr commented Oct 14, 2022

There has been a lot. I think we can even extend the current list with something like „denySubs“.

Also need to adjust the underlying libraries to check and block.

Will look into possible options.

@frankywild
Copy link
Contributor Author

There has been a lot. I think we can even extend the current list with something like „denySubs“.

Also need to adjust the underlying libraries to check and block.

Will look into possible options.

Thanks Jaco

lilsunny243 added a commit to lilsunny243/phishing that referenced this issue Mar 1, 2023
@jacogr jacogr added this to the todo milestone Mar 14, 2023
@jacogr jacogr removed the -size-m label Mar 14, 2023
@frankywild
Copy link
Contributor Author

Hello @jacogr, any updates on this?

Thanks!

@jacogr
Copy link
Member

jacogr commented Jan 15, 2024

No update from me.

There is no reason (although not checked), that we cannot start adding these. There are a couple of options -

  • top-level site, aka
"denySubs": {
  "x.com": [
    "jacogr"
  ]
}
  • explicit links
"denySubs": [
  "https://x.com/jacogr"
]

... now thinking about it, it will probably be dropped if added since we sort these and only extract the deny and allow keys, so it won't check for these. So "just starting to add" would not be kept once CI is done.

Out of the 2 options above, which one is better for the team adding these? (full-url-per-line or grouped-by-domain)

@frankywild
Copy link
Contributor Author

frankywild commented Jan 20, 2024

No update from me.

There is no reason (although not checked), that we cannot start adding these. There are a couple of options -

  • top-level site, aka
"denySubs": {
  "x.com": [
    "jacogr"
  ]
}
  • explicit links
"denySubs": [
  "https://x.com/jacogr"
]

... now thinking about it, it will probably be dropped if added since we sort these and only extract the deny and allow keys, so it won't check for these. So "just starting to add" would not be kept once CI is done.

Out of the 2 options above, which one is better for the team adding these? (full-url-per-line or grouped-by-domain)

I would say the second option because we want to add also telegram/discord/youtube (any other platform where the scam is happening) and would be easier I think.

@frankywild
Copy link
Contributor Author

Hey @jacogr! I hope you are doing well.

I tried to add subdomains here #4275 and here #4276 but the extension is not blocking it, I don't really know why.

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

No branches or pull requests

2 participants