DisclosureLens
GLOBALMalwareTransportation & LogisticsTransportationRansomwareCactusRansom DemandedActor NamedData Leak ThreatenedData PublishedHigh

VSS Transportation Group

bd_a2f5598667507397 · schema v1 · pii pii-v1

Severity

High

Discovered

—

Filed

Jan 17, 2025

To disclose

—

Affected

Not disclosed

Confidence

50%
Full breach record for VSS Transportation Group →2 incidents on file

Threat-actor claim — not a regulatory filing

This row is a claim by the ransomware group Cactus on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.

Group activity: Transportation/LogisticsDiscovered: 2025-01-30
View aggregator listing on ransomware.live

Source: Ransomware.live

Post text · scraped from the leak site

<p>Transportation.<br><br>“VSS Transportation Group provides quality service and complete customer satisfaction. We are constantly working on improving our communication and capabilities to better serve you. Please feel free to leave any comments, questions, or concerns you may have regarding our services and your overall experience with VSS Transportation Group.”<br><br>Website: <a href="https://www.vsstransportationgroup.com/">https://www.vsstransportationgroup.com/<\/a><br><br>Revenue : $54.5M<br><br>Address: 1325 W Belt Line Rd, Carrollton, Texas, 75006, United States<br><br>Phone Number: ([REDACTED-PHONE]<br><br><mark class="marker-yellow"><strong>Download link #1:<\/strong><\/mark> &nbsp;<a href="https://6wuivqgrv2g7brcwhjw5co3vligiqowpumzkcyebku7i2busrvlxnzid.onion/VSSCARRIERS/PROOF/">https://6wuivqgrv2g7brcwhjw5co3vligiqowpumzkcyebku7i2busrvlxnzid.onion/VSSCARRIERS/PROOF/<\/a><br><br><mark class="marker-yellow"><strong>Mirror:<\/strong><\/mark> <a href="https://cactus5dqnqkppa5ayckiyk6dttpqwczdqphv5mxh4dkk5ct544q5aad.onion/VSSCARRIERS/PROOF/">https://cactus5dqnqkppa5ayckiyk6dttpqwczdqphv5mxh4dkk5ct544q5aad.onion/VSSCARRIERS/PROOF/<\/a><br><br><mark class="marker-yellow"><strong>DATA DESCRIPTIONS:<\/strong><\/mark> Personal Identifiable information, corporate confidential data, employees personal files\docs, financial data\payroll, corporate correspondence, database backups etc.<\/p><p><img src="/uploads/BELL_DAVID_DL_2030_updated_address_front_a8ea8bd20f.png" alt="BELL DAVID DL 2030.updated address front.png"><img src="/uploads/BARRETT_ROBERT_DL_2032_FRONT_98d98c38ff.png" alt="BARRETT ROBERT DL 2032 FRONT.png"><img src="/uploads/ALLEMAN_RONALD_DL_2027_ea8a2e6d06.png" alt="ALLEMAN, RONALD DL 2027.png"><img src="/uploads/DRIVER_LICENSE_48f3e25b9d.png" alt="DRIVER LICENSE.png"><img src="/uploads/BAIRD_JOHN_DL_2025_c6e4b44eea.png" alt="BAIRD JOHN DL 2025.png"><\/p>

Incident timeline — mostly unverified

? — ?

Breach window unknown

Jan 17, 2025

Claim posted

—

No filing yet · watching

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

Claim → filing

—

Compliance clock

Not assessable

Tracked as a single-filing incident — the only disclosure on record for this event so far.Unverified claimView incident

Evidence ladder

Leak-site claimThis record

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.

Source ceiling

  • actor name
  • victim claim
  • ransom/leak status
  • discovery date
  • materiality
  • notification
  • affected count
  • confirmed data types
  • compliance clock

The ✕ fields stay blank until a regulatory filing or victim disclosure lands.

About this groupFirst seen 2023-07-03

cactus

According to ransomware.live, The CACTUS ransomware is said to have emerged around March 2023. The group became known for exploiting vulnerabilities to gain initial access and maintain a presence within the organization's infrastructure. There is little known information about the ransomware group, except that it emerged on the mentioned date and, following encryption, a text file named 'cAcTuS.readme.txt' would be created. Additionally, encrypted files were altered to the '.cts1' extension, and data exfiltration and victim extortion were conducted through the use of the service known as Tox. Source: https://github.com/crocodyli/ThreatActors-TTPs

249 tracked hereFull profile →