
BV CyberSec -- https://teapawt.net/t.co/fNnHyNrpHO https://teapawt.net/t.co/30RvJtEghC -- Associated with @BitcoinVN_io
Globally
Joined May 2026
- Tweets103
- Following38
- Followers22
- Likes58
BV CyberSec retweeted
publishing a page where we are sharing everything we know about the movements of the hacker and their ongoing cascade attack on Bitcoin payments infrastructure
Phase two of our 19 September disclosure: a public page that follows the stolen coins, updated as they move.
Follow-up post:
blink.sv/blog/phase-two-follβ¦
Tracking page:
bounty.blink.sv
Bounty terms:
blink.sv/bounty-terms
On 3 October we published the post-mortem of the attack and a 50% bounty on the stolen funds. That was about what happened inside Blink. This is about where the money went.
The page lists every address, transaction and Lightning channel we can tie to the attacker. Anyone can check each one on the public blockchain.
Why public:
We want everyone working on the bounty to have the same data we have, as up to date as ours, so they can be as effective as possible. The page is that data: we update it when the coins move and when we confirm something new.
We are unlikely to catch him on our own. He is careful: his main Lightning node is reachable only over Tor, and his activity is spread across all hours of the day. What he cannot hide is the coins. Every time they move, they move in public.
He already knows he is being watched, so publishing tells him nothing new. Formal channels matter and we use them, but they take weeks. A public page reaches exchanges, analysts and other teams the same day.
He is still active:
He prepared for weeks. He set up his Lightning node ten days before the attack, and nine days before it he already controlled about 14 BTC. He has not stopped: in the first week of October his main node opened a new channel, a second node of his showed itself, and he moved coins again.
In the same week, on 5 October, he attacked @secondhq, a company that builds its own version of Ark (a new way to make Bitcoin payments), called Bark. He exploited a bug in Second's Ark server and took 0.75 BTC of their own funds; no user funds were affected (their disclosure: teapawt.net/secondhq/status/210806β¦).
He paid for it from the same wallet that received the coins stolen from Blink, and at least partly with those very coins.
We believe he may be preparing a cascading attack: using what he takes from each target to fund the next. If you build on Bitcoin as everyday money, there may be extra reason to be vigilant. If you run a Lightning node, a federation, a swap service or an exchange, check the page against what you see.
What the page shows:
The theft, how the coins moved after it, the coins he held before the attack, his Lightning nodes, his attack on Second's Ark server, and a Lightning wallet that is probably his. Every item is labelled proven, traced or probable. Transactions by exchanges or swap services are marked third-party: they are not accused of anything.
About 0.87 BTC still sits untouched at five of the original addresses, 4.84 BTC at an address that is probably his, and 1.64 BTC at addresses he used in the attack on Second. The whole list downloads as a CSV.
What stays off it:
Anything partners told us in confidence. Personal data. Open security issues. Addresses whose owner we cannot establish. Other teams' incidents, until those teams agree or make them public.
How you can help:
Watch the addresses. If coins move, especially toward an exchange or any service that knows its customers, tell us straight away. Freezes depend on reaching the platform within hours.
Report privately to [email protected] with BOUNTY in the subject. Please don't post leads publicly: it warns him, and it does not establish your priority.
If you run a service and listed coins reach you, contact us before acting. If you control a listed address and are not involved, write to us and we will correct the page.
The 50% bounty stands. 25% of what is recovered goes to whoever provides the information that leads to it, and another 25% to Bitcoin Beach, Bitcoin Ekasi, Afribit Kibera and the circular economies they choose. Everything on the page was already known to us, so re-tracing it does not qualify. Where the coins go next can.
Live updates:
Corrections appear as dated notes; we do not silently rewrite it. Spot an error? Write to [email protected] with CORRECTION in the subject.
We timestamp the page's data on the Bitcoin blockchain with @opentimestamps at launch and with every update.
One more thing:
Blink never charges a fee to recover funds and never asks for keys, seed phrases or payments. Anyone offering "recovery services" in our name is not acting for Blink.
BV CyberSec retweeted
You should extrapolate security failures to the future and not assume they are βoverβ. If we get an inflation bug, it can happen again. If a custodian fails once, custodians will fail again. If entropy is bad once, it will be bad again. Change your BTC behavior based on evidence.
BV CyberSec retweeted
KYC is the crime
Our governments are putting us all in danger under the pretext of defending our children or defending the nation against terrorists.
Meanwhile, domestic terrorists get hold of personal information including home addresses and can come knocking anytime.
ID verification strikes again! 2 days ago 153M driver licenses in US+CA leaked and are now up for sale on a Russian cybercrime forum.
When you give a company your personal information (eventually) it will leak.
krebsonsecurity.com/2026/09/β¦
BV CyberSec retweeted
Today, most sw is vulnerable. The vuln just may haven't been found yet.
Don't rely on others. Build your own custom security harness and run your own scans, *constantly*.
This is not optional. If you haven't started, start now.
Paranoid mode on, and we'll get through this π«‘
BV CyberSec retweeted
When LN first launched I felt pretty nervous running my nodes. I recommend not allowing 3rd party connections or channels but I didnβt do that myself. At any moment only some code is protecting your funds. Over the years that trepidation has reduced, but recently itβs on the rise
BV CyberSec retweeted
π¨π¨π¨π¨π¨ If you are using BTCserver update or turn off π¨π¨π¨π¨π¨
There is a critical vulnerability being actively exploited on BTCPay Server, which can result in the loss of funds.
Please update your BTCPayServer to 2.4.2 by going to Admin Dashboard -> Server -> Maintenance -> Update & verify the 2.4.2 version string in the footer.
If you are unable to update right away, turn off your BTCPay Server to prevent unauthorized access until you can update.
BV CyberSec retweeted
what is happening now for the bitcoin industry is a preview of what will need to happen for every other industry in the upcoming months
it's starting with bitcoin because:
- this is where there is the most immediate and transferrable asset to steal from.
- the security posture of most repos/projects have not caught up with the open source model capability.
but when the low hanging fruits are gone (ie: k3 just doesn't find vulnerability anymore by simply pointing it out in a github repo), then the blackhats will mostly move elsewhere
Bitcoin Red Team Update:
We have been working around the clock, with ~$20,000 of spend up to this point across different services. Funding is secured, I appreciate all the gestures for donations but it is not necessary. The bill is taken care of.
We have done over a dozen disclosures up to this point, with 150 repos scanned. The hardest part is coordinating to get things to the right people (thank you @danielabrozzoni for the help)
I have a first pass on a bitcoin red team agent harness which only requires an @opencode zen api key, makes it easy for us to use K3 for the actual heavy lifting and then GPT Sol + Fable/Opus + GLM5.2 for supporting documentation.
While it is powerful, having found critical issues, I would view this as only version one. There is a lot of iteration I'm looking forward to improving on.
Our goal is to open source the harness so it can be pointed at internal repositories for insights so the hardening of defenses can go deeper than the code which is made public.
We also have been connected with OpenAi for some help so I could manage getting the @OpenAI Cyber Harness running as well (thank you @lylepratt ). Its a much more expensive scan, but well worth it for load bearing portions of the bitcoin ecosystem and has already yielded good results.
Goals for tomorrow are scale in processes and systems so we can do a better job and automating full end to end functionality to get humans out of the loop for the heavy lifting. The first mile (requests/staging) and last mile (handoff of reports) are the choke points right now.
Thank you @stutxo @callebtc @benthecarman @thesimplekid and so may more.
BV CyberSec retweeted
Sometimes, trust your guts. Even when you are told it's FUD. Turns out I was right, and that instinct saved so many fucking people. 5 days later, I think I'm not needed anymore, thank you everyone who trusted me and spread the word so quickly.
I'll write a "post mortem" as I lived it, as I think it's probably going to stay as my most valuable contribution to Bitcoin. Good night people, I hope you are safe.
BV CyberSec retweeted
If you are pointing frontier models at FOSS code bases - cool. Let's ensure the ecosystem is safe, the more eyes the better.
But don't recklessly tweet out to try to spread panic or chase clout.
People are on edge from Coldcard. Responsibly disclose with the team that can actually verify your claims, respond the right way, and then most importantly, safely fix the issue (if it's real).
We've been getting lots of engagement from people across the ecosystem. That's great. But, like with anything AI, even the cyber models can produce slop.
I am not dismissing Floppy's claim here. I acknowledged it and we are looking into it within 30 mins of his posting. Any bug or vulnerability is urgent to us, and we are on it.
But this should be done over email, and not in public where unverified claims can lead to false narratives and unnecessary panic.
And weβre officially above $100m.
And, honestly, thereβs still a long ways to go.
BV CyberSec retweeted
I am simply here to tell you @Rob1Ham is a hero and a visionary and you all have been too busy role playing your little identity wars to appreciate his contributions to this space.
I hope @AnchorWatch becomes a multi-generational institution.
Choose intelligence free from guardrails to protect yourself and your users.
I use Kimi K3.
Thank you @Kimi_Moonshot and all other open-source AI labs. Without your models, we'd still be in the dark.
I am urging engineers who are in the Bitcoin ecosystem, use @OpenRouter or @opencode to use @Kimi_Moonshot K3 on any software you run which interacts with bitcoin in any way internally and any public repos you use.
Other models CAN find issues, but K3 will one shot full vulnerability reports to get an extra set of eyes for security checks.
Some of it will be slop/overstated/wrong, but I've been scanning open source repos and finding things I'll be passing along to maintainers.
Kimi K3 came out as open weights on Monday, and I don't think that is a coincidence as it relates to the COLDCARD issues unfolding.
BV CyberSec retweeted
I know the hype for AI is to accelerate but maybe what we really need to be doing in BTC is to slow down and reevaluate all of the software that came before. So many things are relying on a cost of attack that is no longer present and thus threat modeling has become invalidated.
BV CyberSec retweeted
Key management is an engineering problem. End users are not engineers.
Key management solutions that require end users to make the correct engineering decisions are bad solutions.























