Statement Regarding the Keeta Security Incident
To the party responsible for the recent attack against Keeta:
Our investigation has progressed substantially, and we have collected evidence identifying the party responsible for the attack.
This includes IP addresses associated with your internet connection and infrastructure used during the attack, including VPN and VPS services; the user agent and technical environment used to make unauthorized requests; email addresses associated with the activity; software and infrastructure providers used in carrying out the attack; and additional identifying information that we are not disclosing publicly at this time. All relevant evidence has been preserved and is being provided to the appropriate parties.
We are offering you an opportunity to resolve this matter directly.
Return all funds obtained as a result of the Keeta attack within 72 hours of this statement. We will accept repayment in KTA, ETH, or USDC. Funds can be returned to the following address on Base:
0xc439eba7E79496F42e996F7EbD5835934f56bec6
Upon the complete return of the funds, we are willing to discuss an appropriate bug bounty in recognition of identifying the vulnerability and work toward resolving the matter without pursuing further legal action.
You may contact [email protected] to discuss the bug bounty and coordinate the return of funds.
This offer is conditioned on the full return of the funds and cooperation necessary to verify that the matter has been resolved.
If the funds are not returned within the 72-hour period, we reserve all rights and will continue pursuing available legal and recovery measures.
We encourage you to use this opportunity to resolve the matter constructively.
Just listened to Ty on Kee Talks discussing the security incident. There was a lot in there, so here are my biggest takeaways.
First, the response.
Within about 20 minutes of the issue, the team was on a call working it. They identified the problem within roughly 30 minutes and had a fix in less than an hour. That fix has been undergoing testing while they work on additional safeguards around the system.
One example Ty specifically mentioned was essentially a circuit breaker. If an anchor detects activity that isn’t normal, it could pause before more damage can occur.
Ty also talked quite a bit about what they’re learning from this.
Keeta is new technology in the sense that many of the individual ideas aren’t necessarily new, but they haven’t been combined into a system like this before. Ty said the system as a whole is something very few humans fully understand.
That makes what happened particularly important from a security standpoint. The affected component had been through multiple audits and reviews by credible auditors and engineers, yet none of them found the issue.
Ty said there is reason to believe AI may have assisted in the attack. His takeaway was pretty clear: the safeguards going forward need to go far beyond what they’ve relied on in the past, including ways of analyzing the system from perspectives humans may not think to look from.
They are also working with authorities, pursuing every avenue to identify the source, and looking at recovery options.
Ty said when he reached out to a series of partners, they responded within minutes asking how they could help. More importantly, he said those partners are continuing to work with Keeta on the initiatives already underway.
Considering everything we’ve talked about regarding partner risk after an incident like this, that’s about as good of a response as you could hope to hear.
Ty also confirmed something we’ve been talking about for a while. Prior to this incident, the team had been shifting from building to onboarding partners and facilitating volume. They still have a long list of partners to onboard and a lot of volume to facilitate.
This incident unfortunately adds another major item to that list and takes resources away from those core problems, but it doesn’t change what they’re working toward.
As for those affected, Ty reiterated that they will take care of affected participants. Exactly how that happens is still being worked through from the funding, technical, insurance and legal sides, so there isn’t an exact update on that yet.
Ty also acknowledged that simply using the reserve to replace the affected funds isn’t an ideal solution. If the reserve is ultimately used as part of making people whole, he said they will evaluate a buyback as well. I thought that was an important point to address because using the reserve was an obvious concern after the initial update.
Ty made clear that while this was severe, Keeta is in a position where they can recover from it. He said this could have easily been catastrophic, but fortunately they’re not in a position where they can’t recover.
I think that’s ultimately what matters now.
The incident happened. You can’t undo it. What matters is how you respond, whether your partners stick with you, whether affected people are taken care of, and what you learn from it.
So far, I think we’re seeing the response we needed to see.
Ty said Roy has completed the technical incident report and plans to share it after Kee Talks. That’s where we’ll get a much deeper look at exactly what happened and the actions taken.
I’ll be digging into that one when it drops.
@KeetaNetwork $KTA
Root cause identified, patch in test, network halted, report published only after verification.
Crypto is used to teams speculating live in the replies. Feels transparent. It's usually just noise.
Slow and verified beats fast and wrong.
$KTA 💎❄️🩸
Keeta Security Incident Update:
We have identified the root cause of the security incident and are currently testing a patch. Importantly, we have confirmed that the root cause was an isolated issue within the affected component and does not impact Keeta’s anchor systems or any externally connected systems. All KTA on Base remains unaffected.
In parallel, we are evaluating additional precautionary safeguards that can be implemented to further protect the network and prevent a similar incident from occurring in the future.
We are preparing a comprehensive technical report that will detail the exact issue, timeline of events, our response, and the measures being implemented moving forward. We will publish this report as soon as we have completed our investigation and verified all relevant information.
Keeta Mainnet will remain in its current read-only state while this work is completed. We intend to return Mainnet to full operation once the patch has been thoroughly tested and the appropriate additional safeguards are in place.
We are also actively evaluating the best approach to fully reimburse all impacted participants. There are technical and logistical complexities associated with each option, and we want to ensure the process is secure, accurate, and comprehensive.
Our focus remains on ensuring the network is secure, returning to full operation, making all impacted participants whole, and being fully transparent about what occurred and the steps we’re taking moving forward.
We appreciate the community’s continued patience and support as we work through this process.
@KeetaNetwork gets criticised for being quiet. But it's bound by NDAs and moving at the pace of the institutions it's integrating with — that's what regulated infrastructure looks like.
Crypto's used to garage teams posting hourly. Usually ends up as vaporware.
$KTA ����❄️🩸
Keeta Security Incident Update:
We have identified the root cause of the security incident and are currently testing a patch. Importantly, we have confirmed that the root cause was an isolated issue within the affected component and does not impact Keeta’s anchor systems or any externally connected systems. All KTA on Base remains unaffected.
In parallel, we are evaluating additional precautionary safeguards that can be implemented to further protect the network and prevent a similar incident from occurring in the future.
We are preparing a comprehensive technical report that will detail the exact issue, timeline of events, our response, and the measures being implemented moving forward. We will publish this report as soon as we have completed our investigation and verified all relevant information.
Keeta Mainnet will remain in its current read-only state while this work is completed. We intend to return Mainnet to full operation once the patch has been thoroughly tested and the appropriate additional safeguards are in place.
We are also actively evaluating the best approach to fully reimburse all impacted participants. There are technical and logistical complexities associated with each option, and we want to ensure the process is secure, accurate, and comprehensive.
Our focus remains on ensuring the network is secure, returning to full operation, making all impacted participants whole, and being fully transparent about what occurred and the steps we’re taking moving forward.
We appreciate the community’s continued patience and support as we work through this process.
The Keeta survivors just leveled up.
While paper hands panic-sold into the chaos of the mainnet incident, the real ones stayed locked in. Network hit read-only, wallets got tested, price took a brutal hit… and the team responded exactly how a serious project should: fast lockdown, transparent updates, and the Strategic Reserve standing ready to make people whole.
$KTA on Base untouched. Partners still backing. Pipeline of fintechs and institutions still expanding. 10M+ TPS architecture still the real deal.
This isn’t the end.
This is the filter.
The ones who held through the attack aren’t just diamond-handed…
They’re about to watch the most glorious comeback in recent memory.
The weak hands got shaken out.
The strong ones get the upside.
Keeta isn’t broken.
It’s battle-tested.
The comeback is going to be legendary.
And it’s only for those who survived.
$KTA 🚀
You ever have a bad breakup?
It hurts. You feel lost. You’re not really sure what the hell is going on. But then some time later you feel better and eventually you really don’t give that past relationship much thought anymore.
Yeah, that’s kinda what I hope this turns out like.
There’s really no other way to say it. This sucks.
Keeta had some form of security incident where some wallets on Mainnet were drained. Ty has stated that impacted users will be made whole and that the team is exploring all options to do that.
Here’s my thoughts.
Details matter here.
The team has already given us two updates tonight and I’m happy with the communication so far. I hope we hear something again tomorrow, even if they don’t have a full resolution yet. Just keep everyone informed and let us know progress is being made.
One of my biggest concerns immediately was the partners and how they would react.
Ty stated that they have communicated with their partners and those partners expressed their continued support of Keeta. That’s a big deal.
Mainnet was also made read only to prevent any further issues while they figure this out.
There can be a lot of factors that make this situation somewhat better. If the issue is identified and fixed relatively quickly, if some or all of the funds can be recovered, if impacted users are made whole quickly, and if they possibly have insurance coverage for this type of situation, all of those things can affect how easy it is for Keeta to come out of this.
The good news is this happened before any real volume hit the network.
Big institutions aren’t blind to the fact that vulnerabilities happen and get fixed. What matters is how the team responds when they do.
Ethereum and Solana have both had major security issues in their history and almost nobody talks about them anymore. In the grand scheme of things their impact on what those networks eventually became was negligible.
If Keeta clearly communicates what happened, implements a solid fix, takes care of everyone impacted and has a good game plan moving forward, I think they recover from this just fine in time.
Does tonight suck? 100%.
But I still trust the team. I still have full faith in the mission and I think things continue pushing forward.
Let’s see what tomorrow brings.
@KeetaNetwork $KTA