🔺 🦁 Owner and Dev for https://nitter.cf/t.co/H5hD3WHWCE
Joined March 2021
- Tweets6.1K
- Following731
- Followers412
- Likes58.2K
Tekholms.aptm retweeted
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…
Tekholms.aptm retweeted
User funds are safe!
It does look like a hack on Binance. Appreciate the quick freeze from Tether (~$971m) and Circle (~$823m).
I don't manage Binance (.com) anymore, but as a shareholder, I expect all user funds will be fully covered.
Tekholms.aptm retweeted
The epoch flipped last night 🔺
Fees and vote incentives are ready to claim, and last night’s votes are now directing emissions for the next 7 days.
Tekholms.aptm retweeted
Epoch #54 ends in a few hours 🔺
Voting closes tonight at 8:00 PM ET. Your vote helps decide which pools get the next round of PHAR emissions - so make it count.
Vote here: phar.gg/vote
Tekholms.aptm retweeted
TRACEHOUND IS OPEN SOURCE.
the tool behind every hack we've traced is public:
github.com/localminimaa/trac…
what's inside:
> the tracer: one address or exploit tx in, the whole money trail out
> ethereum, solana, tron, bitcoin + bridges and thorchain crossings
> funding trails: who paid the hacker's gas
> token check: dev history, bundles, snipers, sold %
> pump ring detection across early buyers
every finding links to a transaction you can open yourself.
no black box. no "trust us, it's lazarus".
run it locally with your own keys, or paste an address on tracehoundpro
we chase hackers for a living. hiding our code would be a weird look.
something's coming for the people who use it. today. 👀
Tekholms.aptm retweeted
Why does liquidity matter?
It keeps markets moving. More liquidity means better execution, less price impact, and deeper markets.
That’s what we’re building at Pharaoh 🔺
Tekholms.aptm retweeted
When tokenized stocks trade 24/7 on Pharaoh, assets have to move fast and the liquidity has to keep up.
Sub-second finality on @avax means pools reprice as trades land. No lag, and no waiting for the chain to catch up 🔺
Tekholms.aptm retweeted
Concentrated liquidity puts your capital where the trading is actually happening, instead of spreading it across prices that rarely get touched.
Earn more fees while you’re in range.
Here’s how to set one up on Pharaoh 👇
youtube.com/watch?v=IFM001t6…
Tekholms.aptm retweeted
messaging my wife a link containing proof of her husband cheating on her from an anonymous instagram account and then when she clicks on it texting her to let her know she failed the family phishing test and she has to retake my cybersecurity course
Tekholms.aptm retweeted
Boy howdy, that's a fat swarm.
Readers added context they thought people might want to know
The 4.2 Tbps DDoS attack occurred on October 21, 2024, and was the largest Cloudflare had reported at the time. Larger attacks have since been mitigated, including 5.6 Tbps later in 2024 and 31.4 Tbps in 2025.
blog.cloudflare.com/ddos-threat-re…
blog.cloudflare.com/ddos-threat-re…
Tekholms.aptm retweeted
How is Brazil actually using DeFi right now? @Team1BR: staking, LPing, and holding spot.
Less volatile trading, more positions that don't need watching. Worth knowing if you're building for this market 🔺
Tekholms.aptm retweeted
Been updating this site throughout the day, started with around 75 interesting finds, now am at 462 demos covering 425 libraries in 23 sections!
Get some webdev inspiration at
webdev.teknium.io/
Someone showed me this new JS Library for dithering visualizations so I gave it to Hermes Agent, said make me a webpage full of demos for all the lesser known cool styles and components libraries out there.
In 20 minutes it did, and there's some amazing stuff it found. This webgl fluid library is so sick.
Check it out here: webdev.teknium.io/
Tekholms.aptm retweeted
introducing pwn.watch 👀 one place for following all the live security incidents
it serves rss + llms.txt so u can paste to your clankers
tell them to watch it on a schedule and sleep at night 😴
100% free but kitze.io/sponsors will appear on it ❤️
Tekholms.aptm retweeted
Admin keys for Swell DAO's swETH and rswETH appear to be compromised (railway related?)
* Attackers are raising NAV by max 1% (unbacked) each hour
* Four malicious upgrade contracts have been deployed (although not queued yet through multisig) that could steal approx 2500 ETH
Tekholms.aptm retweeted
October has been an absolute nightmare for software
> Railway - customer secrets exposure
> LiteLLM - malicious PyPI + Docker releases
> Zeabur - infrastructure breached
> OpenCode - AI API keys exposed
> OVHcloud CLI - official binaries backdoored
> Rank Math PRO - malware in official plugin
> TeamUpdraft - customer data compromised
> ConnectWise - cloud backup identities compromised
> Tensorlake - npm package infected
> SubQuery - backdoored npm package
> GhostAction - GitHub repos with malicious workflows
> PHP - critical RCE vulnerabilities
> Node.js - security vulnerabilities patched
> eMudhra - certificate authority keys compromised
> Tailscale - eMudhra incident
At this point, the biggest security risk might not be the code we write, but the code we trust...