🇸🇬 PIANIST/UI/UX/Retired Frontend Dev for @famousfoxfed / Solana Maxi / Serpentis Social Club Admin
Singapore
Joined December 2021
- Tweets4.4K
- Following1.5K
- Followers1.5K
- Likes7.1K
Pinned Tweet
Hi, I'm one of the UI/UX guys at @FamousFoxFed .
I turn 40 today. Considering it's also around my 1 year mark as a FFF holder, I figured it's time to doxx myself. 🧵
Winterain 🟠 retweeted
Our message to Nvidia's board:
Do not fire Jensen Huang.
There is no clear replacement for Jensen Huang. We are confident that his departure would ultimately be a net negative for Nvidia, its shareholders, and the AI Revolution.
First, take a look at the data. History also suggests that removing a successful CEO will come with a significant cost.
A study of 187 forced CEO departures from S&P 1500 companies found that removing outperforming CEOs resulted in negative long-term stock returns. This case would be no different, in our view.
Jensen Huang is the definition of an outperforming CEO. Nvidia's board must not make a decision in the heat of the moment.
The board should take the time to conduct a thorough investigation and consult with shareholders, with a strong emphasis on the latter.
Quite literally, Nvidia's board should convene a special shareholder meeting and hold an advisory vote on this decision. This is the most consequential CEO controversy in world history. Shareholders deserve a say.
In addition, Nvidia's stock, $NVDA, is now down -35% in 26 trading days, nearly half of which is a result of the recent scandal.
We believe Jensen Huang's potential removal as CEO is now ~80% priced in.
Why take an action with massive downside potential when the market has already priced in much of that risk?
The downside of retaining Huang may be limited, while the potential upside is tremendous.
Lastly, history shows that retaining Jensen Huang could still lead to a favorable outcome. In 2019, Amazon retained Jeff Bezos as CEO after his extramarital affair became public, and the company's stock subsequently surged +108% by 2021.
Personal misconduct should not be ignored, but it must also be distinguished from corporate wrongdoing and weighed against the consequences of removing an executive who is instrumental to the company's success.
We believe Jensen Huang is an irreplaceable part of Nvidia and the AI Revolution more broadly.
Once the dust settles, firing Jensen Huang would prove to be a costly mistake.
It is time to pause and consult your shareholders.
What about degods?
I don't wanna talk shit about @okaybears , but let's be real. It took them so long to give holders any value. Meanwhile, I'm up 20+ SOL, on @FamousFoxFed in just two months, with weekly rewards....
Just saying🤷🏻♂️
8
Winterain 🟠 retweeted
I went through the on-chain data on the $6.3B Binance hack. What most people are posting is WRONG, and the smartest part of this attack is getting no coverage…
The main drain took 24 SECONDS. Not 20 minutes. About $2.7B left two Binance Ethereum wallets in under half a minute.
How they got in:
Binance says a DevOps engineer's laptop "may" have been compromised. They also say there is no evidence a private key leaked. Both can be true, and that's the interesting part.
An EIP-7702 delegation needs a valid signature from the wallet. If you control a service container that is already authorised to request signatures, you never need the key. You just ask the signing service to sign for you. Same shape as Bybit, where attackers hit a developer machine at Safe.
The transaction itself:
A type-4 tx carrying 50 separate EIP-7702 authorizations, all for the Binance 14 hot wallet, all pointing at the same attacker contract.
Only ONE landed. Nonce range 18,914,775 to 18,914,824.
They didn't know the wallet's exact nonce, so they sprayed a range and let one hit. Blockaid caught this.
The part nobody is talking about:
Within 3 minutes the attacker supplied 60M USDT to Aave as collateral and borrowed 19,762 wETH against it. About $45M.
Tether froze the address right after. Aave froze the markets 46 minutes later.
TOO LATE. They had already turned freezable stablecoins into ETH nobody can touch. Marc Zeller confirmed the position is overcollateralised so Aave isn't out anything.
Where it stands:
Frozen, per ZachXBT: over $2.83B. Roughly 1,767M USDT, 823M USDC, 40.5M RLUSD, 27.8M USD1, 29,934 WBETH.
Still with the attacker: 197,460 ETH, about $436M, plus $122M across 15+ tokens including LINK, AAVE, WBTC and ONDO. Another $19.5M on Arbitrum and $24M on Avalanche.
The wallet was funded with 0.1 ETH out of Tornado Cash. The delegation was removed and the wallet's code was empty again by 01:20 UTC.
The number that actually matters:
$6.3B stolen, about $3B frozen. That's a $3.3B hole.
SAFU took in $1B of Bitcoin earlier this year. It covers less than a third. At least $2.3B comes out of Binance's own corporate balance sheet.
Withdrawals went down at 22:15 UTC, almost two hours after the drain started.
Watch for the updated Proof of Reserves. That's the only document that tells you what Binance actually has left.
I will keep researching the subject, and I will keep you guys updated.
If you own ANY amount of crypto, make sure you're following me so you don't miss any important updates.
A lot of people will regret not following me…
Winterain 🟠 retweeted
Pretty much.
As of the past few weeks, debt markets have almost entirely shut off access to money for any company that doesn’t have substantial revenue independent of AI data centers.
SpaceX closed $40B of debt for GPUs, but we’re investment grade and have Starlink & launch revenue.
That means the 200+ neoclouds are going to see guppy-level death and consolidation. Some will make it through, but not many.
Steps to remedy PHP exploit for people on Amazon EC2
1/ Running PHP on EC2? PHP2Shell (CVE-2026-109618 / 109619) is being exploited in the wild. Unauthenticated RCE, and attacks started as early as Oct 17.
Fixed in 8.2.35, 8.3.36, 8.4.27 and 8.5.12.
2/ Check your version and upgrade:
php -v
sudo dnf upgrade --refresh 'php*' (Amazon Linux 2023)
sudo apt install --only-upgrade 'php*' (Ubuntu)
Then restart php-fpm and nginx/apache.
3/ No fixed package yet? Put AWS WAF in front (via ALB or CloudFront) with the Core rule set's SizeRestrictions_BODY and the PHP Managed Rule Group v2.3. Block multi-part uploads on routes that don't need them.
4/ Check for compromise, going back to Oct 17: look for new or changed .php files in storage/ and uploads, odd cron jobs, and large POSTs in your access logs. Rotate secrets if anything looks off.
5/ Source: aws.amazon.com/security/secu…
1
545
G’damn
So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and Archive.org went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.
48
Wtf?
Effective Immediately, all organizations using PHP for their systems are advised to be prepared for an update addressing two critical vulnerabilities. PHP is widely used for web applications. These vulnerabilities often provide a direct path to the server's file system or database. If an immediate update is not feasible, it is recommend that organizations take the system offline until it can be fully mitigated. NSA will follow up shortly with more specific guidance.
50
Winterain 🟠 retweeted
Your wealth is digital. The device you manage it with should be built for that.
Meet Ledger Atom™: the security of industry leading hardware, the convenience of your everyday apps, plus control over your AI tools, and a rapidly expanding platform of apps, all in one quantum ready device.
Agents propose. You approve. Your Ledger signer enforces.
Winterain 🟠 retweeted
It's amazing to see that Solana was able to advertise and even get an office in China. 👏
@BNBChain was not able to do this, so far. 🤣
Hopefully, what's good for one industry player is also good for the rest.
