Listen to this Post
A New Warning for Metabase Users
A new threat claim circulating on an underground cybercrime forum has put the Metabase analytics platform back under intense security scrutiny. A threat actor claims to possess working proof-of-concept code for CVE-2026-72898, a critical SQL injection vulnerability that can allow an unauthenticated remote attacker to reach administrator-level access inside a vulnerable Metabase deployment.
The claim is particularly concerning because CVE-2026-72898 is not merely a theoretical vulnerability. Metabase itself has described the flaw as critical, assigned it a CVSS score of 10.0, and confirmed active exploitation. The vulnerability allows arbitrary SQL injection through a password-reset-related endpoint and can ultimately expose credentials, connected databases, configuration data, and information accessible through Metabase.
GitHub
+1
That makes the latest underground claim important even though its most dramatic numbers remain unverified. The alleged availability of operational exploit tooling could lower the technical barrier for attackers and potentially accelerate scanning against exposed Metabase installations.
What the Threat Actor Claims
According to the Dark Web Intelligence report, an actor on an underground cybercrime forum claims to have released a functioning PoC targeting CVE-2026-72898.
The alleged tool reportedly includes capabilities for automated discovery of vulnerable Metabase instances, database extraction, mass scanning, and attempts to move from the initial SQL injection into remote code execution.
The actor additionally claims to have compromised more than 600 Metabase databases and obtained more than 50 RCE sessions operating with PostgreSQL user privileges.
Those figures would represent a potentially significant campaign if independently confirmed. However, there is currently no reliable evidence establishing that the claimed number of compromised databases or RCE sessions is genuine.
The Vulnerability Behind the Claim
CVE-2026-72898 is a serious SQL injection vulnerability affecting multiple Metabase release branches. Metabase’s security advisory states that an unauthenticated remote attacker can inject arbitrary SQL into the Metabase application database and potentially obtain administrator access.
GitHub
The affected versions include branches from 58.x through 63.x, with fixes released at 58.24, 59.21, 60.17, 61.11, 62.9, and 63.5 respectively.
GitHub
+1
The vulnerability is also classified as CWE-89, the standard weakness category for improper neutralization of SQL commands. Its CVSS 3.1 and CVSS 4.0 scores are both 10.0, placing it at the highest criticality level.
OpenCVE
Why Administrator Access Changes Everything
The most important detail is that the
According to the vendor advisory, an attacker who reaches administrator access could modify application configuration, steal credentials stored for connected databases, access information available through those connections, and export data.
GitHub
This creates a dangerous chain in which a vulnerability in an analytics platform can become a gateway into broader organizational data infrastructure.
The PostgreSQL Question
The underground post specifically claims access to RCE sessions running with PostgreSQL privileges. That part deserves careful scrutiny.
A SQL injection vulnerability should not automatically be interpreted as an unrestricted operating-system remote-code-execution vulnerability. The confirmed Metabase vulnerability provides a route to SQL injection and administrator access, but whether that can be transformed into operating-system-level execution depends on the surrounding architecture, database configuration, privileges, extensions, operating-system controls, and additional weaknesses.
Therefore, the
The 600-Database Claim Needs Verification
The claim of more than 600 compromised Metabase databases is equally difficult to validate from the available information.
Underground actors frequently exaggerate the size and impact of their operations to increase credibility, attract buyers, pressure victims, or advertise exploit capabilities.
At the same time, dismissing the claim simply because it appeared on a criminal forum would be a mistake. The underlying vulnerability is independently confirmed, actively exploited, and capable of causing serious compromise.
GitHub
+1
The correct security posture is therefore neither panic nor complacency: treat the exploit claim as a credible warning while treating the actor’s statistics as unverified intelligence.
Active Exploitation Was Already Confirmed
One of the most important facts surrounding this story is that exploitation of CVE-2026-72898 was already confirmed before the latest dark-web claim appeared.
Metabase’s own advisory explicitly states that the vulnerability has been actively exploited and urges organizations to upgrade as soon as possible.
GitHub
The vulnerability was also added to the CISA Known Exploited Vulnerabilities catalog in August 2026, indicating that exploitation was significant enough to warrant heightened remediation priority.
CVE | THREATINT
That context makes the appearance of additional exploit tooling considerably more concerning.
Real-World Evidence Shows the Risk Is Not Theoretical
The consequences have already moved beyond vulnerability databases and laboratory demonstrations.
Cloud platform provider Scalingo reported that one of its internal Metabase instances was successfully exploited, resulting in unauthorized exfiltration of personal data and customer-related metadata from an internal analytics data warehouse. Scalingo said approximately 90,000 individuals were affected, while noting that it found no evidence of compromise of customer production applications or production databases.
Documentation Center
This incident demonstrates an important lesson: the compromise of Metabase itself can have consequences beyond the analytics application.
Why Internet-Exposed Metabase Instances Are Especially Dangerous
A vulnerable Metabase server exposed directly to the Internet presents an attractive target because attackers do not necessarily need stolen credentials or user interaction to begin exploitation.
The vulnerability is remotely exploitable, requires no privileges, has low attack complexity, and requires no user interaction according to its CVSS metrics.
OpenCVE
That combination is exactly what makes a vulnerability attractive for automated scanning.
An attacker does not need to personally identify a company before attempting exploitation. Automated systems can search large numbers of hosts, identify recognizable Metabase installations, and test whether those systems appear vulnerable.
Mass Scanning Could Change the Threat Landscape
If the underground
A vulnerability that requires extensive manual research may remain relatively difficult to exploit at scale. A vulnerability accompanied by reliable automation is different.
Once discovery, exploitation, extraction, and reporting are automated, attackers can move from targeting individual organizations to systematically searching the Internet for vulnerable infrastructure.
The Danger of Connected Data Sources
Metabase is designed to connect analytics users with databases and data warehouses.
That makes its security boundary especially important.
A compromise of Metabase can potentially provide an attacker with visibility into data sources that were never directly exposed to the Internet. The vendor specifically warns that attackers gaining administrator access could steal stored database credentials and read data accessible through connected databases.
GitHub
The real security question is therefore not simply, “Is Metabase vulnerable?”
It is also, “What can the compromised Metabase account reach?”
The Database Should Be Considered Part of the Attack Surface
Organizations sometimes treat business-intelligence applications as presentation layers rather than sensitive infrastructure.
That assumption can be dangerous.
If a BI platform maintains credentials or privileged connections to production databases, data warehouses, customer repositories, financial systems, or internal analytics environments, the platform becomes part of the organization’s broader data security perimeter.
The security of those downstream systems can therefore depend partly on the security of Metabase itself.
What Organizations Should Do Immediately
Organizations running Metabase should first identify every deployed instance, including cloud-hosted, containerized, development, testing, and forgotten legacy environments.
They should then determine the exact Metabase version running on each instance and compare it against the vendor’s patched versions.
The confirmed fixes are 58.24, 59.21, 60.17, 61.11, 62.9, and 63.5, depending on the release branch.
GitHub
Patching Is the First Priority
The safest response is to upgrade affected installations to the appropriate fixed release.
Metabase specifically recommends upgrading as soon as possible. For organizations temporarily unable to upgrade, the vendor recommends blocking the affected /api/session/reset_password endpoint as an interim mitigation.
GitHub
A temporary mitigation should not be treated as a substitute for the permanent security update.
Internet Exposure Should Be Reconsidered
Organizations should also determine whether Metabase genuinely needs to be reachable directly from the public Internet.
Where possible, access should be restricted through VPNs, identity-aware proxies, private networks, firewalls, or other access-control mechanisms.
Reducing unnecessary exposure does not eliminate the vulnerability, but it can substantially reduce the number of attackers who can reach the vulnerable service.
Session Revocation Matters After a Possible Compromise
Patching a compromised instance does not necessarily erase evidence of an earlier intrusion.
Metabase recommends revoking active sessions after upgrading an instance whose password-reset endpoint was publicly accessible, reviewing the core_session table, examining API keys, checking administrator accounts, rotating connected database credentials, and reviewing data warehouse logs.
GitHub
These steps are important because an attacker may establish persistence before defenders deploy the patch.
API Keys Deserve Special Attention
Organizations should examine all Metabase API keys and identify credentials that cannot be accounted for.
An unfamiliar API key should be treated as potentially malicious until proven otherwise.
Credential rotation is particularly important when Metabase has access to sensitive databases, because an attacker who extracts database credentials may retain access even after the original Metabase vulnerability has been patched.
Administrator Accounts Should Be Audited
Security teams should review Metabase administrator accounts for unexpected additions, privilege changes, password resets, or other suspicious modifications.
Unexpected administrative activity can provide an important clue that an attacker progressed beyond initial exploitation.
The investigation should also include authentication events, application logs, reverse-proxy logs, firewall telemetry, database activity, and identity-provider records where available.
Query History Can Become an Important Forensic Source
Metabase query history and data warehouse logs may help reveal activity that does not resemble normal organizational behavior.
Large exports, unusual queries, access to previously unused tables, abnormal administrator actions, or activity occurring at unusual times can all help establish whether an instance was abused.
The goal should not simply be determining whether exploitation occurred, but understanding what the attacker accessed after gaining entry.
Deep Analysis: How CVE-2026-72898 Could Become a Larger Attack Campaign
From SQL Injection to Initial Access
The central danger of CVE-2026-72898 is the combination of remote reachability, lack of authentication requirements, and the ability to influence the Metabase application database.
That creates a potentially powerful initial-access mechanism for attackers searching for exposed installations.
From Initial Access to Administrative Control
The
That dramatically changes the
From Metabase to Connected Databases
Once an attacker controls Metabase, connected databases become strategically important.
The attacker may not need to attack every database directly if the compromised analytics platform already has legitimate access to them.
This is why least-privilege database accounts are particularly important.
Least Privilege Can Limit the Blast Radius
If Metabase uses a highly privileged database account, compromise of the analytics platform could have a much broader impact.
If it instead uses tightly restricted read-only accounts limited to specific datasets, the same compromise may still be serious but potentially less destructive.
Security architecture can therefore determine how far an attacker can travel after exploiting the same vulnerability.
RCE Should Be Treated as a Separate Claim
The underground
The confirmed vulnerability is an unauthenticated SQL injection leading to administrator access.
That does not establish universal operating-system command execution.
Additional technical conditions would need to exist for an attacker to move from SQL-level access into operating-system-level execution.
PostgreSQL Privileges Matter
The claim involving PostgreSQL privileges could indicate that the attacker is attempting to leverage database-level capabilities after obtaining SQL execution.
But database privileges vary dramatically between environments.
A hardened PostgreSQL deployment with restricted roles and limited extensions presents a different attack surface from an unnecessarily privileged database account.
Automation Is the Bigger Strategic Threat
The most significant part of the alleged PoC may not be RCE.
It may be automation.
A reliable scanner that can discover vulnerable Metabase installations could enable attackers to identify targets at Internet scale.
That transforms the vulnerability from an issue affecting individual organizations into a potential ecosystem-wide exposure problem.
Exploit Availability Changes Defender Priorities
Once exploit code becomes publicly available or circulates within criminal communities, defenders can expect more experimentation.
Attackers who previously lacked the technical ability to reproduce a vulnerability may simply adapt existing tooling.
That can create a sharp increase in scanning and exploitation shortly after exploit publication.
The Underground Economy Amplifies Vulnerabilities
Cybercriminal ecosystems frequently turn technical vulnerabilities into commercial opportunities.
One actor may discover the vulnerability, another may develop automation, another may purchase access, and another may monetize stolen data.
That means a vulnerability does not have to be sophisticated to become profitable.
Data Extraction Can Be More Valuable Than RCE
For many organizations, the ability to access sensitive analytics data could be more financially valuable than obtaining a shell on the server.
Business intelligence systems may contain customer information, financial reports, operational metrics, employee information, sales data, and strategic business intelligence.
A database-focused compromise can therefore produce significant consequences without traditional malware deployment.
The “Analytics Tool” Label Can Create False Confidence
Security teams sometimes prioritize customer-facing applications while treating internal analytics tools as secondary systems.
CVE-2026-72898 demonstrates why that model is increasingly outdated.
An analytics platform can sit directly between users and highly valuable databases.
Its position in the architecture can make it an attractive bridge into otherwise protected information.
Cloud Deployments Require Special Attention
Cloud-hosted Metabase instances may have additional exposure through public IP addresses, security groups, reverse proxies, load balancers, and identity systems.
Organizations should not assume that placing Metabase in the cloud automatically makes it secure.
The opposite can sometimes be true when default Internet exposure is combined with weak access controls.
Containers Do Not Automatically Neutralize the Risk
Containerized Metabase deployments can provide useful isolation, but containers are not a substitute for vulnerability management.
A vulnerable application inside a container can still expose credentials, access databases, leak sensitive information, and potentially provide a foothold for further attacks depending on the surrounding environment.
Secrets Management Becomes Critical
Database passwords, API credentials, tokens, and other secrets associated with Metabase should be treated as potentially exposed if an affected instance may have been compromised.
Simply upgrading the application may not be sufficient if an attacker has already obtained credentials.
Detection Should Continue After Patching
Organizations should continue monitoring patched systems for signs of earlier exploitation.
Attackers may have compromised an instance days or weeks before defenders discovered the vulnerability.
A patch closes the vulnerability; it does not automatically remove persistence, stolen credentials, unauthorized accounts, or previously extracted information.
Threat Intelligence Should Be Used Carefully
The dark-web claim is useful intelligence, but it should not be treated as confirmed incident evidence.
Threat intelligence is strongest when underground claims are correlated with technical indicators, logs, malware samples, infrastructure telemetry, or independent victim reports.
The correct response is to use the claim to accelerate investigation rather than to automatically accept every statement made by the actor.
The 600-Database Figure Is Not Yet Proven
The reported figure of more than 600 databases is attention-grabbing but remains unsupported by independent evidence in the material available for this report.
That distinction matters.
Reporting an unverified number as an established fact could unnecessarily create panic and undermine otherwise legitimate vulnerability reporting.
The 50+ RCE Sessions Are Also Unverified
The same caution applies to the claim of more than 50 RCE sessions.
The confirmed CVE documentation establishes SQL injection and administrator access, not an automatic RCE pathway in every environment.
GitHub
+1
Therefore, the RCE claim requires technical validation before it should be considered a confirmed capability.
The Underlying Vulnerability Is Still Extremely Serious
Rejecting the unverified claims does not reduce the severity of the actual vulnerability.
CVE-2026-72898 has a CVSS score of 10.0, requires no authentication, requires no user interaction, and has been associated with active exploitation.
OpenCVE
That makes immediate remediation justified even if the underground actor’s claims ultimately prove exaggerated.
CISA’s Classification Raises the Stakes
The inclusion of CVE-2026-72898 in the CISA Known Exploited Vulnerabilities catalog is another strong indicator that organizations should treat this issue as an active security problem rather than a future theoretical risk.
CVE | THREATINT
For federal organizations in particular, KEV inclusion creates a formal remediation priority.
The Attack Surface May Be Larger Than Expected
Organizations should search beyond their known production Metabase deployment.
Old test servers, staging systems, forgotten cloud instances, temporary environments, developer installations, and externally hosted services can all become overlooked entry points.
Attackers do not care whether an organization considers an instance “temporary.”
Asset Discovery Is Part of Remediation
The first question for many companies should therefore be: Where is Metabase running?
Without an accurate inventory, security teams cannot reliably determine which systems require patching.
This is one reason vulnerability management and asset management have become inseparable.
Database Credential Rotation Should Follow Risk Assessment
If an affected Metabase installation was exposed to the Internet or shows signs of exploitation, connected database credentials should be rotated.
This is particularly important where those credentials provide access to sensitive or production environments.
Network Segmentation Can Limit Future Damage
Metabase should ideally have only the network connectivity it genuinely requires.
Segmentation can prevent a compromised analytics application from freely communicating with unrelated internal systems.
It is not a complete defense against CVE-2026-72898, but it can reduce the blast radius.
Security Teams Should Assume Attackers Move Quickly
The combination of an actively exploited vulnerability and alleged exploit automation creates an environment in which defenders should assume that attackers are moving faster than traditional patch cycles.
Organizations should prioritize emergency vulnerability response rather than waiting for routine maintenance windows where feasible.
The Most Important Lesson
The deeper lesson from CVE-2026-72898 is that a vulnerability does not need to provide immediate operating-system RCE to become devastating.
An unauthenticated route to administrative control over an analytics platform that connects to valuable databases can already provide attackers with substantial leverage.
Why This Story Matters Beyond Metabase
The incident reflects a broader cybersecurity trend.
Attackers increasingly target the infrastructure surrounding core applications: analytics platforms, identity systems, monitoring tools, management consoles, development platforms, and other trusted services.
These systems often possess legitimate access to valuable resources.
Compromise the trusted intermediary, and the attacker may inherit some of that trust.
What Defenders Should Remember
The strongest defense is not simply “patch Metabase.”
It is a layered strategy combining rapid patching, minimal Internet exposure, least-privilege database access, credential rotation, network segmentation, monitoring, logging, and incident response.
CVE-2026-72898 is a reminder that every application with access to sensitive data should be treated as part of the organization’s security perimeter.
What Undercode Say:
A Critical Vulnerability Meets an Underground Exploit Claim
The most important distinction in this story is between what has been independently confirmed and what the threat actor claims.
The Confirmed Technical Risk Is Already Severe
CVE-2026-72898 is independently documented as a critical unauthenticated SQL injection vulnerability affecting Metabase.
The CVSS 10.0 Score Is Significant
The maximum severity rating is consistent with the vulnerability’s ability to be exploited remotely without authentication or user interaction.
Active Exploitation Changes the Calculation
This is not merely a vulnerability waiting for attackers to discover it.
Metabase has confirmed active exploitation.
The Dark Web Claim Adds a New Layer
The reported PoC claim suggests that criminal actors may be attempting to operationalize the vulnerability at greater scale.
Automation Could Be More Dangerous Than Individual Exploitation
Mass scanning can dramatically increase the number of organizations exposed to exploitation attempts.
Database Access Is the Real Prize
For many attackers, access to sensitive databases is more valuable than obtaining an operating-system shell.
Metabase Can Sit in a Powerful Position
Because Metabase connects users and applications to databases, its compromise can create a path toward valuable downstream information.
Credentials Increase the Potential Blast Radius
Stored database credentials can transform a Metabase compromise into a much broader data-security incident.
RCE Claims Require Technical Evidence
The alleged 50-plus RCE sessions should not be accepted as fact without independent validation.
SQL Injection Does Not Automatically Equal RCE
The confirmed CVE establishes SQL injection and administrator access, while operating-system execution may require additional conditions.
The 600-Database Claim Is Equally Unverified
The alleged number of compromised databases is substantial, but the available evidence does not independently establish it.
Exaggeration Is Common in Criminal Forums
Threat actors have incentives to inflate numbers when advertising capabilities or attempting to intimidate victims.
But Exaggeration Does Not Mean the Threat Is Fake
Even if the numbers are inflated, the underlying Metabase vulnerability remains real and actively exploited.
CISA’s KEV Listing Is a Major Warning
The
Patch Management Must Move Faster
Organizations should not wait for evidence that their particular server has been targeted before applying the available fixes.
Exposure Reduction Is Equally Important
Internet-facing Metabase systems deserve particular attention because unauthenticated remote exploitation eliminates many traditional barriers.
The Endpoint Deserves Investigation
Security teams should specifically investigate traffic and activity associated with the affected password-reset endpoint.
Logs Can Tell the Story
Application, reverse-proxy, firewall, database, and identity logs may reveal exploitation or post-compromise activity.
Session Revocation Can Break Persistence
Organizations investigating potentially compromised systems should follow
API Keys Must Be Audited
Unknown or suspicious API keys could provide attackers with continuing access after the original vulnerability is patched.
Administrator Accounts Need Review
Unexpected administrative accounts or privilege changes should be treated as potential indicators of compromise.
Database Credentials Should Be Rotated When Necessary
If an affected Metabase instance may have been compromised, connected credentials should be considered potentially exposed.
Production Access Requires Extra Caution
A Metabase account should not possess broader database privileges than necessary for its legitimate function.
Read-Only Access Can Reduce Damage
Where appropriate, restrictive database roles can limit what an attacker can do after compromising the analytics layer.
Network Segmentation Adds Another Barrier
A compromised analytics server should not automatically have unrestricted access across an organization’s internal network.
Asset Inventory Is Essential
Unknown Metabase instances can remain vulnerable even after the primary production system has been patched.
Staging Systems Can Become Attack Targets
Security teams should include non-production environments in emergency vulnerability searches.
Cloud Security Groups Matter
Cloud deployments should be examined for unnecessary public exposure and overly permissive inbound access.
Containers Are Not a Complete Security Boundary
Containerization can help with isolation, but it does not remove the consequences of a vulnerable application.
Threat Intelligence Should Drive Investigation
Underground claims can serve as early warning signals when correlated with defensive telemetry.
Intelligence Should Not Become Panic
Security teams should distinguish verified technical facts from unverified criminal claims.
The Vendor Advisory Is the Baseline
Metabase’s own security guidance should remain the primary source for remediation decisions.
The Exploit Economy Can Accelerate Quickly
Once reliable tooling becomes available, less-skilled attackers can enter the exploitation cycle.
Vulnerability Disclosure Can Have a Second Phase
The initial vulnerability disclosure may be followed by public PoCs, criminal tooling, mass scanning, and automated exploitation.
The Window for Defense Can Shrink Rapidly
Organizations that delay patching can find themselves defending against an increasingly automated threat.
The Biggest Mistake Is Waiting for Proof of Compromise
Security teams should not require evidence of successful exploitation before fixing a critical actively exploited vulnerability.
CVE-2026-72898 Deserves Emergency Treatment
The combination of maximum severity, active exploitation, and alleged operational PoC activity makes this a vulnerability that should receive immediate attention.
The Dark Web Claim Is a Warning, Not a Verdict
The
Undercode’s Assessment
The strongest conclusion is straightforward: organizations should act as though CVE-2026-72898 is actively dangerous regardless of whether the 600-database and 50-RCE claims are ultimately proven.
Confirmed Vulnerability
✅ CVE-2026-72898 is real and critical. Metabase documents it as an unauthenticated SQL injection vulnerability that can lead to administrator access, with a CVSS score of 10.0.
GitHub
+1
Active Exploitation
✅ Active exploitation has been confirmed. Metabase states that the vulnerability has been actively exploited, and the vulnerability was added to the CISA Known Exploited Vulnerabilities catalog.
GitHub
+1
Dark Web Numbers
❌ The claims of 600+ compromised databases and 50+ RCE sessions are not independently verified. They should currently be treated as threat-actor allegations rather than established facts.
RCE Capability
❌ CVE-2026-72898 should not automatically be described as universal RCE. The confirmed vulnerability provides SQL injection and administrator access; operating-system-level RCE would depend on additional technical conditions.
Prediction
(+1) Exploitation Will Continue to Increase
(+1) The combination of active exploitation, maximum severity, and potential availability of operational tooling makes further exploitation attempts highly likely.
(+1) Automated Scanning Will Become More Common
(+1) If the reported PoC genuinely supports mass scanning, attackers will likely use automation to identify vulnerable Metabase installations at scale.
(+1) More Victims Could Appear
(+1) Organizations that have not patched or restricted exposed Metabase instances may discover unauthorized access, data theft, or credential exposure in the coming weeks.
(+1) Defensive Detection Will Improve
(+1) As awareness grows, security teams will increasingly monitor Metabase endpoints, database activity, administrator changes, API keys, and suspicious query behavior for exploitation indicators.
(-1) Criminal Claims May Be Exaggerated
(-1) The reported numbers of compromised databases and RCE sessions may ultimately prove inflated, incomplete, or misleading.
(-1) Unpatched Systems Face the Greatest Risk
(-1) Organizations that leave vulnerable Metabase installations exposed after the exploitation wave expands could face significantly greater incident-response and data-protection costs.
(+1) Patching Can Dramatically Reduce Exposure
(+1) Organizations that rapidly upgrade to fixed Metabase versions, restrict unnecessary Internet exposure, rotate potentially compromised credentials, and investigate logs can substantially reduce the likelihood of continued compromise.
▶️ Related Video (84% 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.discord.com
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
