Username McUserface ( ͠° ͟ʖ ͡°)

28 reviews, 61% of them positive; 100 WHUF vouched for them by 1 person.61% positive · 28 reviews· 100 WHUF vouched· Influence factor 14, above 3% of accounts

The record

From 25 activities · Apr 2026

A prolific contributor known for sharp analysis of scams, rugs, and protocol mechanics, with deep expertise in crypto, cybersecurity, and privacy narratives. Consistently calls out low-effort reviews and bad actors in the community, though critics dispute whether their negative reviews are always thoroughly investigated or sometimes driven by personal disputes rather than objective analysis.

What people say

Received · 28 Given · 241

“scam DMs”The classic scam DM: "Hi, I’m a Venture Scout at the @techfarmvc team. We are exploring new ideas, early-stage projects, and startups to back. Our team offers comprehensive consulting for growing your project or idea , along with investment and mentorship in exchange for a stake in your venture. We also have multiple open positions within our team. If you’re interested in working with us , we can offer roles such as Investment Analyst, Smart Contract Engineer, Blockchain Developer, Operations Manager, Marketing Manager. Compensation is paid daily in cryptocurrency. If you’re interested , message to our investor in telegram: @ali_techfarm" If you've been in crypto long enough you know this is a scam outreach. Stay safe.

on cpruijsen · 1188· 7mo ago · negative18

“Chief Gaslighter @ ENS”A while ago (February) I've noticed I wasn't seeing any ENS governance updates on twitter. That was because the DAO blocked me on twitter, with no prior interactions between our accounts. I was in the ENS server so I've asked about it. Got kicked and banned - and couldn't rejoin. I mentioned this on my twitter timeline. Suddenly I get a DM from Validator saying he doesn't know why that happened, but they just unblocked me. I checked the twitter, unbanned. I tried joining the Discord again, it worked. They removed the ban. While Validator at least admitted to banning me for no reason in DMs, Danny kept gaslighting me about the ban for some reason. Both on the timeline and in DMs. In his own words: my "accusations" were a problem. Danny continued his gaslighting long after Validator mentioned I was banned for no particular reason. Danny then offered to send me discord logs to prove I wasn't kicked and banned - which were conveniently showing the timeframe from after the DAO/Validator unblocked me on Twitter (and Discord). Apparently according to Danny: discord just magically removed me from the server and prevented me from joining again - until I took it to the twitter timeline 😹 Must have been a weirdly coincidental glitch, huh? People working at core Ethereum infra blocking users to prevent them from seeing governance topics on their timeline is pretty vile. Gaslighting people about it even moreso. See: https://x.com/miyaspokeofthis/status/2022012248840081881 https://x.com/miyaspokeofthis/status/2022022850182328354 https://x.com/miyaspokeofthis/status/2066130807664656456 Apparently this was not the first time the ENS/DAO people abused their power and then kept gaslighting people about it: https://x.com/0xBankable/status/2022341557010203024 https://x.com/0xBankable/status/2022390430168760646 Looks like other users were affected by the power tripping as well. I got a handful of DMs from other people describing similar situations. Majority specifically mentioned Validator, but there's been a few mentions of Danny as well. Mainly about Danny's gaslighting shenanigans and trying to distort the reality. Apparently Danny really loves to gaslight people. Based on my personal experience with Danny - I can certainly confirm his love for gaslighting.

on Danny | 184.eth · 1220· 4mo ago · negative17

