<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:yandex="http://news.yandex.ru" xmlns:media="http://search.yahoo.com/mrss/" xmlns:turbo="http://turbo.yandex.ru" version="2.0">
	<channel>
		<title>Banks</title>
		<link>https://14.stf365.com</link>
		<language>ru</language>
		<item turbo="true">
			<title>Attack on Commercial Bank of Standoff correspondent account</title>
			<link>https://14.stf365.com/wiki/banks/commercial-bank/en/tpost/bcetfer4h1-attack-on-commercial-bank-of-standoff-co</link>
			<amplink>https://14.stf365.com/wiki/banks/commercial-bank/en/tpost/bcetfer4h1-attack-on-commercial-bank-of-standoff-co?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:44:00 +0300</pubDate>
			<category>Commercial Bank of Standoff</category>
			<turbo:content>
<![CDATA[<header><h1>Attack on Commercial Bank of Standoff correspondent account</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 255, 255);">Today, unknown hackers made off with a large sum of money, exploiting a vulnerability in the Commercial Bank of Standoff system. By the most conservative estimates, the attackers managed to withdraw more than 50 million rubles from the bank's correspondent account. "We were able to prevent the theft of some of the funds, but it is already clear that a huge amount has been irretrievably lost. The hackers cashed out the money almost instantly," said representatives of the Commercial Bank of Standoff. The bank has suffered irreparable reputational damage. The management will face legal consequences.</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>Government contract leak in Commercial Bank of Standoff</title>
			<link>https://14.stf365.com/wiki/banks/commercial-bank/en/tpost/mya13vfz41-government-contract-leak-in-commercial-b</link>
			<amplink>https://14.stf365.com/wiki/banks/commercial-bank/en/tpost/mya13vfz41-government-contract-leak-in-commercial-b?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:46:00 +0300</pubDate>
			<category>Commercial Bank of Standoff</category>
			<turbo:content>
<![CDATA[<header><h1>Government contract leak in Commercial Bank of Standoff</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 253, 253);">Unexpected information has appeared online about a contract between State S and the company Horns and Hoofs. Hackers gained access to a payment order sent from a Commercial Bank of Standoff branch and made the data public. Judging by the provided information, the actual payment amount was several times larger than that stated by the officials. Citizens are waiting for explanations and demanding that the details of the state contract be revealed. The Commercial Bank of Standoff stated that an investigation into the incident is already underway.</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>International transfer spoofing at Commercial Bank of Standoff</title>
			<link>https://14.stf365.com/wiki/banks/commercial-bank/en/tpost/9dla3nmad1-international-transfer-spoofing-at-comme</link>
			<amplink>https://14.stf365.com/wiki/banks/commercial-bank/en/tpost/9dla3nmad1-international-transfer-spoofing-at-comme?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:47:00 +0300</pubDate>
			<category>Commercial Bank of Standoff</category>
			<turbo:content>
<![CDATA[<header><h1>International transfer spoofing at Commercial Bank of Standoff</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 255, 255);">Last night, the finance world was rocked by the news of a daring cyberattack on the largest bank in State F — Commercial Bank of Standoff. It all started when a man who introduced himself as John Zegrus walked into one of the bank offices. He was clearly agitated and immediately headed for the customer service desk, demanding to see the Commercial Bank of Standoff management. Barely able to contain himself, Zegrus explained that a few days ago, he had transferred a substantial sum to his family in Taured, but the money still hadn't arrived. The man threatened to write a scathing article about the bank's negligence and incompetence in dealing with customers. Understanding the gravity of the situation, the security experts immediately launched an internal investigation. It turned out that the incident wasn't just a technical glitch, but a full-blown hacker attack. Cybercriminals infiltrated the bank's infrastructure and spoofed the international SWIFT transfer meant for the Zegrus family. As a result, a substantial sum of money ended up in the perpetrators' accounts. The management of Commercial Bank of Standoff assured the public that the culprits would be punished and the stolen funds would be returned to the victims. However, the bank's excellent reputation has now been damaged: the incident has caused panic among its customers, who are now hurrying to withdraw money and close their accounts.</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>Bypass of 2FA for QR code payments in First Partner Bank</title>
			<link>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/h98ecfdur1-bypass-of-2fa-for-qr-code-payments-in-fi</link>
			<amplink>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/h98ecfdur1-bypass-of-2fa-for-qr-code-payments-in-fi?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:48:00 +0300</pubDate>
			<category>First Partner Bank</category>
			<turbo:content>
<![CDATA[<header><h1>Bypass of 2FA for QR code payments in First Partner Bank</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 255, 255);">Convenient payments have led to customers losing a lot of money and the bank losing the trust of its customers. It is reported that one of the known hacker groups has managed to bypass two-factor authentication and exploited this vulnerability to make payments using QR codes. So far, it remains unclear how exactly the attackers managed to do this. The bank issued an official apology to the customers and suspended QR code payments, isolating part of the infrastructure. This announcement comes too late to avoid multiple lawsuits filed by the victims.</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>Disruption of First Partner Bank&#039;s payment system</title>
			<link>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/ix40zxtda1-disruption-of-first-partner-banks-paymen</link>
			<amplink>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/ix40zxtda1-disruption-of-first-partner-banks-paymen?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:49:00 +0300</pubDate>
			<category>First Partner Bank</category>
			<turbo:content>
<![CDATA[<header><h1>Disruption of First Partner Bank's payment system</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 255, 255);">The bank clients are raising the alarm: they are unable to make any payments, and money is disappearing from their accounts with mysterious transactions. As we've learned today, the bank fell victim to a cyberattack. The malicious actors hacked the software used to confirm transactions and reissued the authentication keys. The bank's security systems seem to have failed, and now, some customers are unable to make any transactions while others are losing their money to the hackers.</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>Leak of information on devices used for 2FA by First Partner Bank clients</title>
			<link>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/93etouh941-leak-of-information-on-devices-used-for</link>
			<amplink>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/93etouh941-leak-of-information-on-devices-used-for?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:50:00 +0300</pubDate>
			<category>First Partner Bank</category>
			<turbo:content>
<![CDATA[<header><h1>Leak of information on devices used for 2FA by First Partner Bank clients</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 252, 252);">A major data leak occurred at First Partner Bank. Information about devices used for two-factor authentication (model, operating system, software versions) was put up for sale on the darknet. Although the perpetrators did not get their hands on passwords and access codes, experts note that the leaked information will make it easier for hackers to carry out targeted attacks. Representatives of the bank have already announced the start of an investigation. They also urged their clients to update the software on their devices to protect themselves from hacking.</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>Leak of 2FA keys for First Partner Bank clients</title>
			<link>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/mg3zss9l41-leak-of-2fa-keys-for-first-partner-bank</link>
			<amplink>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/mg3zss9l41-leak-of-2fa-keys-for-first-partner-bank?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:51:00 +0300</pubDate>
			<category>First Partner Bank</category>
			<turbo:content>
<![CDATA[<header><h1>Leak of 2FA keys for First Partner Bank clients</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 255, 255);">An archive containing two-factor authentication keys for a large number of users of the First Partner Bank mobile application was discovered on one of the darknet forums. People are panicking, taking steps to close their accounts to prevent their savings from falling into the hands of criminals. Bank representatives stated that they will investigate the incident and also recommended clients to immediately report any suspicious attempts to log in to their accounts.</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>Defacement of First Partner Bank RBS web service</title>
			<link>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/meksgn7xn1-defacement-of-first-partner-bank-rbs-web</link>
			<amplink>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/meksgn7xn1-defacement-of-first-partner-bank-rbs-web?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:51:00 +0300</pubDate>
			<category>First Partner Bank</category>
			<turbo:content>
<![CDATA[<header><h1>Defacement of First Partner Bank RBS web service</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 255, 255);">Hackers defaced the login page of the First Partner Bank's remote banking system with the text "Your money—our goal." Frightened clients are transferring their savings to accounts in other banks. Representatives of First Partner Bank claim that their users' information and money are safe, and the incident was nothing more than a stunt from competitors. However, the organization is unlikely to be able to regain the trust of its customers...</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>Theft of First Partner Bank customer accounts</title>
			<link>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/3xls5kcxc1-theft-of-first-partner-bank-customer-acc</link>
			<amplink>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/3xls5kcxc1-theft-of-first-partner-bank-customer-acc?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:52:00 +0300</pubDate>
			<category>First Partner Bank</category>
			<turbo:content>
<![CDATA[<header><h1>Theft of First Partner Bank customer accounts</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 255, 255);">An archive with account credentials of First Partner Bank clients is rapidly spreading on hacker forums. Users fear that now scammers will withdraw all the funds from their accounts. For the bank, the incident will result not only in a blow to its reputation but also in legal proceedings.</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>Slowdown of First Partner Bank&#039;s processes due to cryptominer</title>
			<link>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/f0rix6u3j1-slowdown-of-first-partner-banks-processe</link>
			<amplink>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/f0rix6u3j1-slowdown-of-first-partner-banks-processe?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:53:00 +0300</pubDate>
			<category>First Partner Bank</category>
			<turbo:content>
<![CDATA[<header><h1>Slowdown of First Partner Bank's processes due to cryptominer</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 255, 255);">For the longest time, First Partner Bank services functioned just fine with an unnoticed critical vulnerability in QR code authentication, which was recently discovered by hackers, who exploited it to access the bank accounts of clients. The incident came to light only after the clients noticed missing funds: the perpetrators were logging into their accounts and transferring money to their wallets. One in three bank clients had their accounts completely emptied. The victims are in despair and are already preparing to file lawsuits against the bank.</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>Leak of source code of First Partner Bank microservice for QR code payment verification</title>
			<link>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/yzurb066p1-leak-of-source-code-of-first-partner-ban</link>
			<amplink>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/yzurb066p1-leak-of-source-code-of-first-partner-ban?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:54:00 +0300</pubDate>
			<category>First Partner Bank</category>
			<turbo:content>
<![CDATA[<header><h1>Leak of source code of First Partner Bank microservice for QR code payment verification</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 255, 255);">An unknown hacker group managed to breach First Partner Bank's infrastructure and extract the source code of the microservice used for QR code payment confirmation in the marketplace operated by the bank and its partners. Since this leak could be used in future cyberattacks, the bank has launched an investigation and is already taking measures to protect its systems. For now, it's clear that First Partner Bank's reputation is at stake. Clients and partners lost trust in the company and are scrambling to close their accounts en masse. As the investigation is ongoing, the bank had to temporarily shut down the marketplace, which only fueled public outrage.</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>Breach of online shop hosting control panel and information compromise</title>
			<link>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/e02v3xzkp1-breach-of-online-shop-hosting-control-pa</link>
			<amplink>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/e02v3xzkp1-breach-of-online-shop-hosting-control-pa?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:54:00 +0300</pubDate>
			<category>First Partner Bank</category>
			<turbo:content>
<![CDATA[<header><h1>Breach of online shop hosting control panel and information compromise</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 255, 255);">First Partner Bank is no longer the top choice for marketplace operations. The potential customers are reluctant to open trading accounts with the bank, and partner trust has been shattered. The infrastructure provided by the bank for online trading turned out to be very friendly and transparent (just as advertised)— for cybercriminals as well as clients. Hackers managed to break into the hosting control panel, causing damage to both the bank and the online shops. Some of these shops have been made to sell illegal goods, while in others, the hackers announced "Everything Must Go" sales. Meanwhile, the clients of First Partner Bank are facing massive losses. No one knows when the service will be put back online and, more importantly, whether anyone will want to use it again.</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>Accessing First Partner Bank accounts using QR code authentication</title>
			<link>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/sbptltfmn1-accessing-first-partner-bank-accounts-us</link>
			<amplink>https://14.stf365.com/wiki/banks/first-partner-bank/en/tpost/sbptltfmn1-accessing-first-partner-bank-accounts-us?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:55:00 +0300</pubDate>
			<category>First Partner Bank</category>
			<turbo:content>
<![CDATA[<header><h1>Accessing First Partner Bank accounts using QR code authentication</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 255, 255);">The largest bank in State F, First Partner Bank, has found itself at the center of a massive scandal. A few months ago, the customers began to notice that the banking services were becoming unstable, and during peak traffic hours, the services would shut down completely. People demanded an explanation from the bank due to multiple issues with financial transactions. In response to numerous inquiries, the bank representatives insisted that there were no problems and the systems were operating normally. This only added fuel to the fire, and the customers began to leave First Partner Bank, citing a lack of trust. As it turned out, this wasn't for nothing: later, reports have surfaced online, revealing that the disruptions in banking services were the work of hackers, who had implanted a cryptominer into the system. The incident went unnoticed for a long time, which made the situation even worse. As a result, First Partner Bank faces a major trust crisis, which is going to be very difficult to overcome.</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>Account balance increase in Global Digital Bank</title>
			<link>https://14.stf365.com/wiki/banks/global-digital-bank/en/tpost/3oh8u9x3a1-account-balance-increase-in-global-digit</link>
			<amplink>https://14.stf365.com/wiki/banks/global-digital-bank/en/tpost/3oh8u9x3a1-account-balance-increase-in-global-digit?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:56:00 +0300</pubDate>
			<category>Global Digital Bank</category>
			<turbo:content>
<![CDATA[<header><h1>Account balance increase in Global Digital Bank</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 255, 255);">A hacker turned a vulnerability in a banking transaction system into a goldmine. It is known that the perpetrator, using a fraudulent scheme, increased the balance of their account in the European branch of Global Digital Bank. Residents of the capital are eager to know the details, and the bank is strengthening protective measures to avoid similar situations in future.</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>Client passport data leak in Global Digital Bank</title>
			<link>https://14.stf365.com/wiki/banks/global-digital-bank/en/tpost/ggegtd1b41-client-passport-data-leak-in-global-digi</link>
			<amplink>https://14.stf365.com/wiki/banks/global-digital-bank/en/tpost/ggegtd1b41-client-passport-data-leak-in-global-digi?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:57:00 +0300</pubDate>
			<category>Global Digital Bank</category>
			<turbo:content>
<![CDATA[<header><h1>Client passport data leak in Global Digital Bank</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 255, 255);">An extremely valuable item has been put up for sale on the darknet: an archive with passport data of customers of the European branch of Global Digital Bank. People are panicking, worried that criminals have already taken out loans in their names. Meanwhile, the bank is preparing to face lawsuits.</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>Denial of service for Global Digital Bank infrastructure</title>
			<link>https://14.stf365.com/wiki/banks/global-digital-bank/en/tpost/vxnsuo6hd1-denial-of-service-for-global-digital-ban</link>
			<amplink>https://14.stf365.com/wiki/banks/global-digital-bank/en/tpost/vxnsuo6hd1-denial-of-service-for-global-digital-ban?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:58:00 +0300</pubDate>
			<category>Global Digital Bank</category>
			<turbo:content>
<![CDATA[<header><h1>Denial of service for Global Digital Bank infrastructure</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 255, 255);">Users have encountered strange behavior in Global Digital Bank services. After a day of silence, bank representatives stated that its infrastructure, running in a Kubernetes cluster, was attacked by hackers. The intruders tried to disrupt the bank's systems, and the security team valiantly resisted them. Hence the strange behavior of some services and the unavailability of others.</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>Denial of service for Global Digital Bank borrowers&#039; database</title>
			<link>https://14.stf365.com/wiki/banks/global-digital-bank/en/tpost/aj2jhbzi91-denial-of-service-for-global-digital-ban</link>
			<amplink>https://14.stf365.com/wiki/banks/global-digital-bank/en/tpost/aj2jhbzi91-denial-of-service-for-global-digital-ban?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:58:00 +0300</pubDate>
			<category>Global Digital Bank</category>
			<turbo:content>
<![CDATA[<header><h1>Denial of service for Global Digital Bank borrowers' database</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 255, 255);">Thanks to an anonymous source, it has become known that hackers attacked part of the infrastructure of the European branch of Global Digital Bank, running in a Kubernetes cluster. It is known that the criminal managed to go beyond the container and gain access to the node's operating system. As a result, most of Global Digital Bank's services were compromised. The security service is addressing the aftermath of the incident. It is still unknown how much confidential information was stolen.</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>Internal Global Digital Bank document leak</title>
			<link>https://14.stf365.com/wiki/banks/global-digital-bank/en/tpost/xc7ekp63n1-internal-global-digital-bank-document-le</link>
			<amplink>https://14.stf365.com/wiki/banks/global-digital-bank/en/tpost/xc7ekp63n1-internal-global-digital-bank-document-le?amp=true</amplink>
			<pubDate>Sun, 24 Nov 2024 23:59:00 +0300</pubDate>
			<category>Global Digital Bank</category>
			<turbo:content>
<![CDATA[<header><h1>Internal Global Digital Bank document leak</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 255, 255);">Hackers successfully attacked Global Digital Bank and, as was later discovered, stole documents about its development plans. The leaked data was discovered online, and the public has been discussing the incident for several days now. Financial experts and investors are more interested in the plans themselves. The organization has acknowledged the leak and announced the start of an investigation. Journalists speculate that not only the bank's reputation will be damaged, but also its competitive advantage.</span></div>]]>
			</turbo:content>
		</item>
		<item turbo="true">
			<title>Hijacking of Global Digital Bank mobile app account</title>
			<link>https://14.stf365.com/wiki/banks/global-digital-bank/en/tpost/5hus5i7nd1-hijacking-of-global-digital-bank-mobile</link>
			<amplink>https://14.stf365.com/wiki/banks/global-digital-bank/en/tpost/5hus5i7nd1-hijacking-of-global-digital-bank-mobile?amp=true</amplink>
			<pubDate>Mon, 25 Nov 2024 00:00:00 +0300</pubDate>
			<category>Global Digital Bank</category>
			<turbo:content>
<![CDATA[<header><h1>Hijacking of Global Digital Bank mobile app account</h1></header><div class="t-redactor__text"><strong style="color: rgb(81, 153, 255);">Event description</strong></div><div class="t-redactor__text"><span style="color: rgb(255, 255, 255);">The use of mobile banking has resulted in financial losses for clients of the European branch of Global Digital Bank and reputational damage for the organization itself. Today it became known that hackers have breached the accounts of several hundred users of the bank's mobile application and withdrawn money from their accounts—big figures are estimated. "I can't believe this happened to me. I thought my savings were definitely safe in the bank. Give me back my money!"—one of the victims raged in his blog. The bank has already acknowledged the problem and promised to fix vulnerabilities in the application, but this won't hold off the lawsuits.</span></div>]]>
			</turbo:content>
		</item>
		</channel>
</rss>