Closed Quartinal closed 8 months ago
bro thinks he owns the repo 😠we are NOT partnered 💀
But this works 👈
By the way, have you even tested this!?
i know it works 👈 but this is the place for issues(?!) also most people can't install ublock 🫢 so quit it before i block you from my profile 🤓
Fine, just block me. I was trying to help by showing people how to find a way to make your KillCurly work (solves #39).
You are the one that should be blocked, with your current attitude. By the way this is not off-topic, you could just edit your README based on my initial issue.
also most people can't install ublock 🫢 so quit it before i block you from my profile 🤓
Do you have any proof of this?
I might as well fork your repo and advertise you, Zek, as the one who should be blocked.
also most people can't install ublock 🫢 so quit it before i block you from my profile 🤓
Do you have any proof of this?
yes, actually. 9 times out of 10 ublock is not able to be installed
I might as well fork your repo and advertise you, Zek, as the one who should be blocked.
you aren't scaring my lil bro
and what you just did is actually against githubs TOS, you marketed an unsafe and vulnerable method to inject javascript to users
lol
From 3kh0's
ext-remover
thingy (in the case that uBlock isn't blocked as an installable extension), I found a way to make your KillCurly exploit work 🎉Essentially, you would follow the instructions here.
Once you have that done, you would press
ctrl
+alt
+~
until you see theEval:
alert.Then you would evaluate:
Since this is JavaScript evaluation only, you wouldn't put the
javascript:
like you would in a bookmarklet.I recommend going to Securly to do all of this because that's where the kill script is meant to work.
If this doesn't work, you would use Bypassi's INSECURLY exploit or Skiovox.
I hope you guys enjoy this 🫰