“TLD dilution, liquidity extraction, pivot out of web3”I already said a lot in the tweet I've saved via Ethos Agent to @UnstoppableWeb + the review I've left there. The same thing applies to Matt as well. UD is buy once, own forever - no ongoing profits. Which means they have to release new TLDs to stay affloat. Which is how we got all those useless TLDs: coin, 888, crypto, x, wif, u, retardio, nft, wallet, polygon, pudgy, unstoppable, dao, blockchain, go, zil, bitcoin, austin, raiin, tball, dfz, pog, smobler, lfg, dream, mumu, propykeys, bald, wrkx, secret, ubu, witg, metropolis, chomp, ethermail, xmr, wifi, boomer, clay, stepn, tea, npc, quantum, emir, donut, onchain, caw, podcast, doga, tribe, bay, miku. bitscrunch, privacy, rad, ltc, her, xec, kryptic, kingdom, pastor, ministry, nibi, ask, south, calicoin, altimist, hegecoin, bobi, twin, pbdx, mery, bch, mycircle, derad, og, pendle, dejay, depin, xyo, swamp, pengu, hub, brave, hi, bitget, ath, bunni, collect, housecoin, tigershark, arculus, pundi, ohm, cgai, anyone, dsci, chip, pokt, learn, pilot, gotchi, lunar, digibyte, mooncat, zano, pack, imtoken, manga, anime, troll, web3, supernova, demos, carbon, presearch, ai4, goblin, undeads, marketer, spend, amped, mobix, aura, agent, openx, yellow, averge, cashme, enigma, digitalfuture, horizen, awake, super, xz1, agi, basenji, grow, robot, sonic Funnily enough, not even their earliest ones work as you would want them to. If you try looking up someone via etherscan, OS - or even unstoppable domains itself - you might notice that you can't find any user details. As was the case here: https://x.com/miyaspokeofthis/status/2034305562637390244 https://x.com/miyaspokeofthis/status/2034310575006626066 https://x.com/miyaspokeofthis/status/2034319628541800629 Their newest web3 TLD release was a week ago: https://x.com/unstoppableweb/status/2031408468822049003 "Announcing our newest TLD into the Fam - .xz1 to bring independent artists onchain." And a week later Matt dropped this announcement: https://x.com/mattgould/status/2033684862964519041 It took them a whole 7 days to go from "new web3 .xz1 TLD, give us your money" to "fuck web3, we outta here". Matt also tweeted about the pivot out of web3: "the general direction has been laid out for almost 2 years now and we continue to believe it's the right direction." Which means the TLDs they've been pumping out for the last ~2 years were nothing more but a cash grab before they pivot out of web3. I've been around UD since 2021 and it took less than 5 TLD releases to notice the direction they were heading. Some people took a while longer and noticed it around the time the UD discord was nuked as they wanted to be more corpo and didn't need the community feedback anymore. But it's 2026. UD has 140+ worthless web3 TLDs. And they don't care about web3 or their userbase anymore. So why should you?

on Matthew Gould · 1286· 7mo ago · negative17

