Not sure of the full scope of the attack but I routinely fetch the lemmyverse dataset and see that over the past two days someone has created over a hundred bogus communities at discuss.tchncs.de.
(update) now looking at the timestamps, there is a non-uniform time between community creations often ranging from 2—10min. So it does not look automated. Maybe some pissed off kid manually did this? Or maybe someone who is just testing their attack script. Here is a sample:
… exhibit56355@discuss.tchncs.de 2026-08-05T23:56:07.111126Z exhibit74575@discuss.tchncs.de 2026-08-05T23:56:53.499897Z montage49848@discuss.tchncs.de 2026-08-05T23:57:25.442903Z gallery78147@discuss.tchncs.de 2026-08-05T23:59:49.329487Z archive68564@discuss.tchncs.de 2026-08-06T00:09:18.605958Z portfolio24010@discuss.tchncs.de 2026-08-06T00:12:13.200293Z archive57120@discuss.tchncs.de 2026-08-06T00:12:26.712641Z stills64667@discuss.tchncs.de 2026-08-06T00:18:44.101341Z curated97085@discuss.tchncs.de 2026-08-06T00:20:27.982432Z montage57326@discuss.tchncs.de 2026-08-06T00:25:18.222482Z visuals79552@discuss.tchncs.de 2026-08-06T00:26:32.490046Z portfolio82493@discuss.tchncs.de 2026-08-06T00:31:00.950359Z curated50274@discuss.tchncs.de 2026-08-06T00:32:35.967834Z archive62242@discuss.tchncs.de 2026-08-06T00:33:19.683080Z archive95840@discuss.tchncs.de 2026-08-06T00:37:49.730539Z visuals27150@discuss.tchncs.de 2026-08-06T00:40:28.852659Z visuals37605@discuss.tchncs.de 2026-08-06T00:43:18.418426Z curated85385@discuss.tchncs.de 2026-08-06T00:47:10.542885Z visuals85531@discuss.tchncs.de 2026-08-06T00:49:14.857853Z collection63981@discuss.tchncs.de 2026-08-06T00:51:42.154544Z collection44977@discuss.tchncs.de 2026-08-06T00:53:34.997045Z portfolio58030@discuss.tchncs.de 2026-08-06T01:02:16.596242Z archive79163@discuss.tchncs.de 2026-08-06T01:04:15.370817Z frames63631@discuss.tchncs.de 2026-08-06T01:11:01.770464Z portfolio93081@discuss.tchncs.de 2026-08-06T01:23:46.632166Z …
Maybe it’s not an attack per-se but rather a coded way to signal to a botnet.
0 comments
log in to comment.