Nicolas T.

Ancien administrateur de forum (darkweb)
OSINT · OPSEC

[Nicolas T. @_NicolasT3_]

@zaddyinchief @Sans_Google It's possible yeah...

[Nicolas T. @_NicolasT3_]

@THD_IT Il est absolument zéro ce serveur par rapport à tour ce qu'il y a sur Discord ou Telegram...

[Nicolas T. @_NicolasT3_]

@CCITIC_ORG L'Express est le dernier journal à vous donner du crédit non ?

[Nicolas T. @_NicolasT3_]

Vous avez fait des recherches avant de pondre cet article ? Des dizaines de groupes Telegram sont bien pires que celui-ci... Et même sur Discord, vous êtes passés à côté de serveurs bien plus dangereux... Bref, l'Express doit être parmi les derniers à apporter du crédit au CCITIC...

[Nicolas T. @_NicolasT3_]

@KuptoKosmos @Revolut Et les choses ne feront qu'empirer...

[Nicolas T. @_NicolasT3_]

@Nikitont @ether_fi @wirexapp @okx @BleapApp @Plasma @coca_card KYC everywere...

[Mark Karpelès @MagicalTux]

Some very interesting details on the Revolut attack which affected ~680 people on how it was allegedly performed.

https://t.co/nqnGXY8Zjc

[lesh @lesh534]

It has not even been a day since Revoluts fuck up and Felix Romer (Owner of Gamdom) has already been robbed by 2 black masked individuals

[Nicolas T. @_NicolasT3_]

@Get_Waltio Comment Waltio est encore debout alors que son incompétence à amené à la séquestration de dizaines de ses clients ?

[Nicolas T. @_NicolasT3_]

@lizardcircles Just don't give your phone to feds and it's ok

[lesh @lesh534]

You can really just use any kind of documents to KYC on stake and gamdom😭

[Groupe Jean Hénaff @JeanHenaffSA]

Nous avons un cahier des charges assez précis et plutôt strict.

[Sam Bent @DoingFedTime]

The Tor Project hates me so much I can't even like their post. Still salty about:

1. Tor Browser's Latest Update Could Get You Fingerprinted
Tor removed a feature that hid your real OS
https://t.co/vnSAjk4POn

2. For 11 Months, Tor Let Users Think They Were Safe
Safety setting did nothing until you restart
https://t.co/Xl9Ts3Hvra

3. For 9 Years Tor Ignored Princeton's Proof: BGP Attacks Can Unmask Millions of Users
Tor knew for years it could unmask users
https://t.co/FfMWuMqAbT

4. The Tor Project Just Gaslit Their Entire User Base
Tor lied to users about removing protection
https://t.co/3fvhYE0FZn

5. $53 Kills the Tor Network (And They Won't Fix It)
Tor network collapses for 53 dollars, unfixed
https://t.co/nS8yH5fh2z

[Nicolas T. @_NicolasT3_]

@ANSSI_FR Blablabla que du vent encore une fois...

[RaidForums @RaidForumsHub]

Old Domain is suspended.

New domain : https://t.co/ueIaAqorLw

Update your bookmarks.

#RF #RaidForums #Breached

[Jean-Baptiste @jb_ma]

Je viens de tomber sur une tentative de hack la plus évoluée et vicieuse que j'ai vu. J'ai d'ailleurs failli me faire avoir
Un faux CAPTCHA Cloudflare, extrêmement bien fait
Décorticage de la technique. 🧵

[Nicolas T. @_NicolasT3_]

@anatolium Le mélange IA-droit est intéressant, hâte voir le résultat, surtout avec cette version de Qwen

[Nicolas T. @_NicolasT3_]

Le Pixel 11 a encore un support matériel minimal de MTE, mais Google a visiblement amputé l’accélération (cache CPU) pour économiser. Les perfs sont si mauvaises que MTE a été totalement désactivé en firmware au lancement.

Avec la QPR2 Beta 4, le support firmware est revenu. On peut l’activer (fastboot oem mte on + kernel custom). Tests en cours pour savoir si ça marche vraiment et à quel prix en performances. Si c’est juste trop lent, le support GrapheneOS sera possible avec un gros caveat perf. Google n’a rien expliqué.

[GrapheneOS @GrapheneOS]

We have good news about the Pixel 11. It still has at least bare minimum support for MTE at a hardware level. We think they removed most of the hardware acceleration from the CPU cache to save money. They ruined the performance so it ended up being fully disabled in firmware. It may still be usable.

Android 17 QPR2 Beta 4 was released on August 28th. It's the first Beta release with Pixel 11 support. MTE support is still completely disabled in the OS and arm64.nomte is unconditionally passed by the firmware to the kernel. The good news is the firmware itself had MTE support added back to it.

It's possible to enable reserving the tag memory for MTE via `fastboot oem mte on`, boot a non-stock kernel ignoring arm64.nomte and use MTE. We're in the process of determining whether it's fully functional and the performance characteristics. It's likely disabled due to performance being ruined.

We expect performance must be quite bad for Google to have decided to entirely strip out support for it in not only the software but also the firmware so that no would could even try to use it before Android 17 QPR2 Beta 4. That's a very strange thing to do. It's at least added back to firmware now.

We reached out to multiple people at Google asking about the MTE situation on the Pixel 11 prior to making our original thread and didn't receive any responses. We still don't know what's wrong with MTE on the Pixel 11. It isn't clear if there are serious CPU errata or it simply performs very badly.

If the issue is simply that MTE performance is poor, then we can support the Pixel 11 with the major caveat that it will be a significant performance downgrade. Aside from MTE, Google downgraded the Pixel 11 series GPU compared to the Pixel 10 series in addition to reducing RAM for base Pro models.

Google has been increasingly silent in response to our communications since dropping Pixel support from AOSP with Android 16 in June 2025. They could have told us MTE performance was significantly reduced so they disabled it at launch but will add it back to firmware for QPR2. That's still unclear.

Android 17 QPR2 Beta 4 releases for the Pixel 11 series were only uploaded around 10 hours ago rather than with the initial release on August 28th so this hasn't been available for very long. It wasn't missed by us or people who looked into it after our initial thread but rather wasn't out yet.