Skip to main content
Darkfield

Ransomware victim disclosure

← All victims

maritimebank.com

Claimed by Lv · listed 3 years ago

31m
Age
since listed · data leaked

Status timeline

  1. ListedDec 20, 2023
  2. Data leakeddate unknown

At a glance

Group
Lv
Status
Data leaked
Country
Russia
Sector
Financial Services
Listed on leak site
Dec 20, 2023

About the victim

AI dossier — public-source company profile

Морской Банк (АО) is a Russian joint-stock bank founded in 1989 by state maritime and river transport entities. It provides comprehensive financial services to businesses and individuals, including account management, foreign exchange, international payments, deposits, and securities market services across multiple Russian cities.

Industry
Banking & Financial Services
Address
Moscow, Russia (headquarters); multiple branches in Russia
Founded
1989

Attack summary

Severity: critical — Exfiltration of 120 TB of data from a regulated financial institution involving client personal and financial records constitutes regulated sensitive data exposure at massive scale, affecting a systemically important bank operating across Russia.

The threat actor claims to have exfiltrated approximately 120 TB of client data from Морской Банк, alleging inadequate information security budgets left customer data unprotected. The group demands $1,000,000 in ransom for non-disclosure and threatens to publish all exfiltrated data.

critical

Data the group says was taken

AI dossier — extracted from the leak post
  • Client financial records
  • Account information
  • Personal data
  • Business transaction records

What the group claims

МОРСКОЙ БАНК (АО) работает на рынке банковского обслуживания уже 34 года и является одним из старейших финансовых институтов России.Банк был основан 29 марта 1989 года государственными учреждениями и предприятиями морского и речного транспорта в целях комплексногофинансового обслуживания субъектов отрасли с учетом особенностей их хозяйственной деятельности.Согласно бюджета на информационную безопасность тратится крайне мало средств,в следствии чего данные клиентов не защищены.Все 120 тб данных будут опубликованы.Стоимость не разглашения на сегодняшний день составляет 1000000$.

Sources

Source

Indexed 3 years ago

This page surfaces a public ransomware disclosure indexed by Darkfield. Original posts come from the operator's own leak site; we cross-check against ransomware.live, RansomLook and RansomWatch where applicable. Share this URL freely.

Is this your supplier? Your competitor? You?

Pro plans monitor your domain, corporate emails, and crypto wallets across every new ransomware leak-site post, breach dump and Telegram callout — alerts within 5 minutes.

Disclosure context

About Lv

Lv is a financially motivated ransomware group that emerged in November 2021, operating with relatively low visibility compared to major ransomware families but maintaining consistent activity across multiple regions and sectors. The group's country of origin and specific affiliations remain undocumented in public threat intelligence reporting, though their targeting patterns suggest they operate independently rather than as part of a larger ransomware-as-a-service ecosystem. Limited public documentation exists regarding Lv's specific attack methodology, initial access vectors, or technical capabilities, though their successful compromise of 115 documented victims across diverse sectors indicates they employ conventional ransomware deployment techniques. The group has demonstrated a preference for targeting critical infrastructure and business services, with notable geographic focus on Russia, France, Malaysia, the United States, and the Netherlands, spanning sectors including energy, telecommunications, business services, media, and non-profit organizations. Current intelligence suggests Lv remains active as of recent reporting, though the group maintains a lower profile than prominent ransomware families and has not been subject to major law enforcement disruption operations. The group has been linked to 115 public disclosures across our corpus. First observed on a leak site on November 22, 2021; most recent post March 13, 2024. The operation is currently inactive.

Timeline of this disclosure

  • December 20, 2023maritimebank.com listed by Lvon the group's public leak site

Other recent disclosures by Lv

Lv has been linked to 115 public victims on Darkfield. A sample of the most recent:

See the full Lv dossier →

Sector and geography

This disclosure adds to ransomware activity in the Financial Services sector, which has 1,184 disclosures indexed across all operators we track. Geographically, maritimebank.com is reported in Russia, a country with 63 ransomware disclosures in our corpus.

If your organisation is affected

A listing by Lv means maritimebank.com appeared on a ransomware extortion site and data attributed to it has been published. If this is your organisation, or a supplier you depend on, the priority is to confirm the intrusion and contain it before the window to act closes.

  • Engage your incident-response team and preserve forensic evidence before remediating — do not wipe affected systems first.
  • Force a password reset and revoke active sessions for exposed accounts; rotate any credentials, API keys or certificates that may have been in the stolen data.
  • Assess regulatory notification duties (GDPR, NIS2, sector regulators) — many carry a 72-hour reporting clock from awareness.
  • Monitor for the data appearing on Lv's leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.

How we know this. Darkfield monitors public ransomware leak sites continuously, archiving every new disclosure and the data later released against the victim. Each entry on this page is sourced from the operator's own publication and cross-checked against complementary OSINT feeds (RansomLook, ransomware.live, RansomWatch). We do not collect or host stolen data — only the metadata, timestamps and screenshots needed to make the public disclosure searchable and accountable. Records here are corrected when the original post is edited, retracted, or merged with another disclosure.