Skip to content
Cyber Threat
CTI Academy Sponsor CTI Academy
Ransomware victim Transportation

Baltimore Tank Lines

Listed by Storm on · organisation based in United States

Disclosed
Oct 19, 2026
Leak-site listing date
Threat group
Storm
118 victims listed
Country
United States
#1 most targeted
Sector
Transportation

ThreatAI analysis

Compiled from this incident record and the threat intelligence profile for Storm. Figures and technique mappings are quoted from the source data, not inferred.

Baltimore Tank Lines was listed on Storm's dark web leak site on 19 October 2026. The transporter moves liquid bulk commodities including fuel, DEF, motor oils, fertilizer and food-grade products for over 75 years.

About Baltimore Tank Lines

Baltimore Tank Lines is a leading transporter of liquid bulk commodities, including fuel, DEF, motor oils, fertilizer, and food-grade products. With over 75 years of experience, the company serves a diverse clientele across local, regional, and national accounts. They are committed to expanding their operations and client base by adding new service locations and growing their manpower and equipment. Baltimore Tank Lines also offers flexible job opportunities and a comprehensive benefits package for transport drivers. The company headquarters is located in 180 8th Avenue NW, Glen Burnie, MD 21061, United States. 11-50 Employees

Source record: ransomware.live

About the Storm group

Storm has listed 84 victims since August 2026.

Incident analysis

Baltimore Tank Lines was listed by Storm ransomware, a group with 118 victims recorded in this database. The listing appeared on the group's leak site on October 19, 2026.

Baltimore Tank Lines is based in United States and operates in the Transportation sector. United States ranks #1 worldwide for ransomware disclosures, with 10,101 victims in this database.

Sector context. Organisations in this sector hold valuable data and operational systems that ransomware groups seek to exploit for financial gain through encryption and data exfiltration.

Storm typically follows a double extortion model: data is exfiltrated from the victim's systems before files are encrypted, so the victim faces two demands at once — pay to restore access, and pay to keep stolen data unpublished. The leak site, where this listing appeared, is the lever for the second demand.

Source. Public leak-site disclosures aggregated via the ransomware.live API. The disclosure date is when the listing was published, which can differ from the date of compromise. This site does not publish or link to stolen data. Last updated .

Frequently asked questions

Was Baltimore Tank Lines attacked by ransomware?

Yes. Baltimore Tank Lines was listed as a victim of the Storm ransomware group on October 19, 2026. The organisation is based in United States and operates in the Transportation sector. The disclosure appeared on the group's dark web leak site.

Which ransomware group attacked Baltimore Tank Lines?

Baltimore Tank Lines was attacked by Storm ransomware. Storm is one of the most active ransomware groups, having claimed 118 victims globally. The group typically employs a double-extortion model: encrypting the victim's files and threatening to publish stolen data.

When did the Baltimore Tank Lines ransomware attack occur?

The ransomware attack on Baltimore Tank Lines was disclosed on October 19, 2026. This date reflects when the victim was published on the threat group's leak site, which may differ from the actual date of initial compromise.

What data was stolen in the Baltimore Tank Lines ransomware attack?

The specific data stolen from Baltimore Tank Lines has not been independently verified by this platform. Ransomware groups typically exfiltrate data before encrypting systems and use the threat of publication to pressure victims. As a Transportation organisation, Baltimore Tank Lines likely held sensitive business data, client information, and operational records.

How can organisations protect against Storm attacks?

To defend against Storm and similar threat actors, organisations should: maintain regular offline backups tested for restoration; implement network segmentation to limit lateral movement; deploy multi-factor authentication on all remote access; use endpoint detection and response (EDR) tools; conduct regular phishing and security awareness training; and monitor threat intelligence feeds for indicators of compromise (IOCs) associated with active groups.