“unsafe CEX that doesn't pay out bounties by claiming things work as intended - then silently tries to patch them”Binance; a "tier 1" exchange with shit tier security and compliance. Back in 2023/24 I've reported something through their bug bounty. Binance claimed it works as intended (=no bounty), then tried to patch it without actually solving the underlying issue. What happened: After being asked to auth a CC payment, I've typed the CVV for the wrong card. Had to redo the transaction but Binance didn't ask for a CVV again - it just went through. If you wonder how that can be possible - it's because Binance stores your CVVs from the moment you add your card. This is a big no-no! This "wrong CVV when auth is requested -> no CVV needed afterwards" thing does get flagged by the users bank account - because they passed on the wrong CVV at first. But if you tried to repeat the action, they didn't ask you to authenticate and just passed the correct CVVs they've stored since the moment you added your card for the first time -> tx went through without ever being authorized by the user. The users bank doesn't detect unauthorized access because it actually gets correctly authorized in the background. The other method, which wasn't detected by the users bank... was just closing the pop up. They ask for CVV -> close pop-up -> repeat deposit -> it just goes through because they pass on the correct CVVs they store. As you might imagine, this absolutely shouldn't be happening. This was(and still is) not only a payment auth bypass at Binance, but a payment auth bypass that is affecting a 3rd party - EVERY SINGLE USERS CONNECTED CC / BANK ACCOUNT. This is a dangerous, unsafe, and non compliant payment system. Saving user CVVs is a big no-no. Not only won't your bank detect unauthorized access because the tx was correctly authorized in the background - but in case of a leak, your full CC details would also be exposed. They claim to have 300M users: https://x.com/binance/status/1998271391016087617 Every single users connected card(s) are at risk. Some users have multiple cards connected, which means that the 3rd party impact is most likely affecting way more than 300M bank accounts 💀 And the method is so ridiculously stupid that literally anyone could do it with 0 technical experience. Your grandma could literally bypass their payment auth 😹 "Binance secured the ISO 27001 and ISO 27701 certificates for meeting the internationally recognized standards in information security governance and privacy information management, respectively." https://www.binance.com/en/blog/compliance/3367416538721239104 "Furthermore, Binance strengthened its compliance credentials in 2025 with 29 certifications and assessments, including ISO 27001 (security), ISO 27701 (privacy), ISO/IEC 42001 (AI management systems), PCI DSS (payment card security), and SOC 1 and SOC 2 reporting." https://www.binance.com/en/blog/ecosystem/5106980969643912604 They mention PCI DSS compliance. That is simply a lie: "PCI DSS Requirement 3.2.2: Do not store the code or the card verification value after authorization." https://pcidssguide.com/pci-dss-requirement-3/ My original bug report included the wrong CVV -> auth (detectable) bypass + closing pop-up to create an undetectable bypass with 3rd party impact + detailed report on their payment system being non-compliant and putting every single user at risk. Binance claimed that... this works as intended? Not once, not twice, not thrice. This case went on and on and on for many many months. I tried to escalate and get someone else from Binance look at the bug report / have the bug report people forward it to compliance team due to payment processing non-compliance on top of the auth bypass with 3rd party impact. "Nah, it works as intended" was an answer via multiple channels from multiple Binance people. I even had the bug platform people escalate it, because it obviously doesn't work as intended. Binance kept claiming their non-compliant payment system is exactly the way it's supposed to be. At this point the bug platform basically said "yeah we see it's an issue, but the client claims it isn't. tough luck but we can't do anything" Funnily enough - EVERY SINGLE TIME I've tried to escalate this - they just added one more pop-up you needed to close - and ultimately they still passed on the CVVs they stored LOL At first you just had to close one pop up. Then two. Then 5. Then 20. Now you can sit there a few minutes closing the auth request pop-up - but in the end it will still go through. Every single pop-up you need to close now is basically corresponding 1:1 to my outreach attempts. All those pop-ups you have to close were patched in after every time I've reached out to Binance. Apparently it might no exactly be "working as intended", so they kept adding more pop-ups you need to close - but they never actually fixed their payment system. (I've been bypassing my own auth since 2023 😅) They still store every users CVVs. They still aren't compliant. All of their users are still at risk. All the 3rd party accounts (bank accounts!) can still be accessed without triggering any unauthorized access flags - because the transactions still get fully authorized via the stored CVVs. This means that getting your phone yoinked - your bank account can get drained because every tx will get fully authorized. This means that should there be a combo exploit that gives someone access to your Binance account - the attacker will have access to your connected bank accounts, and the bank won't flag the transactions as no security flags get triggered. It also means that in case of a leak your full CC details will be exposed. It's not even the fact that some of their security people are incompetent, but the fact that they actually were aware that it's not the way it's supposed to work - hence all the patches to add more pop-ups requesting authorization. But it's not important enough (I mean, only ALL of their users are affected 😹) to actually fix it. And the bigger issue is that they are straight up unwilling to pay out bounties or actually solve security issues. They will just claim it works as intended to stiff you on your bounty and then try to silently patch the issue - without actually fixing it... I got stiffed on $5-10K auth bypass bounty that affected every user and their bank accounts. Additionally this should count as "special" due to the whole non-compliance part of the report, and a special would be worth up to $100k. It's not even the fact that they stiffed me on up to ~110k - but the sheer fact that they were unwilling to actually fix this over the past 3+ years. https://x.com/miyaspokeofthis/status/1837720820203888657 https://x.com/miyaspokeofthis/status/1906393910462578865 https://x.com/miyaspokeofthis/status/2021458445015072973 https://x.com/miyaspokeofthis/status/2021674746752954758 https://x.com/miyaspokeofthis/status/2021648042357927955 So yeah, if you use Binance it might be worth checking your connected cards. If you absolutely need to use CC deposits via Binance then make sure to use a virtual card. You can set up a $1 limit on the card, and only raise it when you want to deposit. Otherwise there is a nonzero chance someone will drain your bank account. And at that point you might encounter another issue. Consider the perspective of your bank. You might claim unauthorized access. To them it looks like authorized access from a service you used in the past. None of the transactions looked suspicious, because they were fully authorized in the background. Many users try to spend money and claim unauthorized access. The banks look really close into those cases. The Binance bank account drain would look like fully authorized transactions - from a service you did actually interact with in the past multiple times. Good luck trying to claim that it was unauthorized access so they can cover it from insurance...

