Listen to this Post
A New Wave of Ransomware Claims Raises Fresh Questions About Corporate Security
Ransomware activity rarely arrives as a single isolated event. Instead, new victim claims can appear across underground channels and threat-intelligence monitoring platforms with little warning, leaving organizations, customers, partners, and security teams trying to determine what actually happened. On August 9, 2026, two separate ransomware-related claims drew attention after the ThreatMon Threat Intelligence Team reported that the Qilin and Play ransomware groups had allegedly added new organizations to their victim lists.
The organizations named in the reports are ENERGETIC DEVELOPMENT CORP, allegedly associated with Qilin, and Marconi Industrial Services, allegedly associated with Play. The reports appeared within a short period of each other, creating another reminder of how active the ransomware ecosystem remains and how quickly threat actors can move from intrusion to public pressure.
At this stage, however, the available information should be treated as ransomware claims rather than independently confirmed breaches. A victim appearing on a ransomware group’s alleged list does not automatically prove that an intrusion occurred, that data was stolen, or that the attackers successfully encrypted systems.
What Happened on August 9, 2026?
According to the ThreatMon Threat Intelligence Team, dark-web ransomware activity indicated that the Qilin ransomware operation had added ENERGETIC DEVELOPMENT CORP to its alleged victim list.
The report was timestamped August 9, 2026, at 23:08:25 UTC+3, placing the observation on the same day as the publication of the alert.
The second report involved the Play ransomware group, which allegedly added Marconi Industrial Services to its victim list. ThreatMon listed this activity at 21:56:25 UTC+3 on August 9, 2026.
The two reports therefore appeared only a little more than an hour apart, highlighting how multiple ransomware operations can simultaneously maintain pressure against organizations in different industries.
Qilin Is Once Again Drawing Attention
Qilin has become one of the most closely watched ransomware operations because of its aggressive victim targeting and its use of a ransomware-as-a-service model.
Rather than depending on a single centralized group to conduct every intrusion, ransomware-as-a-service operations can involve affiliates responsible for gaining access to organizations, stealing information, deploying malware, and negotiating with victims.
This structure makes the ecosystem difficult to disrupt.
Even when infrastructure associated with one operation is taken offline, affiliates, access brokers, cryptocurrency channels, leak sites, and other supporting services can potentially continue operating or migrate to new platforms.
The ENERGETIC DEVELOPMENT CORP Claim
The latest ThreatMon report specifically identifies ENERGETIC DEVELOPMENT CORP as an alleged Qilin victim.
The report itself does not provide enough information to establish the initial access method, the systems allegedly compromised, the volume of data supposedly stolen, or whether ransomware encryption actually occurred.
Those details are important.
A ransomware
Play Ransomware Appears in a Separate Claim
The second incident involves Marconi Industrial Services, which ThreatMon reported as an alleged victim of the Play ransomware group.
Play, also known as PlayCrypt in some security research, has established itself as another significant ransomware threat. Its operations have historically focused on gaining access to organizational networks, moving laterally, collecting sensitive information, and applying pressure through data theft and encryption.
The appearance of Marconi Industrial Services on an alleged victim list therefore deserves attention, but it should not be interpreted as confirmation that the organization suffered a complete network compromise.
Why the Two Reports Matter
The importance of these reports extends beyond the names of the two organizations.
Qilin and Play represent two mature ransomware ecosystems capable of operating at scale. When organizations appear in monitoring reports associated with these groups, security teams should pay attention even before every technical detail becomes public.
Ransomware incidents frequently develop in stages.
An attacker may first obtain credentials, establish persistence, move laterally, identify valuable systems, locate backups, collect sensitive files, and only later deploy encryption or begin extortion.
That means the public appearance of a victim name can occur after weeks or months of malicious activity inside a network.
A Victim Listing Is Not the Same as Proof
One of the most important distinctions in ransomware reporting is the difference between a claim and a confirmed incident.
Threat actors have repeatedly published victim names as part of extortion campaigns. Some claims are eventually confirmed by the affected organization, security researchers, regulators, or forensic investigations.
Others remain unverified.
There can also be cases in which attackers exaggerate the impact of an intrusion or publish an organization’s name after obtaining only limited access.
For that reason, responsible reporting should use language such as “allegedly,” “claimed,” and “reported” until independent evidence becomes available.
What Could Have Happened Inside the Networks?
If the Qilin and Play claims are legitimate, the underlying attacks could involve several stages.
The attackers may have acquired valid credentials through phishing, credential theft, password reuse, infostealer infections, compromised remote-access services, or previously purchased access.
Once inside, they could attempt privilege escalation and reconnaissance.
The next stage could involve lateral movement through Active Directory environments, endpoint compromise, remote administration tools, or exploitation of exposed services.
The attackers may then identify file servers, databases, backups, cloud resources, and other systems containing information that can be monetized.
Data Theft Has Become Central to Ransomware
Modern ransomware is no longer simply about encrypting files.
Many major groups use double extortion, in which attackers steal sensitive information before encrypting systems or threatening to publish the stolen data.
This strategy gives attackers a second source of leverage.
Even if an organization has reliable backups and can restore its infrastructure, the threat of public disclosure may remain.
For businesses, that can create regulatory, legal, financial, contractual, and reputational consequences.
Why Industrial Organizations Remain Attractive Targets
The involvement of an industrial-services organization such as Marconi Industrial Services is particularly relevant because industrial businesses can contain valuable operational information alongside traditional corporate data.
Engineering documents, contracts, supplier records, employee information, project files, financial data, and operational documentation can all have significant value.
Attackers do not necessarily need to disrupt physical operations to make an intrusion profitable.
Stealing business information alone can create significant extortion leverage.
The Operational Risk Is Larger Than Encryption
A ransomware incident can affect more than computers and file servers.
Organizations may lose access to email, enterprise applications, accounting systems, project-management platforms, customer records, authentication infrastructure, file-sharing systems, and communication tools.
In industrial environments, interruptions can also affect scheduling, procurement, logistics, production planning, maintenance, and supplier relationships.
The resulting cost can therefore exceed the ransom demand itself.
The Human Element Remains Critical
Despite increasingly sophisticated ransomware infrastructure, attackers still frequently depend on human mistakes.
A stolen password, reused credential, malicious attachment, fraudulent login page, compromised browser session, or unauthorized remote-access connection can provide the initial foothold.
This makes employee security awareness an important part of ransomware defense.
Technical controls are essential, but they cannot compensate for every compromised credential or successful social-engineering attack.
Deep Analysis: What the Qilin and Play Claims Reveal
Command 01 — Treat the Victim Lists as Signals
Security teams should treat ransomware victim-list appearances as early-warning intelligence rather than automatically labeling them confirmed breaches.
A claim can justify investigation even when it cannot yet justify a definitive public statement.
Command 02 — Validate the
Organizations named in ransomware reports should immediately review externally exposed systems.
Remote desktop services, VPN infrastructure, authentication portals, management interfaces, cloud applications, and other internet-facing assets should be checked for unusual activity.
The objective is to determine whether suspicious access occurred before assuming that the ransomware claim is either true or false.
Command 03 — Hunt for Compromised Credentials
Credential abuse remains one of the most dangerous pathways into enterprise networks.
Security teams should investigate unusual authentication events, impossible-travel patterns, abnormal login locations, privilege escalation, new administrative accounts, and suspicious access to sensitive applications.
Password resets should be prioritized when there is credible evidence of credential compromise.
Command 04 — Inspect Privileged Accounts
Privileged accounts can provide attackers with enormous control over enterprise environments.
Investigators should examine recently created administrator accounts, unexpected group-membership changes, privilege escalations, and unusual administrative sessions.
Any unexplained administrative activity deserves immediate investigation.
Command 05 — Examine Endpoint Telemetry
Endpoint detection and response platforms can provide valuable evidence about ransomware activity.
Security teams should search for suspicious command execution, credential dumping behavior, unauthorized remote-management tools, archive creation, unusual PowerShell activity, lateral movement, and processes interacting with large numbers of files.
Command 06 — Search for Data Exfiltration
If the ransomware claim involves data theft, network telemetry becomes particularly important.
Large outbound transfers, unusual cloud-storage activity, archive creation, unexpected encrypted connections, and abnormal traffic to unfamiliar infrastructure can help determine whether sensitive information may have been removed from the environment.
Command 07 — Protect the Backups
Backups are among the most valuable defensive assets during ransomware incidents.
Organizations should verify that backups are available, protected from unauthorized deletion, isolated from ordinary administrative credentials, and capable of successful restoration.
A backup that exists but cannot be restored is not an effective ransomware recovery strategy.
Command 08 — Investigate Lateral Movement
Attackers rarely stop at the first compromised machine.
Security teams should examine remote logins, SMB activity, administrative shares, authentication events, remote services, domain-controller access, and unusual connections between internal systems.
The goal is to determine how far an attacker may have traveled.
Command 09 — Monitor the Dark Web Carefully
Dark-web monitoring can provide useful early indicators, particularly when ransomware groups publish victim names or samples of allegedly stolen information.
However, dark-web intelligence must be corroborated.
A screenshot or victim listing alone does not establish the scale or validity of a compromise.
Command 10 — Separate Facts From Claims
The strongest incident reports clearly distinguish between what has been observed, what has been reported by third parties, and what has been independently confirmed.
This distinction protects organizations from unnecessary panic while preserving the urgency required for legitimate investigations.
Command 11 — Expect Extortion Pressure
If the claims are legitimate, organizations may face additional pressure through countdown timers, sample files, public allegations, direct communications, or threats against customers and partners.
Incident-response teams should prepare for these tactics before attackers escalate them.
Command 12 — Protect Customer and Employee Data
When a suspected breach involves personal information, organizations should immediately identify which databases and systems could contain sensitive records.
The investigation should determine whether employee information, customer records, financial details, credentials, intellectual property, or contractual documents may have been accessed.
Command 13 — Review Cloud Environments
Ransomware investigations should no longer focus exclusively on traditional on-premises infrastructure.
Cloud storage, identity providers, SaaS platforms, collaboration systems, APIs, and cloud-hosted databases can all become targets.
Compromised cloud credentials may allow attackers to access information without deploying traditional ransomware.
Command 14 — Examine Security-Control Changes
Attackers frequently attempt to weaken defenses after gaining privileged access.
Investigators should look for disabled security software, altered firewall policies, modified logging configurations, suspicious exclusion rules, newly trusted applications, and unusual changes to identity-security policies.
Command 15 — Assume Attackers May Have Persistence
Removing visible ransomware does not necessarily remove the attacker.
Threat actors may create scheduled tasks, new accounts, remote-access mechanisms, malicious services, web shells, stolen authentication tokens, or other persistence mechanisms.
A complete investigation should therefore look for mechanisms that could allow attackers to return.
Command 16 — Preserve Evidence
Organizations should preserve relevant logs, endpoint images, authentication records, firewall data, cloud audit logs, email evidence, and suspicious files.
Evidence can become essential for determining the attack timeline and supporting regulatory, legal, insurance, or law-enforcement investigations.
Command 17 — Map the Attack Timeline
A useful investigation should establish when the attacker first entered the environment, how they escalated privileges, what systems they accessed, what information they collected, and when the final destructive or extortion activity occurred.
A timeline can reveal weaknesses that may otherwise remain hidden.
Command 18 — Identify the Initial Access Vector
Understanding the initial access method is one of the most important outcomes of a ransomware investigation.
If attackers entered through stolen credentials, the organization must address identity security.
If they exploited a vulnerability, patching and exposure management become priorities.
If phishing was involved, email security and authentication controls require additional attention.
Command 19 — Strengthen Multifactor Authentication
Multifactor authentication can substantially reduce the usefulness of stolen passwords.
Organizations should prioritize phishing-resistant authentication for privileged accounts and externally exposed services whenever possible.
Command 20 — Reduce Unnecessary Exposure
Every internet-facing service increases the
Organizations should continuously identify systems exposed to the internet and remove unnecessary services.
Systems that do not need to be publicly reachable should not remain publicly reachable.
Command 21 — Monitor for Encryption Behavior
Modern security tools can detect unusual file-encryption patterns.
Sudden mass modification of files, suspicious extensions, rapid file renaming, and unusual access to network shares can provide valuable signals before ransomware spreads across an entire environment.
Command 22 — Segment Critical Systems
Network segmentation can limit the blast radius of an intrusion.
If attackers compromise one workstation, they should not automatically be able to reach every server, backup repository, database, and administrative system.
Segmentation can turn a potentially catastrophic incident into a more manageable containment event.
Command 23 — Test Recovery Procedures
Recovery plans should be tested before an incident occurs.
Organizations should conduct realistic exercises that answer difficult questions: How quickly can critical systems return? Who approves restoration? Which systems come first? Can backups be trusted? How will employees communicate if corporate systems are unavailable?
Command 24 — Prepare a Communications Strategy
Ransomware incidents create communication challenges.
Organizations need clear procedures for communicating with employees, customers, suppliers, regulators, insurers, legal counsel, and law enforcement.
Poor communication can amplify the damage caused by the original intrusion.
Command 25 — Watch for Secondary Attacks
A ransomware incident can attract additional attackers.
Once an organization becomes known as a compromised target, stolen credentials and leaked information may circulate among other criminal groups.
Defenders should therefore remain vigilant even after the initial incident appears to be contained.
Command 26 — Do Not Ignore Small Indicators
A suspicious login may appear insignificant by itself.
A newly created account may also look harmless.
An unusual archive may not immediately appear malicious.
But when these events occur together, they can form a clear attack pattern.
Command 27 — Understand the Economics
Ransomware survives because it remains financially attractive.
Attackers can monetize stolen data, encryption, access brokerage, extortion, and sometimes the resale of compromised credentials.
As long as the economics remain favorable, criminal groups have incentives to continue developing their operations.
Command 28 — Watch the Affiliate Ecosystem
Qilin and Play should not be viewed simply as pieces of malware.
They are parts of broader criminal ecosystems involving affiliates, initial-access brokers, infrastructure providers, negotiators, cryptocurrency services, and data-leak platforms.
Disrupting one component does not necessarily eliminate the entire ecosystem.
Command 29 — Expect Tactics to Evolve
Ransomware groups continuously adjust their methods.
As organizations improve endpoint protection, attackers may shift toward identity compromise, cloud environments, virtualization platforms, remote-management software, and third-party access.
The defensive strategy must evolve at the same pace.
Command 30 — Do Not Confuse Silence With Safety
An organization that has not appeared on a ransomware leak site is not necessarily safe.
Many intrusions remain undiscovered for weeks or months.
Threat actors can maintain access without immediately publishing a victim’s name.
Command 31 — Use Threat Intelligence Correctly
Threat intelligence becomes valuable when it drives action.
A ransomware report should trigger appropriate investigation, monitoring, and validation rather than simply being reposted as confirmed news.
The best security teams turn intelligence into measurable defensive activity.
Command 32 — Investigate Before Making Public Statements
Organizations facing an allegation should avoid making premature claims about what happened.
An initial statement may acknowledge awareness of an allegation while investigators determine whether unauthorized access occurred.
This approach preserves credibility and leaves room for evidence-based updates.
Command 33 — Evaluate Third-Party Risk
A ransomware intrusion can originate outside an
Suppliers, contractors, managed-service providers, software vendors, and remote-access partners can create indirect attack paths.
Security programs should therefore examine trusted connections rather than treating the internal network as an isolated environment.
Command 34 — Prioritize Identity Security
The modern enterprise perimeter is increasingly centered around identity.
Strong authentication, privileged-access management, conditional access, session monitoring, and rapid credential revocation can dramatically reduce the impact of stolen credentials.
Command 35 — Build an Incident-Response Muscle
Incident response should not begin when ransomware appears.
Organizations should regularly conduct tabletop exercises and technical simulations involving credential theft, data exfiltration, ransomware deployment, cloud compromise, and backup destruction.
Prepared teams respond faster.
Command 36 — Measure Detection Speed
One of the most important ransomware metrics is not simply whether an organization eventually detects an attack.
It is how long attackers remain inside the environment before detection.
Reducing attacker dwell time can prevent data theft, privilege escalation, and large-scale encryption.
Command 37 — Assume Data May Be the Real Prize
Encryption creates operational disruption, but stolen information creates long-term leverage.
For this reason, organizations should treat sensitive data repositories as high-value security assets and apply strong access controls, monitoring, encryption, and segmentation.
Command 38 — Follow the Evidence
The most reliable conclusion will come from technical evidence rather than the victim-list entry itself.
For ENERGETIC DEVELOPMENT CORP and Marconi Industrial Services, future confirmation could come from the organizations themselves, security researchers, regulators, forensic investigations, or credible evidence published by the attackers.
Command 39 — Keep the Claims in Perspective
The two August 9 reports are significant threat-intelligence indicators, but they should not automatically be interpreted as proof of successful ransomware deployment.
That distinction is especially important for readers who may encounter the claims through social media without seeing the original context.
Command 40 — The Bigger Warning
The larger message from these incidents is straightforward: ransomware remains a persistent business risk.
Qilin and Play do not need to compromise every organization to demonstrate their impact.
A handful of successful attacks can generate enormous financial pressure, while the constant threat of exposure forces organizations to invest in prevention, detection, response, and recovery.
What Undercode Say:
Ransomware Has Become a Continuous Threat
The latest Qilin and Play claims demonstrate how ransomware has evolved from occasional malware outbreaks into a continuous criminal business model.
Claims Can Still Be Valuable Intelligence
Even an unverified victim-list entry can provide defenders with a reason to investigate authentication logs, endpoint telemetry, cloud activity, and network traffic.
Verification Must Come First
The names of ENERGETIC DEVELOPMENT CORP and Marconi Industrial Services should currently be described as alleged victims based on the available report.
Social Media Accelerates the Story
A ransomware claim can spread around the internet within minutes, long before investigators have enough evidence to determine what actually happened.
Headlines Can Create Unnecessary Panic
Calling every victim-list appearance a confirmed breach risks confusing readers and damaging organizations that may still be investigating.
Qilin Remains a Serious Threat
The continued appearance of Qilin-related claims shows why defenders should continue tracking the group’s infrastructure, techniques, and affiliate ecosystem.
Play Remains Relevant
The separate Play claim demonstrates that ransomware activity is not concentrated around one criminal operation.
Multiple Groups Mean Multiple Attack Paths
Defenders cannot build a strategy around blocking one ransomware family.
Identity Is Becoming the New Battlefield
Stolen credentials can give attackers access to systems without requiring traditional malware to be installed immediately.
Remote Access Remains Dangerous
VPNs, remote-management tools, exposed administration interfaces, and other access technologies remain attractive targets.
Data Exfiltration Changes the Equation
Organizations can recover encrypted systems, but they cannot easily recover confidential information once attackers have copied it.
Backups Are Not Enough
A company with excellent backups can still face extortion if attackers successfully steal sensitive data.
Segmentation Can Limit Damage
Separating critical systems can prevent a compromised endpoint from becoming a gateway into the entire organization.
Detection Speed Matters
The earlier defenders identify suspicious activity, the less time attackers have to escalate privileges and steal information.
Ransomware Investigations Need Patience
A credible investigation may take days or weeks because forensic teams need to reconstruct what happened rather than simply react to a public allegation.
Dark-Web Intelligence Has Limits
Threat-intelligence monitoring is useful, but it should be treated as one source of evidence rather than an unquestionable source of truth.
Threat Actors Have Incentives to Create Pressure
Publishing a victim name can be part of an extortion strategy designed to force an organization into negotiations.
Public Pressure Is Part of the Attack
The leak site, social-media posts, and media coverage can all become components of the criminal pressure campaign.
Businesses Need Prepared Communication
Organizations should know in advance how they will communicate during a ransomware crisis.
Customers Can Become Part of the Impact
If stolen information belongs to customers, partners, or employees, the incident can extend well beyond the compromised company.
Industrial Companies Have Valuable Data
Engineering documents, contracts, project information, supplier records, and operational systems can all become targets.
The Cloud Is Not Outside the Threat Model
Cloud accounts and SaaS platforms must be included in ransomware investigations and defensive planning.
Privileged Accounts Deserve Special Protection
A compromised administrator account can turn a limited intrusion into an enterprise-wide emergency.
Multifactor Authentication Is Essential
Strong authentication reduces the value of stolen passwords and can stop entire classes of attacks.
Phishing Remains Dangerous
Sophisticated ransomware operations do not necessarily need sophisticated initial access when employees can be tricked into surrendering credentials.
Third-Party Access Matters
Attackers can exploit trusted suppliers and service providers to bypass traditional perimeter defenses.
Ransomware Is an Ecosystem
The criminals behind an attack may rely on separate specialists for access, malware, infrastructure, negotiation, and monetization.
Removing Malware Does Not End an Incident
Attackers may leave behind persistence mechanisms that allow them to return after defenders believe the environment is clean.
Evidence Must Drive Conclusions
The strongest reporting separates confirmed facts from allegations, assumptions, and predictions.
The August 9 Claims Are a Warning
Even without independent confirmation, the Qilin and Play reports should remind organizations that ransomware remains active and adaptive.
The Real Question Is Not Who Is Next
The more important question is whether organizations are prepared to detect and contain an attacker before that attacker can turn network access into a full-scale crisis.
✅ Qilin Victim Claim Was Reported
ThreatMon reported on August 9, 2026, that Qilin had added ENERGETIC DEVELOPMENT CORP to its alleged victim list. This confirms that the claim was reported by the cited threat-intelligence source, but it does not independently confirm the underlying breach.
✅ Play Victim Claim Was Reported
ThreatMon separately reported that Play had added Marconi Industrial Services to its alleged victim list. The report establishes the existence of the threat-intelligence observation, while the actual compromise remains subject to independent verification.
❌ Successful Breach and Data Theft Are Not Confirmed
The supplied information does not establish how either organization was allegedly compromised, whether systems were encrypted, how much data may have been stolen, or whether the claims have been independently confirmed by the organizations or forensic investigators.
Prediction
(-1) More Ransomware Victim Claims Are Likely
The ransomware ecosystem is unlikely to slow significantly in the near term. Qilin, Play, and other established operations are expected to continue publishing alleged victims as they pursue new extortion opportunities.
(-1) Extortion Pressure Will Increase
Attackers are likely to rely increasingly on stolen data, public leak threats, and reputational pressure rather than encryption alone.
(-1) Industrial Organizations Will Remain Attractive Targets
Companies connected to engineering, manufacturing, infrastructure, logistics, and industrial services hold valuable operational and commercial information, making them attractive targets for financially motivated attackers.
(+1) Strong Identity Controls Can Reduce Exposure
Organizations that deploy phishing-resistant multifactor authentication, privileged-access controls, segmentation, continuous monitoring, and well-tested recovery procedures will be in a stronger position to contain ransomware activity.
(+1) Better Threat Intelligence Can Improve Early Detection
Monitoring ransomware infrastructure and victim claims can provide defenders with useful warning signals when combined with internal telemetry and forensic investigation.
(-1) The Ransomware Economy Will Continue Adapting
Even if individual ransomware groups disappear, affiliates and access brokers can migrate toward other operations. The broader criminal ecosystem is therefore likely to remain resilient.
(+1) Preparation Can Change the Outcome
The most important prediction is also the most actionable: organizations that prepare before an attack are far more likely to detect suspicious activity early, contain the intrusion, restore critical operations, and reduce the leverage available to attackers.
Final Assessment
Two Claims, One Larger Warning
The August 9 reports involving ENERGETIC DEVELOPMENT CORP and Marconi Industrial Services should currently be understood as ransomware victim claims reported through threat-intelligence monitoring, not as independently verified breaches.
Nevertheless, the reports are worth watching.
The simultaneous appearance of Qilin and Play in fresh victim allegations illustrates the broader reality facing businesses in 2026: ransomware remains organized, commercially motivated, adaptive, and capable of creating pressure long before the public understands the full scope of an incident.
For organizations potentially affected, the priority should not be panic or speculation. It should be evidence.
Review authentication activity. Examine endpoint telemetry. Check privileged accounts. Investigate unusual outbound transfers. Validate backups. Search for persistence. Preserve forensic evidence. And most importantly, determine whether an attacker actually gained access.
Because in modern ransomware incidents, the first public claim may be only the beginning of the story.
▶️ Related Video (70% 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
