Listen to this Post
A New Warning for Healthcare and Retail
Cybersecurity incidents are increasingly showing that attackers do not need to completely shut down a company to cause lasting damage. Sometimes, a few hours of disruption can expose sensitive information, while an alleged intrusion at a major retailer can create operational uncertainty across an entire market.
Two cybersecurity developments highlighted on August 19, 2026, illustrate that problem from very different angles. CareCloud says a March security incident involving its healthcare environment may have exposed information associated with approximately 3.7 million people. Separately, a ransomware claim allegedly connected to the threat actor known as xpl0itrs reportedly targeted Target and disrupted parts of its U.S. retail operations.
The CareCloud incident is particularly serious because healthcare systems contain some of the most valuable personal information available to criminals. The company previously disclosed that a March 16, 2026, security incident caused approximately eight hours of disrupted functionality and data access in one of its six electronic health record environments. Its later filing said investigators determined that an unauthorized third party accessed a cloud account supporting that environment and exfiltrated patient-related information.
The Target allegation presents a different kind of threat. While the claim should not be treated as independently verified simply because it appears in a cybersecurity report or social-media post, the reported association with xpl0itrs is noteworthy. The group has been connected in public reporting to access-broker activity and other supply-chain-focused operations.
Together, the incidents underline a broader reality: modern cyberattacks are increasingly about access, data, persistence and leverage, rather than simply deploying malware and demanding money.
CareCloud Incident Reaches a Potentially Massive Scale
CareCloud’s March 2026 incident initially appeared to be an operational disruption affecting one part of its healthcare technology environment.
The company reported that functionality and data access were interrupted for approximately eight hours before being restored the same day. At that stage, the incident was described as contained to the CareCloud Health environment, with no evidence that other platforms, divisions, systems or environments had been affected.
That description became much more concerning after forensic investigators determined that an unauthorized third party had gained access to a cloud account supporting the affected electronic health record environment.
According to
The reported figure of approximately 3.7 million potentially affected individuals dramatically changes the significance of the incident.
Eight Hours of Downtime Can Hide a Much Larger Problem
One of the most important lessons from the CareCloud case is that the visible operational disruption was relatively short.
Eight hours may sound like a serious outage for a healthcare technology provider, but it is still only a small part of the overall incident lifecycle. The more consequential activity may have occurred before the disruption was detected.
An attacker can potentially gain access, identify valuable databases, collect information and move data outside an environment without immediately causing a noticeable outage.
This creates a dangerous distinction between service disruption and data compromise.
A company can restore its systems in a matter of hours while spending months investigating what information may have been accessed, determining who may have been affected, notifying customers and regulators, and responding to legal consequences.
Cloud Accounts Have Become High-Value Targets
The CareCloud disclosure is also a reminder that cloud security cannot be reduced to protecting servers.
The investigation identified unauthorized access to a cloud account supporting an electronic health record environment.
That detail matters because cloud identities frequently provide access to multiple services at once.
A compromised credential, token, administrative account or poorly protected service identity can potentially become a doorway into databases, storage systems, application infrastructure and sensitive business information.
The cloud does not eliminate security risk. It changes where that risk lives.
Healthcare Data Is Especially Valuable
Healthcare organizations remain attractive targets because their databases combine identity information with deeply personal records.
A stolen email address can be inconvenient. A stolen medical record can be far more difficult to replace.
Healthcare information can include names, identifiers, insurance information, treatment-related details, billing records and other data that may remain valuable for years.
That long lifespan makes healthcare breaches particularly damaging.
An attacker does not necessarily need to immediately monetize every stolen record. Information can be retained, combined with other datasets, sold through criminal marketplaces or used in future fraud.
The Legal Consequences Can Outlive the Technical Incident
CareCloud’s regulatory filing also shows how a cybersecurity incident can continue long after systems return to normal.
The company disclosed that multiple class-action complaints were filed alleging that personal information had been compromised. Those cases were later consolidated in federal court, with plaintiffs filing a consolidated amended complaint.
This is an important part of the modern breach equation.
The cost of an incident is not simply the price of rebuilding servers or hiring incident-response specialists. Organizations can face notification expenses, legal costs, regulatory scrutiny, customer support demands, cybersecurity improvements, insurance claims and reputational damage.
The technical emergency may last hours.
The business emergency can last years.
Target Faces a Different Kind of Cybersecurity Threat
The Target story described in the supplied report is less established than the CareCloud incident.
The report says Target experienced a ransomware incident allegedly linked to xpl0itrs, with disruption affecting U.S. retail operations and indications of unauthorized access.
At this stage, that should be treated as an allegation, not a confirmed attribution.
That distinction is critical in cybersecurity reporting because threat actors sometimes claim attacks they did not conduct, exaggerate the scale of intrusions, recycle old information or publish misleading evidence.
A ransomware claim becomes substantially more credible when independent evidence emerges from the victim, investigators, incident-response firms, law enforcement or verifiable technical artifacts.
Why the xpl0itrs Name Matters
Even without accepting the Target allegation as proven, the appearance of xpl0itrs in the claim deserves attention.
Public reporting has associated the actor with initial-access activity and broader cybercrime operations. A recent cybersecurity report cited xpl0itrs among major sellers of North American access listings, while other public threat research has linked the actor to supply-chain compromises and activity involving TeamPCP.
That history makes claims involving the actor worth monitoring.
But reputation is not proof.
Security analysts should separate what is technically demonstrated from what is merely claimed by a threat actor or third-party account.
Retail Operations Create Enormous Pressure
A major retailer presents a fundamentally different attack surface from a healthcare technology provider.
Retail companies operate huge numbers of stores, endpoints, payment systems, corporate applications, logistics platforms, employee accounts, cloud services and third-party integrations.
When attackers disrupt retail infrastructure, the consequences can become visible very quickly.
Customers may encounter unavailable services. Employees may lose access to systems. Distribution can be interrupted. Internal communications can become complicated. Payment and ordering infrastructure can face additional scrutiny.
That operational pressure can give attackers additional leverage during extortion.
Ransomware Has Become an Access Business
Modern ransomware operations increasingly resemble a broader criminal ecosystem rather than a single malware campaign.
One group may obtain credentials.
Another may sell access.
Another may perform the intrusion.
Another may steal data.
Another may handle extortion.
This specialization allows attackers to scale their operations without every participant needing to develop every technical capability themselves.
The growing importance of access brokers is particularly relevant here. Public reporting has identified xpl0itrs among actors associated with North American initial-access listings.
That means defenders need to think beyond ransomware executables.
The first critical event may happen weeks before encryption ever begins.
The Real Battlefield Is Identity
Both cases point toward the same fundamental security problem: identity.
CareCloud’s incident involved unauthorized access to a cloud account.
Ransomware campaigns frequently begin with compromised credentials, stolen sessions, exposed secrets or abused legitimate accounts.
This makes identity protection one of the most important defensive priorities for organizations operating cloud infrastructure.
Multi-factor authentication, privileged-access management, short-lived credentials, conditional access policies, token protection and continuous monitoring are no longer optional extras for high-value environments.
They are core security controls.
Deep Analysis
Command 01 — Separate Confirmed Facts From Claims
The first command for cybersecurity readers is simple: classify every statement as confirmed, reported, alleged or unknown.
CareCloud’s March incident is supported by the company’s own regulatory disclosures.
The specific 3.7 million figure reported in the supplied material should still be treated carefully unless the corresponding notification or regulatory documentation independently confirms the exact number.
The Target incident, as presented here, remains an allegation.
Command 02 — Follow the Access Path
Security teams should investigate the identity that initially entered the environment.
Was the account compromised?
Was a token stolen?
Was a service credential exposed?
Was a privileged account abused?
Did an attacker bypass authentication?
These questions are often more valuable than simply searching for ransomware signatures.
Command 03 — Assume Data Theft Can Be Quiet
Organizations should not assume that a short outage means limited damage.
Data theft can occur without encryption.
An attacker can quietly copy information while leaving applications operational.
That makes outbound traffic monitoring, cloud audit logging, unusual API activity and abnormal identity behavior essential.
Command 04 — Protect High-Value Cloud Accounts
Cloud administrators should receive stronger protections than ordinary users.
Phishing-resistant MFA, privileged access controls, just-in-time administration and strict session policies can dramatically reduce the consequences of credential theft.
A single cloud account should never become an unrestricted master key.
Command 05 — Monitor Data Movement
Security teams should establish baselines for normal data movement.
Large transfers, unusual destinations, unexpected API calls and abnormal access patterns can reveal an attacker before destructive activity begins.
This is especially important for healthcare environments containing large volumes of protected information.
Command 06 — Treat Third Parties as Part of the Attack Surface
Healthcare and retail companies depend on enormous ecosystems of vendors.
Billing platforms, cloud providers, software suppliers, logistics companies, payment systems and contractors can all create additional paths into corporate environments.
Security assessments therefore need to include identity relationships and technical integrations, not merely vendor questionnaires.
Command 07 — Prepare for Extortion Before It Happens
Incident-response plans should assume that attackers may steal data even when they fail to deploy ransomware.
Organizations need predefined procedures for evidence preservation, legal review, customer communication, regulatory notification and executive decision-making.
Waiting until an extortion deadline arrives is a recipe for chaos.
Command 08 — Validate Threat-Actor Claims
Threat actors have an incentive to exaggerate.
Organizations should independently validate screenshots, samples, directory listings, timestamps, database structures and other evidence before accepting a public claim.
The same principle applies to cybersecurity news outlets.
Accuracy matters more than speed when reputations and patient privacy are involved.
Command 09 — Watch for Secondary Fraud
Healthcare breaches can generate secondary attacks.
Victims may later receive convincing phishing messages referencing medical providers, insurance information or billing activity.
Organizations should warn potentially affected individuals about impersonation attempts and suspicious communications.
Command 10 — Measure Recovery Beyond Uptime
A system being online does not necessarily mean the incident is over.
Recovery should include credential rotation, forensic validation, persistence hunting, data-loss assessment and monitoring for renewed attacker activity.
Operational recovery is only one part of cybersecurity recovery.
Command 11 — Build Detection Around Behavior
Traditional malware detection remains useful, but attackers increasingly abuse legitimate tools.
That makes behavioral detection increasingly important.
Security teams should look for impossible travel, unusual privilege escalation, abnormal cloud access, unexpected administrative activity and suspicious data transfers.
Command 12 — Protect the Blast Radius
Organizations should assume that one account will eventually be compromised.
The objective should therefore be limiting what happens next.
Network segmentation, least privilege, separate administrative identities and strong application boundaries can prevent a compromised account from becoming a company-wide disaster.
Command 13 — Healthcare Needs Special Protection
Healthcare organizations should treat electronic health record environments as crown-jewel infrastructure.
Access should be tightly controlled, extensively logged and continuously monitored.
Sensitive data should be encrypted and unnecessary access should be removed.
The potential scale of the CareCloud incident demonstrates why those controls matter.
Command 14 — Retail Needs Resilience
Retail security cannot focus exclusively on preventing intrusion.
Companies also need resilient operations.
If one system fails, stores and customers should still have carefully designed fallback procedures.
The objective is to prevent one compromised environment from becoming a nationwide operational event.
Command 15 — Cloud Security Must Be Continuous
Cloud environments change constantly.
New accounts appear.
Permissions change.
Applications are deployed.
Third-party integrations are added.
Secrets are created and sometimes forgotten.
Continuous monitoring is therefore more effective than an annual security review alone.
Command 16 — Identity Is the New Perimeter
The old model assumed that organizations could build a strong boundary around their network.
Modern infrastructure is far more distributed.
Employees work remotely.
Applications communicate through APIs.
Cloud services span multiple providers.
Contractors access systems from outside corporate networks.
Identity has therefore become one of the most important security boundaries.
Command 17 — Breach Notification Is Not the Finish Line
Sending notifications to affected individuals is necessary, but it does not end the security responsibility.
Organizations should continue monitoring affected environments and supporting victims.
They should also investigate why the initial controls failed.
Command 18 — Security Lessons Must Become Engineering Changes
A post-incident report has little value if it produces only recommendations.
Security findings should become concrete engineering tasks.
Weak authentication should be replaced.
Excessive permissions should be removed.
Logging gaps should be closed.
Unnecessary accounts should disappear.
Command 19 — Attackers Exploit Complexity
Large organizations often have thousands of interconnected systems.
Every integration creates another potential failure point.
The challenge is not simply securing individual applications.
It is understanding how those applications interact.
Command 20 — Visibility Determines Response Speed
The faster defenders understand what happened, the faster they can contain it.
Organizations should therefore prioritize centralized logging, endpoint telemetry, cloud visibility and identity monitoring.
Visibility is not glamorous.
But during an attack, it can be the difference between containment and catastrophe.
Command 21 — The CareCloud Case Is a Warning About Scale
The reported 3.7 million-person impact demonstrates how a single healthcare environment can potentially connect to an enormous population.
One compromised platform can therefore have consequences far beyond one company.
That is why healthcare technology providers should be treated as critical components of the broader healthcare ecosystem.
Command 22 — The Target Claim Shows the Other Side of the Equation
The Target allegation illustrates how attackers can pursue operational leverage.
If a retailer experiences meaningful disruption, the attacker may attempt to convert that disruption into pressure for payment.
That strategy is particularly effective when organizations lack tested continuity plans.
Command 23 — Attribution Requires Evidence
The name attached to an attack can attract headlines.
Technical evidence should attract analysts.
Organizations should avoid declaring attribution solely because a ransomware group or cybercrime actor claims responsibility.
Command 24 — Public Claims Should Trigger Investigation
At the same time, unverified claims should not simply be ignored.
A credible threat claim can provide an early warning.
Security teams should investigate internally while external researchers independently assess the available evidence.
Command 25 — Data Theft Can Be More Dangerous Than Encryption
Encrypted systems can often be restored from clean backups.
Stolen information cannot simply be restored.
Once sensitive data leaves an
Command 26 — Backup Strategy Still Matters
Ransomware defense requires resilient backups.
Backups should be isolated, tested and protected from attackers who compromise production credentials.
A backup that exists but cannot be trusted is not a reliable recovery strategy.
Command 27 — Incident Response Must Be Practiced
Organizations should conduct realistic tabletop exercises.
Executives, IT teams, legal departments, communications staff and security personnel need to understand their responsibilities before an incident occurs.
Command 28 — Security Insurance Is Not a Security Control
CareCloud disclosed that it believed its cybersecurity insurance coverage was likely sufficient for anticipated losses.
Insurance can help manage financial exposure.
It cannot restore stolen privacy, reverse reputational damage or eliminate regulatory obligations.
Command 29 — Patient Trust Is a Security Asset
Healthcare companies depend on trust.
Patients expect their medical information to remain private.
When that expectation is broken, the damage can extend beyond the immediate incident.
Security is therefore part of the patient relationship, not merely an IT function.
Command 30 — The Industry Should Expect More Cloud Incidents
As more healthcare and retail infrastructure moves into cloud environments, attackers will increasingly target cloud identities and configurations.
The shift does not make cloud inherently insecure.
It makes identity, configuration and monitoring increasingly important.
Command 31 — Attackers Follow Concentrated Value
Criminal groups naturally gravitate toward environments containing large quantities of valuable information.
Healthcare databases are attractive.
Retail infrastructure is attractive.
Cloud control planes are attractive.
Centralized systems create efficiency for legitimate organizations—and potentially for attackers.
Command 32 — Security Teams Need Threat Intelligence
Organizations should monitor threat intelligence for exposed credentials, access listings, stolen data claims and emerging campaigns.
Early warning can provide defenders with valuable time.
Command 33 — But Intelligence Must Be Verified
Threat intelligence is most useful when confidence levels are clearly documented.
A confirmed credential leak is different from an anonymous allegation.
A sample of real customer data is different from a screenshot.
A verified technical indicator is different from a social-media claim.
Command 34 — Regulators Are Increasingly Relevant
Large healthcare incidents can trigger obligations across multiple jurisdictions.
Organizations must understand notification requirements before an emergency occurs.
Legal and compliance teams should therefore be involved in incident-response planning.
Command 35 — Attack Surface Reduction Still Works
The simplest defense is often reducing unnecessary exposure.
Unused accounts should be removed.
Unused services should be disabled.
Excessive permissions should be eliminated.
Old credentials should be rotated.
The fewer doors an attacker can find, the fewer doors defenders must monitor.
Command 36 — Security Teams Should Assume Persistence
Attackers may attempt to maintain access after their initial intrusion.
Incident response should therefore include searches for persistence mechanisms and unauthorized accounts.
Command 37 — Eight Hours Should Never Define Severity
The CareCloud incident demonstrates why downtime is an inadequate measure of breach severity.
The operational outage was measured in hours.
The investigation, notifications and legal consequences can extend much further.
Command 38 — Ransomware Is Now an Ecosystem
The Target allegation fits into a larger environment in which access brokers, ransomware operators, data thieves and extortion groups can operate across overlapping networks.
That ecosystem makes defensive attribution and prevention more complicated.
Command 39 — The Biggest Risk Is Often Invisible
The most dangerous moment may occur before anyone realizes an attack is happening.
A stolen credential can sit unnoticed.
A cloud account can be abused quietly.
Sensitive data can leave an environment without immediately triggering an outage.
Detection must therefore focus on abnormal behavior, not just obvious destruction.
Command 40 — The Final Lesson Is Preparation
CareCloud and the alleged Target incident represent two different manifestations of the same modern cybersecurity problem.
Organizations must assume that attackers will seek identities, cloud access, sensitive information and operational leverage.
The strongest defense is not a single security product.
It is layered protection combined with visibility, rapid response, segmentation, resilient recovery and disciplined verification.
What Undercode Say:
The Bigger Pattern
The CareCloud incident is a powerful example of why cybersecurity reporting must look beyond the initial headline.
An eight-hour disruption sounds like an operational event.
A potential impact involving millions of people turns it into a major data-security story.
Healthcare Is Becoming a Prime Target
Healthcare technology platforms sit at the intersection of cloud infrastructure, sensitive personal information and highly interconnected organizations.
That combination creates extraordinary value for attackers.
Cloud Security Cannot Be Treated as Automatic Security
Moving data into AWS or another cloud provider does not automatically make that data secure.
Cloud providers secure the underlying infrastructure, while customers remain responsible for many aspects of identities, permissions, configurations and applications.
Identity Is the Critical Layer
The CareCloud disclosure specifically points toward unauthorized access to a cloud account.
That is exactly the kind of event security teams must design against.
The 3.7 Million Figure Deserves Careful Handling
The reported 3.7 million-person figure is enormous, but cybersecurity journalism should distinguish between a reported impact figure and independently verified facts.
The underlying incident itself is supported by
Target Requires Even More Caution
The Target ransomware story currently deserves an allegation label.
It should not be rewritten as a confirmed breach unless stronger evidence becomes available.
xpl0itrs Is Still Worth Watching
The
Public reporting has linked xpl0itrs to initial-access activity and broader supply-chain-related operations.
Attackers Are Monetizing Access
The growing market for stolen access means organizations may be compromised long before ransomware appears.
That changes the defensive timeline.
Data Theft Is a Strategic Weapon
Ransomware operators no longer need encryption alone to create pressure.
Stolen information can become the primary weapon.
Healthcare Data Has a Long Shelf Life
Medical information cannot simply be reset like a password.
That makes the consequences of healthcare breaches unusually persistent.
Retail Has a Different Pressure Point
Retail organizations are vulnerable to operational disruption because their systems are closely connected to customers, stores, logistics and payments.
Short Outages Can Create Long Crises
The duration of downtime is a poor indicator of the ultimate cost of an incident.
A company can restore operations while still facing years of investigation and litigation.
Verification Matters
Cybersecurity reporting has become increasingly dependent on rapid social-media information.
Speed is valuable, but accuracy is more valuable.
Threat Actors Want Attention
Attackers have incentives to exaggerate successful compromises.
That makes independent validation essential.
Companies Need to Assume Breach
Modern security should operate under the assumption that some credentials will eventually be compromised.
The objective becomes limiting what attackers can do after that point.
Segmentation Is Underrated
A compromised identity should not provide unrestricted access to every important system.
Segmentation limits blast radius.
Least Privilege Is Essential
Users and applications should receive only the permissions they actually need.
Every unnecessary permission increases potential damage.
MFA Must Be Strong
Multi-factor authentication remains important, but organizations handling high-value systems should increasingly prioritize phishing-resistant authentication methods.
Logging Needs to Be Actionable
Collecting enormous amounts of telemetry is not enough.
Security teams need the ability to identify abnormal identity activity and data movement quickly.
Incident Response Must Start Before the Incident
Organizations should know who makes decisions during a breach.
They should know how evidence will be preserved.
They should know how customers will be contacted.
Backups Protect Availability, Not Privacy
A clean backup can help restore encrypted systems.
It cannot recover data that has already been copied by an attacker.
Insurance Does Not Replace Security
Cyber insurance can reduce financial risk.
It cannot eliminate the consequences of lost customer trust.
Third Parties Need Continuous Monitoring
Vendor relationships can create pathways into critical environments.
Security assessments should therefore evolve as those relationships change.
Cloud Accounts Deserve Special Attention
Privileged cloud identities should be monitored more aggressively than ordinary accounts.
They represent potential control over enormous amounts of infrastructure.
Threat Intelligence Can Provide Early Warning
Dark-web monitoring and access-broker intelligence can sometimes reveal attacks before victims publicly acknowledge them.
But intelligence must be assigned confidence levels.
The Human Factor Remains Central
Credentials, authentication sessions and privileged accounts remain among the most valuable assets attackers pursue.
Technology alone cannot solve that problem.
Healthcare Needs a Higher Security Standard
The potential scale of the CareCloud incident reinforces the need for exceptional protection around electronic health record environments.
Retail Needs Resilience
Retailers must design systems so that a cyber incident does not automatically become a nationwide operational failure.
Attackers Are Becoming More Specialized
The modern cybercrime ecosystem allows different actors to specialize in access, intrusion, theft and extortion.
That specialization increases efficiency on the criminal side.
Defenders Must Specialize Too
Organizations increasingly need dedicated expertise across identity, cloud security, detection engineering, threat intelligence and incident response.
The Biggest Lesson
The biggest lesson from these two stories is not simply that companies can be hacked.
It is that attackers increasingly target the connections between systems.
The Future of Breach Defense
The strongest organizations will combine identity security, cloud monitoring, segmentation, data-loss controls, threat intelligence and rehearsed incident response.
Undercode’s Bottom Line
CareCloud’s confirmed security incident and the separate alleged Target ransomware event should not be treated as identical cases.
One is supported by corporate regulatory disclosures; the other remains a claim requiring further verification.
But both demonstrate the same strategic reality: attackers are increasingly hunting for access to the systems that organizations cannot afford to lose.
✅ CareCloud’s March 16, 2026 cybersecurity incident is supported by company regulatory disclosures, which state that one CareCloud Health EHR environment experienced approximately eight hours of disruption and that an unauthorized third party accessed a cloud account.
✅ CareCloud disclosed that patient-related information was exfiltrated, including personally identifiable information and protected health information, making this more than a simple service outage.
❌ The Target ransomware incident and its alleged connection to xpl0itrs should not be presented as independently confirmed based solely on the supplied social-media report. The claim requires corroboration from Target, investigators or reliable technical evidence.
Prediction
(+1) Healthcare organizations will increasingly strengthen cloud identity controls as incidents demonstrate that compromising a single cloud account can potentially expose enormous quantities of sensitive information.
(+1) Threat intelligence will become more important for early detection, particularly as access brokers and cybercrime groups increasingly advertise stolen credentials and corporate access.
(+1) Organizations will place greater emphasis on phishing-resistant authentication, least privilege and cloud monitoring rather than relying primarily on traditional perimeter defenses.
(-1) Data-breach consequences will continue to outlast the original intrusion, with investigations, notifications, lawsuits and reputational damage potentially continuing long after systems have been restored.
(-1) Unverified ransomware claims will continue to create confusion, especially as threat actors increasingly use public allegations as part of their extortion and reputation-building strategies.
(+1) The organizations that perform best in future attacks will not necessarily be those that prevent every intrusion, but those that detect unauthorized access quickly, contain the blast radius and maintain reliable recovery capabilities.
▶️ Related Video (68% 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.linkedin.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
