$186 million hacking case finally comes to an end: how regulators will penalize negligent crypto bridges

robot
Abstract generation in progress

【Crypto World】The 2022 Nomad Bridge theft incident has finally received an official regulatory response. The U.S. Federal Trade Commission has reached a settlement with the operators—requiring the full return of nearly $186 million in funds to the affected users.

Details of this settlement are noteworthy: firstly, prohibiting the company from further exaggerating its security capabilities, which is ironic since they clearly cannot do so; secondly, requiring the establishment of a formal security system, with third-party assessments every two years, effectively placing a “tight leash” of regulation.

What’s even more heartbreaking is the root cause of the incident—hidden vulnerabilities in code updates, security testing was essentially useless, and emergency response was painfully slow. The FTC specifically pointed out a detail: at the time of the incident, an engineer was on a plane, making it impossible to stop the loss immediately. What does this imply? It’s not just technical negligence but also chaos in risk management.

For the entire crypto industry, this case serves as a warning: security cannot just be lip service; real investment is needed. Projects claiming “military-grade defense” but cutting corners will eventually attract regulatory scrutiny.

View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • 5
  • Repost
  • Share
Comment
0/400
SnapshotBotvip
· 12-19 18:09
Haha, hilarious. The engineer on the plane is a perfect example of the daily struggles in Web3. Full refund of 186 million? Nice talk. Let’s see if they can actually pay it back in full. Nomad getting sanctioned this time was well-deserved. Their security testing was a joke, and they still dared to boast about their professionalism. Laugh out loud. The regulatory crackdown is coming. From now on, these projects will have to do honest audits. What’s the use of an apology? Users’ losses can’t be recovered. I just want to know if that engineer is still on the plane.
View OriginalReply0
NewPumpamentalsvip
· 12-16 23:30
Well, the Nomad incident finally has a result, but can the 186 million be really returned... Doubtful. The engineer laughing at the detail on the plane—this is what you call a "professional team"? Prohibit exaggerated claims about safety? The implication is that they were bragging before. Such penalties are like scratching an itch for Web3. Auditing every two years still feels like treating the symptoms rather than the root cause.
View OriginalReply0
WalletWhisperervip
· 12-16 23:29
$186 million can really be fully refunded? Why do I feel like this isn't that simple? Engineers on the plane, haha, what kind of reckless risk management is that? Prohibit exaggerated claims about safety? You're only saying this now? Why didn't you do it earlier? Once every two years for review, indeed a tight control, but does that prevent the next issue? Has the refund been credited to everyone? Or do we have to wait in line for notifications again? Honestly, it's still a human problem; no matter how advanced the technology, chaotic management is useless. Nomad's issue is finally resolved, but when will the subsequent bridges truly be safe?
View OriginalReply0
shadowy_supercodervip
· 12-16 23:29
Hey, this is outrageous. Engineers on a plane? How unprofessional is that? 186 million just gone like that. Refund? I just want to know if it's really possible to get everything back. I've seen this trick too many times. Prohibit hype + biennial assessments, that's what should be done. Why was no one managing this before? Code audits are useless; this is the current state of most bridges. I stopped trusting these long ago. Assessment every two years? Feels like just treating the symptoms, not the root cause. How can it be fixed if it's fundamentally rotten? Actually returning 186 million would be truly conscientious. I'll wait to see the financial report first. This incident exposes the industry's risk management as truly difficult to describe. Engineers flying... I really can't smile about this. Is this a safety deployment? The most ironic thing is banning them from bragging, but they have nothing to brag about anyway. Thinking of those projects that claimed to be very safe, now it’s all clear—there's a role model for everyone.
View OriginalReply0
GmGmNoGnvip
· 12-16 23:23
Haha, this engineer on the plane is truly impressive. This is the real picture of Web3 security. $186 million was just forcefully spit out like that. It seems that regulators are really getting serious. A third-party audit every two years... feels like we're learning traditional finance. Our circle still has a lot to learn. Code audits are practically useless. I just want to laugh. Still dare to say you're secure? Losing money is easy, but regaining trust is the hard part.
View OriginalReply0
  • Pin
Trade Crypto Anywhere Anytime
qrCode
Scan to download Gate App
Community
  • 简体中文
  • English
  • Tiếng Việt
  • 繁體中文
  • Español
  • Русский
  • Français (Afrique)
  • Português (Portugal)
  • Bahasa Indonesia
  • 日本語
  • بالعربية
  • Українська
  • Português (Brasil)