274

FYI admins

cross-posted from: https://quokk.au/c/fediverse/p/1066667/tesseract-dev-injects-malicious-code-into-browser-to-illegally-ddos-the-dbzer0-instance

As part of the devs farewell message on their site, they have included malicious code to make each visitor sends 2,000 requests to the dbzer0 servers in an attempt to DDOS and take the instance offline.

top 50 comments
sorted by: hot top new old
[-] db0@lemmy.dbzer0.com 41 points 2 months ago
load more comments (2 replies)
[-] cRazi_man@europe.pub 85 points 2 months ago

Gotta say, I've enjoyed this whole drama. This seems like the end of the story arc. It's been fun guys. Better than beans.

[-] craftrabbit@lemmy.zip 52 points 2 months ago

Yeah, also this makes me really happy that we're on the fediverse. Turns out some part of the system is run by a strange control freak? Swiftly replace the part and everyone moves along.

[-] KurtVonnegut@mander.xyz 16 points 2 months ago
[-] eldavi@lemmy.ml 5 points 2 months ago

only works for the ones lucky enough to catch it -- a tiny minority is likely considering that piefed was caught doing something similar and it's still on track to be one of the largest instances on the fediverse nonetheless.

[-] magnetosphere@fedia.io 23 points 2 months ago

Agreed. I usually don’t care about online drama at all, but at least this has been… amusing.

[-] db0@lemmy.dbzer0.com 42 points 2 months ago

The memes have been fresh!

[-] magnetosphere@fedia.io 24 points 2 months ago

You deserve more credit. Thanks for bringing it to everyone’s attention!

load more comments (1 replies)
[-] goferking0@lemmy.sdf.org 13 points 2 months ago

I hope it's the end but like the piefed stuff we think it's done then something else comes up.

Plus the dev/user/admin of dubvee has said a few times they're leaving only to be back soon after saying that. Hell there were two or three announcements tesseract work was stopped 🤷

[-] cRazi_man@europe.pub 13 points 2 months ago

Gotta leave the door open for a next season sequel with a sneaky post credits scene.

[-] KurtVonnegut@mander.xyz 8 points 2 months ago
[-] goferking0@lemmy.sdf.org 8 points 2 months ago

Piefed dev doing something similar on the flagship instance, and has some odd philosophies on what should be filtered out in the code.

When people started pointing it out and asking questions called it harassment and tried to get instances to instance ban them all.

Best part was insulting everyone looking at the code if you didn't ask on their specific comm.

load more comments (1 replies)
load more comments (1 replies)
[-] jerkface@lemmy.ca 4 points 2 months ago

I dunno, this opens the author up to a lot of consequences other people might choose to pursue.

load more comments (5 replies)
[-] Valmond@lemmy.dbzer0.com 48 points 2 months ago

What a loser. Tiny whiny loser.

Fabulous reaction time from db0 & team!

So who is this loser, I mean it's a tiny whiny bit illegal what he did it seems...

[-] A404@lemmy.dbzer0.com 39 points 2 months ago
[-] db0@lemmy.dbzer0.com 67 points 2 months ago

Already known and mitigated.

[-] ggtdbz@lemmy.dbzer0.com 14 points 2 months ago

Not to expose anything that’s best left internal, but is this something the proof of work check handles? Is it something that’s been implemented in advance? Just curious, if you can talk about it at all. I’m woefully undereducated on the actual ins and outs of the web.

[-] naught@sh.itjust.works 9 points 2 months ago

They can block requests from a specific origin or implement tailored rate limiting rules or disable CORS from that instance. Probably more too

[-] unwarlikeExtortion@lemmy.ml 10 points 2 months ago* (last edited 2 months ago)

