BxV

I've pushed a fix to balooProxy lite which should have hopefully fixed random crashes some people were experiencing

If you experience crashes/errors with the gofiber version please dm @ddosmitigation. There seem to be some people who have issues with it

i've released a lite version of balooProxy, which uses gofiber instead of net/http for increased performance. It's only known drawbacks so far are not having http/1 support and not having the http.query field available in the custom firewall rules engine. I would recommend trying it out. Some changes that are in this version, that i will implement into balooProxy main later on are: - Attack notifications also trigger when an attack doesnt bypass - Some improvements in tls fingerprinting

I'm currently working on a lite version of balooProxy, which uses gofiber instead of net/http. While i'm already at it, should i make it so the ddos notifications also get triggered when the attack doesnt bypass?

purged the scammers/ddosers channel. As he deserves

I've made an announcement about "zenection" / @txpmystery before. He used to have the channel "deadleaks", which just distributed malware, now he's apparently selling/making ads for nets. He's currently holding a vote on who is a scammer in his own channel "Mystery Rate" and is getting pretty embarrased by the results. Feel free to vote on it aswell :P

Not sure if anyone cares, i made a program for golang that allows you to prettymuch use telegram bots like discord webhooks (an example of how the webhooks can look like is seen in the image) https://github.com/41Baloo/TeleHook

should've squashed the major bugs. should work as expected now

@BalooDstatBot is back. Enjoy it while it lasts

balooProxy has been updated to 1.4. Performance drastically improved and the previously somewhat unfinished API has been expanded upon and made it easier for you to add your own api endpoints. At the moment it's a readonly api. I might add editing endpoints down the line aswell, as of right now, if you want them, feel free to make them yourself and open a pull request on the github.

bxv.gg might display just a black screen in a while (~2 days). We're testing a new obfuscation method.

For the love of god, stop using services that cannot even make their own design like skl[.]team, which stole "their" design from cotoax[.]com. If they have to copy and paste their design, their code is more likely than not also copy pasted.

Remember the kid that spreads malware in his "leaks" channel? @zenection and his alt @jennejdidjd. Feel free to bully him about his horribly working website that's down 99% of the time that he enjoys flexing as "unhittable" bullingov[.]ru

Since people keep asking. @BalooDstatBot is offline. Probably forever

Reminder of why you should NOT buy stressbot[.]io ALL, each and every single one of their powerproofs is FAKE. In this example they claim to have hit some other stresser that downed them, i assume to get "revenge". However, said other stresser uses cloudflare, meaning instead of he 502 Bad Gateway nginx error, a cloudflare error would have shown. Further, the font is obviously not the actual nginx font. Tl;dr: Stressbot[.]io fakes ALL their powerproof. They are a known scam stresser

balooProxy has been updated to 1.3. It should be more stable, require less cpu and also has some basic headless browser checks intigrated into the js challenge (feel free to make a pull request if you have any better detections)

Reminder not to buy stresslayer[.]pro / cryptobooter[.]us This video was made by their owner. He sent his entire network (12 concs) of browser to baloo[.]one 5 months ago. He lagged his own internet to make it seem like the website was lagging but even with that, website loaded like a beast. (He later inspect elemented checkhost screenshots, more proof can be seen further up in our channel (https://t[.]me/balooxvoltic/256)) Tl;Dr: cryptobooter[.]us is a scam with 0 power (it can't even hit 74[.]74[.]74[.]74. Not even kidding)

@BalooDstatBot back up, now stop crying please

bxv.gg locked again, royalhosting doing *whatever*, we don't even know at this point https://status.royalehosting.net/