Listen to this Post
A Troubling Cybersecurity Claim Emerges From Cuba
A new dark web breach claim is raising questions about the cybersecurity of one of Cuba’s major state-owned hotel operators. A threat actor is reportedly offering a massive collection of data allegedly stolen from the Gran Caribe Hotel Group, claiming the haul contains approximately 110 GB of uncompressed information spread across 34 Microsoft SQL Server databases.
The alleged incident is particularly concerning because the databases reportedly extend far beyond ordinary hotel booking information. According to the threat actor’s marketplace listing, the stolen material may include reservations, guest records, billing information, employee data, accounting records, inventory systems, loyalty-program information, Wi-Fi accounts and security-related credentials.
However, there is an important distinction between a dark web claim and a confirmed breach. The information currently comes from a threat actor advertising allegedly stolen data. The intrusion, the authenticity of the samples, the claimed 110 GB volume and the August 10, 2026 breach date have not been independently verified.
The Alleged Gran Caribe Breach
The threat actor claims that Gran Caribe Hotel Group was compromised on August 10, 2026, just two days before the Dark Web Intelligence report appeared.
The alleged stolen dataset is said to contain 34 Microsoft SQL Server databases, collectively totaling roughly 110 GB in uncompressed form. If the claim is genuine, the scale would make this considerably more serious than a limited theft involving a handful of customer records.
The seller reportedly says the databases were extracted directly from live production servers rather than being an old archive or previously circulated dataset. The actor is allegedly offering Microsoft SQL Server .BAK backup files and samples to potential buyers.
A $10,000 Price Tag for the Alleged Data
The alleged database collection is reportedly being offered for $10,000 USD, although the seller is said to be willing to negotiate.
For a dataset containing sensitive hotel, employee and operational information, that price is relatively modest compared with the potential intelligence value of the information described in the listing.
The price could also be part of the seller’s strategy. Threat actors sometimes use relatively low prices to attract multiple buyers quickly, while others deliberately advertise stolen information at a premium when they believe the data has strategic or commercial value.
Importantly, the asking price itself does not demonstrate that the data is authentic.
Eight Hotel Properties Reportedly Affected
According to the threat actor, the alleged dump covers information associated with eight Gran Caribe hotel properties.
That claim is significant because compromising multiple properties through shared infrastructure could indicate that the attacker allegedly obtained access to centralized systems rather than breaching individual hotels separately.
A centralized compromise could potentially give an attacker access to common reservation, accounting, human resources, loyalty or administrative systems serving multiple locations.
Hotel Reservation and Guest Information at Risk
One of the most sensitive categories reportedly included in the alleged database is guest information.
The threat actor claims the stolen records contain reservations, check-ins, room assignments, billing information and other client details.
If authentic, such information could expose much more than names and booking dates. Hotel databases can contain travel patterns, contact information, payment-related records, identification details and information about when specific individuals are expected to be present at particular locations.
That makes hotel systems particularly attractive targets for cybercriminals because their databases can provide both financial and personal intelligence.
Employee Records Allegedly Included
The alleged breach reportedly extends into human resources systems as well.
The seller claims to possess records for approximately 873 employees, allegedly including names, positions, departments, salaries and telephone numbers.
Employee databases can be extremely valuable for follow-on attacks. Even when passwords are not exposed, information about job titles and organizational structures can help attackers construct convincing phishing campaigns or impersonate executives and internal departments.
The combination of employee names, roles and contact information can also make social-engineering attacks significantly more credible.
Financial and Accounting Information
The alleged database reportedly contains accounting and financial information, including financial statements and other business records.
Financial systems are among the most sensitive components of an organization’s IT environment because they can reveal revenue information, payment relationships, suppliers, expenses and internal business operations.
If authentic, the data could therefore represent a risk not only to individual customers and employees but also to the hotel group’s broader commercial operations.
Supplier and Operational Data
The threat actor also claims to have obtained supplier information and operational logs.
Supplier databases can reveal relationships between organizations, contact details, purchasing activity and business dependencies. Operational logs can sometimes provide an attacker with insight into how an organization functions behind the scenes.
This type of information may not attract as much attention as guest records, but it can become highly useful when combined with other stolen datasets.
Loyalty Program Information Allegedly Exposed
The alleged breach reportedly includes loyalty-member data.
Hotel loyalty programs often contain information accumulated over years, potentially including customer identities, contact information, membership identifiers, travel activity and account history.
A compromised loyalty database can therefore become a valuable source of personal information and may also create opportunities for account takeover attempts or highly targeted phishing.
Wi-Fi Accounts and Password Hashes
One of the more technically concerning claims involves hotel Wi-Fi accounts.
The seller reportedly claims that the stolen information contains Wi-Fi credentials protected using MD5 password hashes.
MD5 is a cryptographic hashing algorithm that has long been considered unsuitable for protecting passwords because it is fast and vulnerable to modern password-cracking techniques.
A password hash is not the same thing as a plaintext password, but weak password hashing can make credential recovery significantly easier when passwords are weak or reused elsewhere.
Cuban Identification Numbers Allegedly Included
The threat actor further claims that the dataset contains Cuban DNI numbers.
Government-issued identification numbers are particularly sensitive because they can potentially be used to connect multiple records to the same individual.
If genuine, exposure of such identifiers could increase the long-term privacy impact of the alleged incident because identification numbers cannot simply be changed like passwords.
Security-System Credentials Raise Additional Questions
Perhaps one of the most serious claims involves security-system credentials and hashes.
Hotel security systems can include access-control infrastructure, surveillance-related systems and other technologies used to protect guests and employees.
A database breach does not automatically mean an attacker gained operational control of those systems. Nevertheless, if valid security credentials were actually exposed, organizations would need to treat them as potentially compromised and rotate or invalidate them immediately.
The Difference Between a Claim and a Confirmed Breach
The most important fact surrounding this story is also the easiest to overlook: the breach has not been independently confirmed based on the information currently available.
The threat actor is making the allegations while attempting to sell the purported data. That creates an obvious incentive to exaggerate the size, sensitivity or authenticity of the material.
Dark web listings can contain genuine stolen information, recycled datasets, fabricated samples, misleading claims or combinations of old and new material.
For that reason, the reported 110 GB figure should currently be treated as an allegation rather than an established fact.
Why the 110 GB Figure Matters
If the claimed volume is accurate, 110 GB across 34 databases represents a substantial collection of information.
The size alone, however, should not be interpreted as proof of severity. Database dumps can contain duplicate records, historical information, logs, backups and large technical tables that do not necessarily contain sensitive personal data.
The more important question is what portion of those 110 GB contains authentic, current and sensitive information.
Why Live Production Servers Would Be Significant
The seller allegedly claims the databases were extracted from live production servers.
If independently verified, that detail would be particularly important because it could suggest direct access to active business systems rather than an abandoned backup or historical database.
It could also raise questions about how long the attacker allegedly maintained access, whether security controls were bypassed and whether credentials or other persistence mechanisms were left behind.
Again, this remains an unverified claim.
A Potential Supply-Chain and Infrastructure Concern
The alleged compromise could have implications beyond individual hotel properties if Gran Caribe relies on centralized infrastructure.
Modern hotel groups frequently connect reservations, property-management systems, accounting, loyalty services, human resources and other operational platforms.
A single compromised administrative environment can therefore create a path into multiple business functions.
That makes segmentation particularly important. A reservation system should not automatically provide a route to HR databases, financial systems or security infrastructure.
The Human Impact Could Be Larger Than the Database Size
Cybersecurity incidents are often measured in gigabytes and records, but the real impact is experienced by people.
A hotel guest whose travel history is exposed may face privacy concerns. An employee whose salary and phone number are leaked may become a target for fraud. A loyalty-program member may face phishing or account takeover attempts.
If identification numbers are genuinely present, the consequences can potentially extend much further.
Why Hotel Groups Are Attractive Cyber Targets
Hotels possess a unique combination of valuable information.
They know who is traveling, where guests are staying, when they arrive, how long they remain, how they pay and sometimes which loyalty programs they use.
That information has intelligence value far beyond the hospitality industry itself.
A hotel database can potentially reveal patterns of movement, business travel, organizational relationships and personal contact information.
Dark Web Markets Turn Breaches Into Commodities
The alleged Gran Caribe listing also illustrates how cybercrime has become increasingly commercialized.
A successful intrusion can be divided into products: databases, credentials, access tokens, backups, employee information and customer records.
Threat actors do not necessarily need to personally exploit every piece of stolen data. They can sell it to other criminals who specialize in fraud, identity theft, phishing or further network intrusion.
The $10,000 asking price therefore represents more than a number. It illustrates how stolen organizational data can become a tradable commodity.
Deep Analysis: What This Alleged Breach Could Mean
Centralized Databases Create Concentrated Risk
The reported use of 34 databases suggests a potentially complex environment.
If several properties rely on shared databases or centralized management infrastructure, one successful intrusion could theoretically affect multiple locations simultaneously.
That is precisely why segmentation and least-privilege access are so important in hospitality environments.
Database Backups Are High-Value Targets
The alleged availability of .BAK files deserves particular attention.
SQL Server backup files can contain extensive historical database information. Depending on how they are protected, stolen backups may allow attackers to reconstruct large portions of an organization’s data environment.
Backups therefore need security controls comparable to production systems.
MD5 Hashes Would Represent a Security Weakness
If the reported Wi-Fi credentials really use MD5 hashes for password protection, that would be an important security finding.
Modern password storage should use deliberately slow, password-specific algorithms such as Argon2id, bcrypt or scrypt, combined with appropriate salting and security controls.
The alleged presence of MD5 hashes does not automatically mean passwords can be recovered, but it would substantially increase the risk for weak or reused passwords.
Employee Information Can Enable Targeted Fraud
The alleged 873 employee records could be valuable to criminals even without passwords.
An attacker who knows an employee’s name, position, department and phone number can construct a highly convincing impersonation attempt.
For example, criminals could impersonate an IT administrator, finance employee or senior manager and attempt to convince another employee to disclose credentials or approve a transaction.
Hotel Guests Could Become Phishing Targets
Guest information can similarly enable personalized attacks.
Instead of sending generic messages, criminals could potentially reference a real hotel booking, arrival date or property.
A fraudulent message that appears to know where someone is staying can be considerably more convincing than ordinary spam.
Loyalty Data Can Have Long-Term Value
Loyalty information may remain useful even after a breach has been publicly disclosed.
Attackers could potentially use membership identifiers and customer information to target account recovery processes or impersonate customers.
Organizations should therefore treat loyalty databases as security-sensitive assets rather than simple marketing databases.
Security Credentials Require Immediate Attention if Confirmed
The reported exposure of security-system credentials would warrant urgent investigation.
If authentic, organizations should assume that exposed credentials may be compromised and rotate them.
Where possible, access should also be restricted by network location, device identity, multifactor authentication and narrowly defined permissions.
Data Volume Should Not Become a Distraction
The headline number of 110 GB is attention-grabbing, but defenders should focus on data sensitivity rather than volume.
A 1 GB database containing authentication secrets can be more dangerous than a 100 GB database filled mostly with logs.
The real questions are whether the data is authentic, current, unique, sensitive and actionable.
Verification Is the Critical Next Step
Independent verification should focus on samples, database structures, timestamps, record consistency and whether the information corresponds to current Gran Caribe operations.
Security researchers should also look for evidence that the alleged data has been recycled from previous incidents.
This is particularly important in dark web intelligence, where old datasets are sometimes repackaged as new breaches.
The Claimed August 10 Date Requires Scrutiny
The alleged breach date is August 10, 2026.
Because the marketplace listing surfaced only shortly afterward, investigators should determine whether the claimed timeline is consistent with available technical evidence.
Timestamps inside databases, backup metadata, logs and file creation information could potentially help establish whether the dataset is recent.
The Listing Could Be Used as an Initial Warning
Even if the claim ultimately proves exaggerated, organizations should not dismiss it automatically.
A credible threat intelligence report can serve as an early warning.
Organizations can use such claims to check whether exposed credentials exist, review authentication logs, examine unusual database activity and confirm that critical systems are properly segmented.
Hotel Cybersecurity Requires Defense in Depth
A hotel group cannot rely on a single firewall or endpoint security product.
Its environment may include reservation systems, point-of-sale infrastructure, Wi-Fi, guest applications, employee systems, accounting platforms, physical security systems and third-party integrations.
Each layer should be isolated as much as practical.
Privileged Access Is a Critical Control
Administrative accounts should have the minimum permissions required to perform their jobs.
If one compromised account can access dozens of databases, the consequences of credential theft become much greater.
Privileged access management, multifactor authentication and detailed auditing can reduce this risk.
Database Access Should Be Closely Monitored
Unexpected bulk queries, unusual backup operations and large data exports should trigger investigation.
An attacker attempting to extract 110 GB of information would potentially generate unusual activity somewhere in the environment, although the exact evidence would depend on the architecture and logging capabilities.
Database activity monitoring can therefore provide an important detection layer.
Backups Need Strong Protection
Organizations should assume that attackers will target backups during serious intrusions.
Backups should be encrypted, access-controlled and separated from ordinary production credentials.
Offline or immutable backup strategies can also reduce the damage caused by ransomware and destructive attacks.
The Human Element Remains Critical
Technology alone cannot prevent every breach.
Employees need practical training on phishing, impersonation and credential protection.
This becomes particularly important after employee information is leaked because attackers can use legitimate organizational details to make fraudulent messages appear authentic.
Incident Response Should Begin Before Confirmation
Organizations do not always need to wait for absolute certainty before taking low-risk defensive actions.
If credible evidence suggests credentials may have been exposed, rotating them can be sensible.
If suspicious database access is detected, investigating it immediately is preferable to waiting for a marketplace listing to become indisputable.
Dark Web Monitoring Can Provide Early Indicators
Continuous monitoring of underground marketplaces can help organizations discover alleged breaches earlier.
The information may not always be accurate, but it can provide leads that security teams can investigate.
The most valuable role of dark web intelligence is therefore not simply announcing breaches. It is helping defenders identify signals that deserve technical verification.
The Incident Highlights Data Minimization
The more information an organization stores, the more information attackers can potentially steal.
Businesses should periodically review whether they still need historical personal information.
Data that has no operational or legal purpose should not remain indefinitely accessible in production systems.
Encryption Can Reduce Exposure
Encryption does not prevent a breach, but it can reduce the usefulness of stolen data.
Sensitive databases, backups and credentials should be protected using modern encryption and secure key management.
Encryption should also be combined with access controls rather than treated as a replacement for them.
Segmentation Could Limit a Multi-System Breach
If reservation, HR, accounting and security systems are placed behind independent access boundaries, compromising one system becomes less likely to expose everything.
Network segmentation can therefore transform a potentially catastrophic compromise into a contained incident.
The Alleged Breach Is a Reminder About Identity Security
Passwords remain one of the weakest links in many organizations.
Strong password policies, multifactor authentication, password managers and phishing-resistant authentication can significantly reduce the value of stolen credentials.
Where possible, organizations should move toward stronger authentication standards rather than relying on passwords alone.
Public Claims Should Be Handled Carefully
Threat intelligence reporting must balance urgency with accuracy.
Publishing an unverified allegation as confirmed fact can create unnecessary panic and potentially damage organizations or individuals.
The responsible approach is to clearly distinguish between what the threat actor claims, what researchers have observed and what has been independently verified.
The $10,000 Question Is Not Really About Money
The asking price may attract attention, but the larger issue is what the data could enable.
If authentic, the dataset could potentially support identity fraud, phishing, credential attacks, corporate espionage or additional compromises.
That potential downstream value can be much greater than the original purchase price.
Cuba’s Hospitality Infrastructure Could Face Broader Pressure
The alleged incident also demonstrates that organizations operating in countries with significant geopolitical attention can become attractive targets for a wide variety of threat actors.
Whether the motive is financial, intelligence-driven or simply opportunistic cannot be determined from the marketplace listing alone.
Attribution should therefore be avoided until stronger evidence becomes available.
The Most Important Evidence Is Still Missing
At present, the key unanswered question is whether the seller actually possesses authentic and recent Gran Caribe data.
Without independently verified samples or technical evidence, the 110 GB claim remains just that—a claim.
That distinction should remain at the center of any responsible coverage of this incident.
What Undercode Say:
A Potentially Serious Claim, But Not Yet a Confirmed Breach
The alleged Gran Caribe incident is exactly the kind of dark web claim that deserves attention without being treated as proven fact.
The Dataset Description Is Technically Detailed
The marketplace listing describes multiple database categories, SQL Server infrastructure, .BAK files and specific types of information.
That level of detail makes the allegation interesting, but technical detail alone does not establish authenticity.
The Number of Databases Raises Questions
Thirty-four databases would represent a broad intrusion if the claim is accurate.
Investigators should determine whether those databases belong to one centralized environment or represent multiple independently compromised systems.
The 110 GB Figure Needs Independent Validation
Large datasets are impressive headlines, but volume can be inflated through duplicate, historical or non-sensitive records.
The actual number of unique affected individuals matters more than raw storage size.
Guest Information Would Be Highly Sensitive
Reservation and check-in information could expose personal travel patterns.
If authentic and current, this category deserves immediate privacy and security attention.
Employee Data Could Enable Social Engineering
Names, departments, positions and telephone numbers can make phishing attacks much more convincing.
The alleged employee dataset therefore creates a potential secondary threat even if passwords were not exposed.
Financial Data Could Create Business Risks
Financial statements and accounting records could reveal sensitive information about the organization.
Competitors, criminals or other unauthorized parties could potentially exploit such information.
Wi-Fi Credentials Deserve Special Scrutiny
The reported MD5 hashes are concerning because MD5 is not suitable for modern password storage.
If confirmed, affected credentials should be considered potentially recoverable depending on password strength and other controls.
Security Credentials Could Increase the Severity
The alleged presence of security-system credentials would move the incident beyond a conventional customer-data breach.
However, there is currently no verified evidence that attackers gained operational control of security systems.
Dark Web Sellers Have Incentives to Exaggerate
A threat actor trying to sell data has an obvious financial motivation.
Claims should therefore be independently tested rather than accepted at face value.
The Timing Is Worth Watching
The alleged August 10 breach date and August 12 report create a narrow timeline.
Future disclosures, samples or victim statements could help establish whether the claim is genuine.
Gran Caribe Should Be Treated as a Potentially At-Risk Organization
Even without confirmation, the allegation provides a reason to review credentials, database activity, remote access and unusual data transfers.
Defensive verification is more useful than waiting for certainty.
Customers Should Remain Alert
People who have recently interacted with affected hotel properties should be cautious with unexpected messages referencing reservations, payments or hotel stays.
A breach claim does not prove that any particular individual was affected, but targeted phishing is a plausible secondary risk.
Employees May Face Increased Targeting
If the alleged HR records are real, employees could receive highly personalized impersonation attempts.
Security awareness should therefore emphasize unusual requests involving credentials, payments and account recovery.
The Data Could Have Intelligence Value
Hotel records can reveal movements, organizational relationships and travel patterns.
That makes hospitality databases potentially valuable beyond conventional financial cybercrime.
Centralized Systems Are a Major Security Consideration
Shared infrastructure can simplify operations but also concentrate risk.
A single compromised administrative environment can potentially affect multiple properties.
Segmentation Should Be a Priority
Reservation systems, HR platforms, accounting infrastructure and physical security systems should not have unrestricted connectivity.
Strong segmentation can limit lateral movement.
Backup Security Is Equally Important
The reported .BAK files demonstrate why database backups should receive strong protection.
Backups can contain almost everything attackers need to reconstruct an organization’s information environment.
Authentication Should Be Strengthened
Multifactor authentication and phishing-resistant credentials can reduce the consequences of stolen passwords.
Organizations should especially prioritize privileged accounts.
Monitoring Should Focus on Data Movement
Large exports and unusual database queries can sometimes reveal data theft.
Strong logging can make these activities easier to identify.
Data Retention Should Be Reviewed
Organizations should not retain sensitive personal information indefinitely without a legitimate reason.
Reducing unnecessary data can reduce the impact of future breaches.
The Incident Shows Why Verification Matters
Dark web intelligence is valuable because it can reveal threats before organizations publicly acknowledge them.
But intelligence becomes reliable only when allegations are tested against technical evidence.
A Claim Can Still Be Useful Without Being Confirmed
Even if the Gran Caribe listing eventually proves false or exaggerated, it can still serve as a trigger for defensive investigation.
That is one of the most useful roles of threat intelligence.
The $10,000 Price Is Not Proof
A seller setting a price does not establish the authenticity of the material.
The market value of the information should be separated from its credibility.
The Most Dangerous Data May Not Be the Largest Dataset
A small collection of valid administrator credentials can potentially be more damaging than gigabytes of historical hotel records.
Security teams should prioritize authentication secrets and privileged access.
The Human Impact Should Remain Central
Behind every database entry is potentially a real guest, employee or business relationship.
Cybersecurity analysis should therefore focus not only on technical scale but also on privacy and personal consequences.
Attribution Should Be Avoided
Nothing in the supplied allegation establishes who conducted the intrusion or why.
Threat actor claims should not be transformed into unsupported attribution.
The Next Few Days Could Be Important
Additional samples, independent researchers, victim confirmation or evidence of data circulation could materially change the assessment.
For now, the situation should remain classified as an alleged breach claim.
Undercode Assessment
The allegation is technically plausible and serious enough to warrant monitoring, but the available evidence does not justify presenting the breach as confirmed.
The strongest response is careful verification combined with immediate defensive checks.
❌ The Gran Caribe Breach Is Not Independently Confirmed
The supplied report explicitly states that the intrusion, 110 GB volume, samples and August 10 breach date have not been independently verified. The incident should therefore be described as an alleged breach rather than a confirmed compromise.
✅ The Reported Dataset Claims Are Accurately Represented
The threat actor reportedly claims 34 Microsoft SQL Server databases totaling approximately 110 GB, covering eight hotel properties and multiple business functions. These details are presented as claims rather than established facts.
❌ The $10,000 Price Does Not Prove the Data Is Authentic
The alleged seller is reportedly asking $10,000 USD, negotiable. However, an underground marketplace price provides no independent evidence that the advertised database is genuine or that the claimed information was actually stolen from Gran Caribe.
Prediction
(-1) A Verified Breach Could Trigger Significant Privacy Concerns
If independent researchers confirm that the data is authentic and current, the incident could become a significant privacy and cybersecurity event involving guests, employees and hotel operations.
(-1) Exposed Credentials Could Create Follow-On Attacks
If valid Wi-Fi, administrative or security credentials are included, attackers could potentially attempt credential reuse, phishing, unauthorized access or lateral movement.
(+1) Early Detection Could Limit the Damage
If Gran Caribe or its security partners identify the alleged compromise quickly, credential rotation, access restrictions, segmentation and incident-response measures could substantially reduce further exploitation.
(+1) Independent Verification Could Clarify the Situation
Additional samples and technical investigation should eventually establish whether the alleged 110 GB dataset is authentic, recycled, fabricated or substantially different from what the seller claims.
(-1) Stolen Data Could Continue Circulating
If the database is genuine, even removing the original marketplace listing would not eliminate the risk. Copies could be redistributed among multiple criminal actors.
(+1) The Claim Can Serve as a Defensive Warning
Even before confirmation, the allegation gives defenders an opportunity to investigate unusual database activity, review exposed credentials and strengthen controls around sensitive systems.
(-1) The Combination of Guest and Employee Data Would Increase Risk
If both categories are authentic, attackers could potentially combine personal and organizational information to conduct more convincing phishing, fraud and impersonation campaigns.
(-1) Security-System Exposure Would Be Especially Serious
If the alleged security credentials prove valid, the potential consequences could extend beyond data privacy into operational security concerns.
(+1) Strong Segmentation Could Contain the Incident
If Gran Caribe maintains effective separation between hotel operations, HR, accounting, guest services and security infrastructure, even a genuine database compromise may be prevented from becoming a full-network intrusion.
(+1) Overall Forecast
The most likely immediate development is continued investigation and monitoring rather than instant confirmation. Until independent evidence emerges, the responsible assessment is that Gran Caribe may have been targeted, but the alleged 110 GB breach remains unverified.
▶️ Related Video (66% Match):
🕵️📝Let’s dive deep and fact‑check.
🎓 Live Courses & Certifications:
Join Undercode Academy for Verified Certifications
🚀 Request a Custom Project:
Secure, high-velocity infrastructure and disruptive technological engineering. Contact our engineering team for high-tier development and proprietary systems:
[email protected]
💎 Smart Architecture | 🛡️ Secure by Design | ⭐ Trusted by Thousands
References:
Reported By: x.com
Extra Source Hub (Possible Sources for article):
https://www.quora.com/topic/Technology
Wikipedia
OpenAi & Undercode AI
Image Source:
Unsplash
Undercode AI DI v2
🔐JOIN OUR CYBER WORLD [ CVE News • HackMonitor • UndercodeNews ]
📢 Follow UndercodeNews & Stay Tuned:
𝕏 formerly Twitter 🐦 | @ Threads | 🔗 Linkedin | 🦋BlueSky | 🐘Mastodon | 📺Youtube