The problem is that this is a client side javascript-based attack - meaning your browser sends these malicious requests. So a DDOS, not "just" a regular (centralized) DOS. Anyone opening the page with javascript turned on (which is 99% of real users, however for Lemmy the statistic's surely a bit better) is an "attacker".

You can - once you know of the nature of the attack (this one's relatively simplistic), just react to any realistic-looking request and ~~block~~ ignore the malicious ones - in this case garbled rng output.

Rate limiting would only lead to what the attacker wants - legit users (who are unknowingly sending these malicious requests) being blocked from accessing the site.

[-] db0@lemmy.dbzer0.com 6 points 2 months ago

For this kind of stuff you can easily ask an llm and it will give you a pretty decent rundown of mitigation tactics

load more comments (1 replies)
load more comments (2 replies)
[-] minty@aussie.zone 30 points 2 months ago

Wow lmao. This is crazy levels of petty

[-] Abyssian@lemmy.world 25 points 2 months ago

"Tesseract dev found to have world's smallest and most rancid penis."

[-] Telemachus93@slrpnk.net 23 points 2 months ago

What the actual fuck? This idiot may have his braindead opinions and do to his OSS project whatever he wants (so sag I wasn't on the list), but that is just such a fucked up thing to do.

[-] Draconic_NEO@lemmy.dbzer0.com 21 points 2 months ago

It just gets worse and worse. I figured that the goodbye message he posted wouldn't be the end of it. Thankfully it seems to be down now so it's not causing harm anymore directly but still.

[-] Rocketpoweredgorilla@lemmy.ca 17 points 2 months ago* (last edited 2 months ago)

This whole thing reminds me of the guy (Angled/LMAO) 3 years ago that was all butthurt after he got busted trying to take all the good sublemmy names, and responded by posting a bunch of disgusting stuff with alts and DOSing lemmy.world.

Edit https://lemmy.world/post/1720870

load more comments (1 replies)
[-] kittenzrulz123@lemmy.dbzer0.com 14 points 2 months ago

Im sure some shitlibs will still defend this

[-] db0@lemmy.dbzer0.com 12 points 2 months ago

Where is @Kirk@startrek.website when you need him most?

[-] SkaveRat@discuss.tchncs.de 8 points 2 months ago

not convinced that's not a sock puppet, from all the stuff I've seen so far

[-] db0@lemmy.dbzer0.com 16 points 2 months ago* (last edited 2 months ago)

He kept claiming they're AP, but refused to provide proof. Not sure but as it happens, startrek.website defederated us as soon as we banned him.

[-] goferking0@lemmy.sdf.org 12 points 2 months ago

Huh, weird how the framing of the defedederation lines up so well to what ap and Kirk would say.

https://startrek.website/post/42709922

If you’re not familiar with how Lemmy/the Fediverse works, basically everything you read at StarTrek.website is hosted by us, even if the content originated elsewhere. That means we are responsible for everything here and we have to decide if we are comfortable boosting content from other instances.

If you’re curious, the final straw here was learning that db0 explicitly allows hosting discussions about hurting people, which needless to say goes against our instance values and we simply don’t have the manpower to moderate that volume of content incoming from their server to a degree that we feel meets our quality standards, which left defederating as the only viable option.

In keeping in line with past trends we’re announcing this because is is a larger instance and don’t want to leave any of the crew confused as to why something may be missing.

load more comments (2 replies)
[-] OwOarchist@pawb.social 13 points 2 months ago

I wonder if you could actually track him down and prosecute him for it...

[-] wiccan2@thelemmy.club 22 points 2 months ago

The domain seems to be registered to SquareSpace so his details are hidden from public view but there is a SquareSpace abuse email and US phone number.

I suspect in the first instance if db0 complained to them the site would be shutdown and SquareSpace would then have to comply with any legal action.

INAL but I strongly suspect that the DDOS would constitute a crime in the US where the domain is registered.

[-] SpikesOtherDog@ani.social 7 points 2 months ago

Yup. Anyone knowingly assisting would also be implicated. Afaik, the precedent was set about 20 years ago with the whole LOIC/anonymous ddos.

[-] Taleya@aussie.zone 7 points 2 months ago

Nah he's hosted on inmotion. I already bipped 'em

[-] wiccan2@thelemmy.club 11 points 2 months ago

The domain is registered to SquareSpace: https://who.is/whois/dubvee.org

The IP associated with the domain points to Inmotion: https://who.is/whois-ip/ip-address/107.161.30.39

Looks like both are true, hopefully Inmotion will take appropriate action based on your report. Worthwhile reporting to SquareSpace too so he can't just rehost an attack elsewhere.

[-] Taleya@aussie.zone 17 points 2 months ago

Registrar and hosting are different things.

Registrar is who you bought and manage the domain name you use on your site through. Hosting is where it lives.

Most domain name registrars do not give a single shit what you do with a domain name, unless they're somehow on the hook. Hosting on the other hand.....

[-] wiccan2@thelemmy.club 6 points 2 months ago

I understand how it works.

All I'm saying is the registrar should also be notified otherwise the site can be moved to another hosting platform.

If the registrar can be convinced to take action, at least the domain can't be used for future attacks.

load more comments (1 replies)
[-] 20cello@lemmy.world 9 points 2 months ago

Idk what this tesseract is and at this point I'm too afraid to ask

[-] SCmSTR@lemmy.blahaj.zone 7 points 2 months ago

Actual lmao

[-] naevaTheRat@lemmy.dbzer0.com 5 points 2 months ago

Isn't that like seriously criminal in the usa lol?

load more comments
view more: next ›
this post was submitted on 27 Jul 2026
274 points (98.9% liked)

/0

2235 readers
1 users here now

Meta community. Discuss about this lemmy instance or lemmy in general.

Service Uptime view

founded 3 years ago
MODERATORS