A month that reinforces an uncomfortable lesson for the digital market
The attacks on the crypto ecosystem, which totaled more than US$ 766 million in September, stand out not only for their size. They clearly show how the combination of digital assets, complex infrastructure, and security gaps still creates room for significant losses.
According to data released by security firms, the month saw dozens of incidents, with the Bitget attack, at US$ 388 million, and the incident at Liquid Network, at US$ 320 million, as the main highlights. A significant portion of the funds from Liquid Network was later returned, but the episode remains a clear sign of systemic vulnerability.
For companies that work with technology, payments, integrations, and sensitive data, the lesson should not be limited to the crypto world. The core issue is different: when digital architecture grows faster than governance, risk stops being theoretical and starts affecting operations, reputation, and trust.
What the numbers show beyond the financial impact
PeckShield counted 55 incidents and US$ 766.5 million in stolen funds. CertiK, in turn, recorded 97 incidents and estimated losses of US$ 768.4 million. The difference between the figures does not change the essence of the problem: the ecosystem remains exposed to frequent attacks with high and recurring impact.
There is also a figure that deepens the concern. CertiK reported 656 security incidents in 2026 and a total loss of US$ 2.68 billion over the same period. That indicates the challenge is not isolated. It is structural.
Even cases with partial recovery, such as Liquid Network, do not eliminate the operational impact of the attack. In many scenarios, the damage has already been done: systems are interrupted, teams shift into crisis mode, customers lose confidence, and the company must respond under pressure.
What traditional companies can learn from this scenario
Although the headlines are about crypto, the lesson applies to any digital business. The more a company depends on systems, integrations, and automated workflows, the more it needs to treat security as part of its strategy rather than the final stage of a project.
In practice, that means reviewing areas such as:
- access control and authentication in critical systems;
- continuous monitoring of integrations and APIs;
- management of vendors and technology dependencies;
- incident response plans and internal communication;
- frequent vulnerability testing and permission reviews.
Companies that operate e-commerce sites, portals, CRMs, automations, and cloud environments need to think about resilience. It is not enough to work well day to day. They must be prepared for failures, intrusion attempts, and unexpected outages.
Digital security is also commercial trust
In B2B markets, trust is an asset. When a system fails, the perception of risk rises quickly. When there is a breach, intrusion, or loss of control, the discussion is no longer just technical and begins to involve brand, contracts, and business continuity.
That is why digital projects need to be built with security in mind from the architecture stage. This applies to websites, internal systems, third-party integrations, and automated workflows. In many cases, the difference between a robust environment and a fragile one comes down to simple decisions about planning, documentation, and governance.
At SuaEmpresa.Net, this perspective is part of the work in digital solution development. In projects that require stability, integration, and data protection, security must go hand in hand with performance and user experience. That is where a well-structured website and web systems development makes a real difference.
Cases like the order portal and Omie integration show how integrations require technical discipline and attention to control points. And to go deeper into data protection, it is also worth reviewing the article on how to prepare your company’s website to collect data securely.
The final message for leaders and technology teams
The digital market is more exposed than many managers realize. And the answer is not just to react to incidents, but to build environments that are more predictable, auditable, and resilient.
If your company’s operations depend on technology, the right question is not whether there will be risk. It is whether the current structure is ready to handle it.
Source: Cointelegraph