Now Paris himself has been forced to admit that for many years they recommended vulnerable software to everyone working on the dark web under the guise of reliable protection.
Great!
I used this to force them to come clean.
And what other ways are there to use a domain’s private key?
For example, you could set up a fake website by proxying the real one and read all the correspondence and see all the transactions.
It’s really fun when combined with email. Right?
With all your arguments and debates.
And let’s remember—how many projects have been destroyed during this time, and how many people have gone to prison? I think Dread deserves an award from the drug control agencies of many countries.
Day 3: So Why Did We Do It?
Actualizaciones
Oh, and I forgot
Everyone kept asking me why I didn't go for the bug bounty ))
Well, because you can't keep something like that a secret—don't you think?
Everyone needs to know who really sets the security standards on the dark web, for fuck's sake!
And here is a small selection of domains
And here is a small selection of domains that leaked and were passed on to us thanks to Dread — you know them, right? For safety, we are redirecting their traffic to our own project ourselves, okay?
Ask Dread to compensate you for your losses involving the addresses below, and you will be told to fuck off.
Interesting addresses
dreadytofatroptsdj6io7l3xptbet6onoyno2yv7jicoxknyazubrad.onion
dreadlandswkysea676lnblidg3ienxnu2ilzcegxzt3v4hwkhmqz7id.onion
nexusabcdkq4pdlubs6wk6ad7pobuupzoomoxi6p7l32ci4vjtb2z7yd.onion
omega7eye5ar3rkrhfr5odhzmlft7mrygp76fuqkh4kian73nd3b7hyd.onion
primeynxn52jsv3d7mbq2zoehoikid7kv5gv7t3p3n2qeeqdgicxh5yd.onion
Additional domains being published
anopicus6cwgd6mdswsxnujhcajz2p3sfd5kvsdsus7drizhhntvhuid.onion
darkmat3kdxestusl437urshpsravq7oqb7t3m36u2l62vnmmldzdmid.onion
darkmmaugjlnyv7i367vwddz4jkvy2sdlaeutb2uilgs5g3no54mb4qd.onion
darkmmk3owyft4zzg3j3t25ri4z5bw7klapq6q3l762kxra72sli4mid.onion
darkmmka22ckaagrnkgyx6kba2brra3ulhz3grfo4fz425nr7owcncad.onion
darkmmnjhxn5sf3j2rz3hy36kdotf3apgfh4g6iez6cb2q2feazlsuad.onion
darkmmro6j5xekpe7jje74maidkkkkw265nngjqxrv4ik7v3aiwdbtad.onion
Escribir Únete para participar en la discusión.
hmm
are you responsible for the second hack on dread too?
Respuestas · 1
It was one big hack.
bots here and dread is not working? think there is a war behind the scenes
Respuestas · 1
There is a new working link.
Respuestas · 2
That's some lame spam from some kid thinking he's the ultimate haxxor. It shows the whole branding of dread, a bunch of retard.
Respuestas · 2
Definitely.
O yes
yes
Respuestas · 1
First off, nice to see you actively answering yourself. Looking forward to see if this could become a real alternative to Dread. Secondly. How on earth have you made Conclave run so much smoother and faster than Dread?
Respuestas · 1
Well, I've got plenty of other problems that are solved on Dred, like those silly bots. But overall, I'm using a modern stack and working on the project while fending off attacks at the same time. Sorry if I can't always respond quickly.
Respuestas · 1
I'm sure there's tons to do! Keep it up!
We are living in states of surveillance one would be silly to think paris and hug would never be found with current capabilities
The only two mistakes were to trust dread to begin with and put these admins on a pedestal if you did neither and kept your opsec straight you have nothing to fear
Respuestas · 1
Get off that LE cock. They are far from omnipotent. I have heard enough from Dread's admins over the years to know that they know what they are doing.
Comentario eliminado por el autor.
we welcome back all to pm and try our new top of class researchchemical line!!! free samples of 1p-lsd, 5-meo-mipt, ethylhexedron, u47700, furanylfentanyl, and more limit available