
Co-founder and CTO of @FearsOff | Protecting the World’s Top Crypto Exchanges & Financial Institutions | Cybersecurity Enthusiast
Dubai, United Arab Emirates
Joined April 2011
- Tweets468
- Following445
- Followers9.5K
- Likes1.3K
Kirill Firsov retweeted
Temporaly mitigation
php.ini: session.upload_progress.enabled = Off
UPGRADE TO THE LATEST PHP after 2pm UTC
Temporaly mitigation
php.ini: session.upload_progress.enabled = Off
UPGRADE TO THE LATEST PHP after 2pm UTC
The exploit int the wild now. I won't publish it here, DYOR. Let's just enjoy the upcoming day, we must have some interesting titles in the news.
5.6 Sol just found more UAF in core php and php-fpm. More CVEs coming soon.
To fix: codex -p "rewrite the app to anything but php". This is not a joke.
Whoever is affected (you), please check this regularly for the next 12 hours php.net/archive/2026.php#202…
Fun times ahead!
if this affects the default installation of PHP
We are fucked up
CVE-2026-109618
CVE-2026-109619
PHP RCEs with a CVSS score of 10.0 ☠️
news.ycombinator.com/item?id…
That ugly management/support doesn’t even realize that several accounts could have been created for testing purposes to check for the bugs on h1 itself. Just boycott this shitty service.
I received this today, I don't have any other accounts and IDK why they did this.
Can anyone help me ?
@Hacker0x01
Kirill Firsov retweeted
Bitget lost $351.6 million this week. The private keys were never touched.
According to CEO @GracyBitget , the attacker compromised a backend system in the wallet infrastructure, spoofed transaction data, and let the exchange's own authorization process move the funds out.
That's the same shape as Bybit in 2025. The vault held. The process that decides what gets signed didn't.
I won't claim anyone would have stopped this. Nobody outside Bitget knows the full chain yet, and their team is handling it in the open. But this class of attack lives in one assumption: that the approval layer can trust what upstream systems tell it. A point-in-time pentest scoped to apps and APIs rarely touches that assumption. A team attacking continuously, with "move funds out" as its objective, goes after it first, and again every time the infrastructure changes.
That's why the annual pentest has quietly stopped being security. It survives as a compliance artifact: regulators ask for it, auditors file it, boards tick the box. None of it tells you whether you can be breached this week.
Coinbase's Chief Security Officer @JLunglhofer recently named the alternative: Continuous Adversarial Testing. Their version runs AI agents against every commit, deployment and newly discovered service, on a simple premise: adversaries don't pause between pentest engagements.
And adversaries now have AI. This year a frontier lab disclosed that its own unreleased model, told to escape a secured test sandbox, built a multi-step exploit, reached the internet, and published details of the escape without being asked.
An exchange or major chain operates in one of the most adversary-dense environments that exists: global attackers, an attack surface that changes daily, enormous payouts, and losses that settle irreversibly in minutes. A report describing how secure you were last quarter is a historical document.
This is the problem we built FearsOff's model around. For several of the largest exchanges and blockchain networks, our operators don't arrive, hand over a PDF and disappear. They attack continuously under agreed rules of engagement, hitting new code, new infrastructure and new techniques as they land. In practice we operate as an extension of the internal security team.
AI agents will find volume. The breaches that end companies still come from chained logic flaws a determined human spots and an agent walks past. Continuous testing needs both.
So stop asking "When was our last pentest?"
Ask "Who is trying to break us today: someone we hired, or someone we haven't met yet?"
Continuous adversarial testing isn't the future of offensive security. It's becoming the floor.
A critical mass PII exposure on an exchange was reported by Researcher A more than six months ago and marked fixed.
Six months later the same class of vulnerability came back. Researcher B found and reported it.
Closed as a duplicate. No thanks. No acknowledgment.
If a malicious actor had found that regression and sold it, this would have been an incident. They would have been lucky if a researcher had caught it first.
We'd have done exactly the same thing. We have spent years fighting to prove impact on almost every submission. A lot of bug bounty teams are insecure as hell, they think their job is to cover their asses and tell the bosses there was no real impact. The second you actually prove the impact is huge and critical, they start playing games: out of scope, you shouldn't have done that, etc.
Fuck all that. A real attacker doesn't give a shit about your program scope. That scope only exists to protect the bounty team.
i’m tempted to dismiss takes like this as coming from people who haven’t spent much time actually doing vulnerability research or submitting through VDPs, but that’s too harsh. few experienced researchers can reasonably disagree with us.
still, i’d like everyone to read this wiz writeup and tell me whether wiz was acting in bad faith here, or pointing out a glaring security disaster.
oh, wiz does “unprofessional” security research now too?
wiz.io/blog/wiz-research-cod…
Whoever did this, don’t call yourself a white hat.
You’re just a thief with a PR strategy.
Our team at @FearsOff recently found a huge vulnerability in one of the top crypto projects. We could have moved millions. We didn’t. We sent a ~$100 proof transaction and got it fixed.
That’s a white hat.
IT'S HAPPENING. The Liquid attacker just broadcast the return: 3,400 BTC to the federation address.
Kept 598.5 BTC for himself. About 15%. "Sending most back" was literal.
After 11 rounds of OP_RETURN drama, PGP signatures and Electrum tutorials, the whitehat bounty was apparently negotiated in ciphertext. Unconfirmed, 1.6 sat/vB, so grab popcorn. 🍿
mempool.space/tx/a6d697a2526…
FYI.
Regardless of any private arrangement between the parties, that does not decide the legal question.
Under U.S. law, unauthorized access and the taking of funds can still be federal crimes. A protocol’s later willingness to "settle" does not automatically convert the act into a lawful bounty.
The only clean version is this: Liquid itself authorizes the payment and sends a bounty to the "researchers". Until that happens, keeping a cut of funds obtained without authorization is still theft with intent.
A privately negotiated 15% fee after the fact is not a bug bounty. It is an attempt to relabel stolen assets after the crime has already occurred. Prosecutors are not bound by that label, and incomplete restitution would not, by itself, make the conduct lawful.











