About a year ago, I discovered a vulnerability in software that Dread recommended to its users.
Paris’s explanation of the vulnerability, after consulting AI, was basically correct. The root cause was that I failed to account for mathematical bit width.
All this time, I proxied the traffic and collected the sessions of people who reached my Tor descriptors, proxying the main domain to the premium one and vice versa, replacing content where necessary. This wasn’t magic, just a simple technical task. The lack of JavaScript on the site made it much easier—without JS, there isn’t even a chance to detect this kind of attack. Any phisher will tell you that the hardest part is picking apart all those hashes in JavaScript.
Unfortunately, I never obtained any admin sessions because it depends on chance—or, more likely, the admins don’t use public domains.
There’s nothing truly valuable in your private messages, so don’t worry :) Except for a few chats—I’ll contact those users directly later.
After collecting information for several months, I got tired of it and decided to bring this case to public attention. The way it was carried out was deliberately designed to generate maximum publicity.
So you can continue assuming that there was no hack and that the keys simply leaked.
Написать Join — чтобы участвовать в обсуждении.
uh, I know I have said this before, but can you go ahead and hack DREAD again please. It would really do us all a favor!
I FUCKING hate dread, could you please hack them again and this time actually destroy there server and all data?
Hell yea, keep up the good work. Dread taken down a month after my ban, lmao.
go for privacy not profit, no need to beat dread or make a rivality, just go for people's privacy.
Комментарий удалён автором.
I say so far Conclave is beating the shit out of Dread, just give it a bit more time
I definitely can see a heavy boting presence, most likely Dread's goons :D
Ответы · 1
Yeah, I cleared out the dumbest bots—around 12,000 of them. We’re weeding out the rest as they reveal themselves ))
Ответы · 1
If it helps, I can put together a list of the users clearly using AI to bot this forum.
They're using AI to hit my posts almost instantly, trying to discredit our service and spread FUD.
It's honestly pathetic. Dread goons at their finest. lol.
Комментарий удалён автором.
You've missed the point twice now.
We were talking about things beyond the scope of this specific topic.
You brought up the fact that MITM and hacking are different which I agreed with but I was adding some necessary nuances to that point.
You missed the point.
A Man-in-the-Middle (MITM) attack can lead to the collection of admin and staff session credentials, depending on whether PGP is utilized.
On top of that 2FA can be bypassed using sophisticated reverse proxies.
From there, it is simply a matter of escalating the attack to gain access to a broader surface.
Once admin credentials are compromised, the system is essentially compromised if the attacker is skilled enough.
Ответы · 4
Ответы · 2
You are also under the strong assumption that " all " users verify the PGP signed messages and public PGP key of the markets they shop on, but this is far to be true.
If a user or a sloppy admin falls for a MiTM trap, it's likely that he will keep on re-using that same rotten mirror over time. So 2FA becomes quite useless in this very specific case.
The MiTM will keep on reverse proxying the encrypted message to the user and the decrypted message to the server.
All admins get sloppy at once, at the very least. trust this
Ответы · 1
And the op is Incorrect.
Admin sessions can also be retrieved, ain't no problem with that.
Any sessions and cookies can be passed to the proxy, but sessions expire.
Ответы · 1
No disrespect but how about you double read all my posts above before replying non-sens TO ME ?
What you say and what I say are two different things man, both correct.
Комментарий удалён автором.
Reverse proxies and exploits are two different things indeed.
Both remain dangerous and under very specific circumstances a proxy could also affect the service by allowing for a broader attack surface
Ответы · 1
Комментарий удалён автором.
They have full access because this isn’t a login page—it’s a reverse proxy from one domain to another. This is a classic man-in-the-middle (MITM) attack.
Ответы · 1
Комментарий удалён автором.
Комментарий удалён автором.