Helping builders ship in AI & Web3 @fluxor_ | Blockchain dev | Full-stack (MERN) | Open source contributor | Speaker
1.1.1.1
Joined July 2018
- Tweets1.6K
- Following299
- Followers875
- Likes3.9K
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified.
The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete.
As an immediate precaution, Binance has:
- temporarily suspended deposits and withdrawals while security checks are completed;
- revoked the affected address authorisation;
- engaged law enforcement and blockchain intelligence partners to trace and recover funds.
Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice.
Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions.
binance.com/en/support/annou…
Binance just confirmed the largest crypto heist ever: ~$6.3B impacted.
Compromised engineer’s laptop -> unauthorized withdrawals. No private key leak reported. ~$3B already frozen on-chain (Circle froze >$800M USDC, Tether ~$1.5B+ USDT). Rest is mostly BTC/ETH that can’t be frozen.
They say user funds are safe and they’ll cover everything from SAFU + company money. Withdrawals paused.
Trust in centralized exchanges is always conditional. The joy (or relief) when USDC got frozen shows how much the system still depends on the issuers’ ability to hit the kill switch.
Biggest crypto theft on record, attributed to North Korean hackers. Proof of Reserves update coming. Stay safe out there.
October 2026 internet speedrun: get hacked → ship a patch → file for bankruptcy → repeat. Wild month to be online.
Kanishak 🔜 DevCon VIII retweeted
@kartiktalwar sir please karvado approval @ETHGlobal
🥲😭😭😭
Kanishak 🔜 DevCon VIII retweeted
OCTOBER 21, 2026: A BRUTAL DAY FOR THE INTERNET
Certificate trust failures.
Customer secret exposure.
Critical RCEs.
Platform disruptions.
CDN latency.
Broken builds.
AI service errors.
GitHub. Railway. Cloudflare. Sentry. OpenAI. Anthropic. CircleCI.
Different incidents. Different root causes. One uncomfortable truth:
Our digital infrastructure is only as resilient as its weakest dependencies.
Patch confirmed vulnerabilities.
Rotate credentials on confirmed or reasonably suspected exposure.
Revoke compromised certificates.
Verify before amplifying breach claims.
Build redundancy before the next outage.
The internet doesn’t need more panic.
It needs better security and resilience.
♻️ Repost so developers can investigate, verify, and respond.
Kanishak 🔜 DevCon VIII retweeted
4/ 💻 Open Source Hub
The future of Ethereum is built in the open.
Meet the developers, contributors, and communities advancing open-source technology, exchange ideas, and discover new ways to contribute to the decentralized ecosystem.
With @WarangShankar, @dappdost, @hpdang & @fossasia.
Anyone would like to suggest me some men care products, having too much acne and dark spot on face – at Noida, India
OCTOBER 21, 2026: A BRUTAL DAY FOR THE INTERNET
Certificate trust failures.
Customer secret exposure.
Critical RCEs.
Platform disruptions.
CDN latency.
Broken builds.
AI service errors.
GitHub. Railway. Cloudflare. Sentry. OpenAI. Anthropic. CircleCI.
Different incidents. Different root causes. One uncomfortable truth:
Our digital infrastructure is only as resilient as its weakest dependencies.
Patch confirmed vulnerabilities.
Rotate credentials on confirmed or reasonably suspected exposure.
Revoke compromised certificates.
Verify before amplifying breach claims.
Build redundancy before the next outage.
The internet doesn’t need more panic.
It needs better security and resilience.
♻️ Repost so developers can investigate, verify, and respond.
next week i'll be in mumbai to attend @EFDevcon . any side event is happening before 3rd Nov. to mention the link
@dappingHQ
@ZeroXSpace_
@TeamGRYD
see ya'll in Mumbai for @EFDevcon !🫶
let's connect if you'll be around, i'd like to make new friends, open to listen ideas , cook something together & explore the film city together!
I built the same API in 5 languages today: Python, @golang , @nodejs .js, C++ and Rust.
Then I hit each one with 4,000 concurrent users for 30 seconds, with RAM limits from 4 GB down to 64 MB.
Same endpoints, same Postgres, same Redis. Here's how the race went 🧵
visit link and check the detailed stats:))
github.com/kanishak11-cyber/…
🤖 Made with AI
12/ Takeaways:
• Raw speed: C++, Rust and Go are in the same league. Single-process Python and Node.js aren't.
• Memory: C++ is in a class of its own.
• A cache helps most where the DB driver is slow.
• Config (workers, TCP_NODELAY, GOMEMLIMIT) matters as much as language.