on Binance · 1677· 6mo ago · negative30

“spam tagging people with shitcoin claims”One of the multiple accounts spam tagging people about some shitcoin claim. Even tagging Elon Musk about it 💀💀💀

on David Choukroun · 1328· 6mo ago · negative21

“scam 2.0”The previous collection ("kiwyu") got nuked on OS for stealing art from Hurt Hapas. Not even 10 minutes after the collection got removed from the OS frontend and they already started another mint ("kiwyu NFT") that's using the same stolen assets that got them nuked in the first place 💀 Sadly the new one is already at 750 mints at ~$1 per item. Looks like a serial extractor is porting full collections over to RH and dropping them for $1-10 per NFT. It's not much, but when you repeatedly do it with 10k assets collections @ $1-10 then it quickly adds up and manages to extract thousands of dollars of liquidity from people who have no clue what they're minting... because they are minting every cheap whitelist they got sent. No idea if this profile will get reused for something else or if they will repeatedly launch under the same name with slight variations ("kiwyu" and "kiwyu NFT" so far). Either way, don't give them a cent and be careful what you're minting on RH. So far most of the RH whitelists I've seen posted around are for grift collections following the same pattern as kiwyu. Lots of old remilia (& adjacent eco) assets are being ported 1:1 (artworks, nft ids, traits - everything ported 1:1) to RH and minting for less than $10 a piece. Scammers are mainly targeting communities like cash cats with whitelists and people mint their WLs blindly because they are cheap. This just lets scammers thrive with ultra low effort grifting...

on kiwyu · 927· 2mo ago · negative16

“slop poster”"Overall," this account has posted a LOT of slop reviews. https://app.ethos.network/profile/x/matchamilk_4?activities=given "Overall," maybe you should stop copy pasting slop and write at least a single review by yourself. Stop the slop brah.

on Anndrop · 1184· 2mo ago · negative16

“optimism cofounder stealing other peoples work”@tyneslol aka @Optimism and @OPLabsPBC cofounder reminted "Mi Note 2" by @639_yomme on Zora without credit. Got caught, then sent some "sorry for stealing your work bribe ETH" to a yomme impersonator 💀 Wow, I guess L2s are truly dead when the cofounder of Optimism has to resort to stealing other peoples already minted art and reminting it on Zora for profit. How down bad and spiritually broke can you be? Also if you can't even read the username and send money to an impersonator requesting ETH - it's a pretty bad image for yourself and everything you've built. https://x.com/guruguruhyena/status/1960888327911125417 https://x.com/639_yomme/status/1960890728101654737 https://x.com/badboykrys/status/1960892386021724190 https://x.com/badboykrys/status/1960893279148642376

on Optimism · 1886· 1y ago · negative20

“amazing tool”Heard about anticapture amidst the ENS treasury takeover by Nick. Amazingly useful tool. Example: https://x.com/LefterisJP/status/2070612273832374313 https://x.com/miyaspokeofthis/status/2071149360297955650

on anticapture · 1231· 4mo ago19

on WhiteBold99Ⓜ️Ⓜ️T · 1216· 55d ago · negative15

“Retarted and cute :)))”retarts are NFTs by the one and only peepeepingus :)) some are random creations that end up listed on the market and some are custom made - but all of them are equally as retarted and cute 🤍 Retarts are imho what veefriends wanted to be (but failed becoming). I kinda get what Gary tried to make with veefriends, but it ended up being so soulless. retarts are on the other end of the spectrum (heh) and full of soul and fun and friendship :)))

on retart 🍎 · 1220· 1y ago15

on etherscan.eth · 1494· 4mo ago · negative14

‹ Back108 of 241 · most upvoted firstMore ›