A Vulnerable Chain Gang, Maze Running, On the Job Training, Behind the Painted Smile, Too Much Enthusiasm, and Playing in the Big League. It's CISO Intelligence for Wednesday 26th March 2025.
Chinks in the chain, testing: a perpetual process, no training required, using deception for protection, a very big oops, and phishing in the big pool.
💡
"Gives me everything I need to be informed about a topic" - __UK.Gov__
Table of Contents
1. When Python Is Poisoned: How Runtime Security Stops the tj-Actions Attack
2. MAS Compliance Unmasked: Slaying the Regulation Dragon
3. Help Wanted: Bad Actors Apply Within
4. Mind Your Mask: Privacy Engineering's New Hero
5. Microsoft's Remote Desktop Snafu: Just Another Day at the Digital Office
6. A Sneaky Phish Just Grabbed my Mailchimp Mailing List
Sign up for CISO Intelligence.
21st century industry insights for the modern CISO
It won't hurt, I promise.
Email sent! Check your inbox to complete your signup.
No spam. Unsubscribe anytime.
When Python Is Poisoned: How Runtime Security Stops the tj-Actions Attack
_The modern twist on trusting noodles from a shady chef._
What You Need to Know
The widely-used GitHub Action `tj-actions/changed-files` was recently compromised, affecting over 23,000 development projects. This incident, tracked under CVE-2025-30066, highlights significant vulnerabilities in software supply chains. Executive boards need to understand the potential risk exposure and endorse the recommended security measures to protect against such attacks. It's crucial to evaluate current software dependencies and strengthen the organization’s supply chain security posture. Additionally, the board must ensure that resource allocation aligns with mitigating and managing these newfound vulnerabilities.
CISO Focus: Supply Chain Security
Sentiment: Strong Negative
Time to Impact: Immediate
*
The Dangerous Juice in CI/CD Pipelines
In a recent unsettling turn of events, software developers globally were jolted when the GitHub Action largely recognized as `tj-actions/changed-files` was compromised. This tool, an essential component of countless Continuous Integration and Continuous Delivery (CI/CD) pipelines, supports over 23,000 software projects. What unfolded was a calculated supply chain attack that laid bare the precarious nature of our reliance on software components' security.
The Vulnerability Unveiled
The crux of the matter lies in the exploitation of what was perceived as a trusted component, permeating through codebases all over the world. This breach wasn't just a minor blip; it peeled back the layers of latent vulnerabilities in software supply chains that many organizations heavily depend upon.
* Widespread Impact: A popular choice among developers, the compromised GitHub Action has been a staple tool in automating code changes, integrating critical software components effortlessly.
* Credential Exposure: The incident may have exposed sensitive credentials during the build processes, risking unauthorized access across critical systems and data platforms.
The Implications
Such attacks redefine the landscape of cyber threats, making it incumbent upon companies to overhaul their security frameworks. Here’s a snapshot of what organizations should prioritize:
* Robust Oversight: Continuous monitoring of CI/CD pipeline security is crucial. Having an active watch on integration tools ensures any anomalies are detected quickly.
* Supply Chain Vigilance: The importance of comprehensive vendor diligence and continuous evaluation of third-party software components is clear.
A Chain Reaction of Response
In light of the breach, the developer community and affected parties are advised to conduct immediate audits on their systems, especially focusing on build environments and related credentials.
* Secure Backdoors: Overhaul procedural checks on access permissions and logs related to `changed-files` usage.
* Automated Security Hurdles: Implement runtime security solutions capable of flagging suspicious activities in real-time during code compilation and deployment.
The sentiment surrounding this incident is decidedly strong negative, influenced heavily by the immediate and unforeseen threats introduced into operational pipelines. Given the instantaneous shockwaves felt across myriad projects utilizing `tj-actions/changed-files`, the time to impact is classified as immediate. This exemplifies the urgent need for increased security vigilance across all CI/CD operations, placing supply chain security at the CISO’s forefront.
As we navigate this precarious environment, it's imperative to remember that dependency can be dangerous. Trust, once granted, should always be validated and continually reevaluated. Be it in noodles or nodes, ensure the ingredients of your security practices are as clean as your conscience.
*
Vendor Diligence Questions
1. What measures do vendors have in place to secure their own development environments and prevent such compromises from affecting customers?
2. How frequently are security audits conducted for the software components they provide?
3. Can vendors provide a detailed incident response plan in the event a compromise occurs within their supply chain?
Action Plan
* Immediate Review: Conduct an immediate assessment of all projects using `tj-actions/changed-files`. Identify any signs of exploitation.
* Credential Rotation: Initiate a mandatory rotation of credentials for projects potentially affected to limit exposure.
* Security Enhancement: Work on enhancing pipeline security with additional layers of monitoring and error-reporting functionalities within CI/CD tools.
* Vendor Communication: Reach out to involved third parties for updates on their response and further guidance concerning the supply chain attack.
*
Source:When Python Is Poisoned - Sentinel One
*
MAS Compliance Unmasked: Slaying the Regulation Dragon
_Who knew compliance could be more enthralling than a novel?_
What You Need to Know
Financial institutions operating in Singapore must adhere to stringent regulations set by the Monetary Authority of Singapore (MAS). These rules ensure cybersecurity integrity and data protection while simultaneously fostering industry trust. Executives need to allocate budgets for ongoing compliance audits, train staff regularly, and invest in the latest cybersecurity technologies to remain compliant. Ignoring these regulations could result in hefty fines, reputational damage, or both.
CISO Focus: Compliance and Regulatory Security
Sentiment: Slightly Negative
Time to Impact: Immediate to Short Term
*
In the captivating world of financial compliance, the MAS regulations emerge as a necessary guardian, albeit a daunting one. The Monetary Authority of Singapore (MAS) requires diligence that has put financial institutions on high alert. It's akin to slaying a dragon, however, in this case, the dragon is a labyrinth of security protocols and legislative requisites.
Key Protocols of MAS Compliance
MAS regulations provide a robust framework aimed at maintaining the security and trustworthiness of financial institutions operating within Singapore. These include:
Technology Risk Management Guidelines (TRMG): This standard focuses on IT security practices, ensuring the protection of customer information against cyber threats.
Personal Data Protection Act (PDPA): As Singapore's definitive data protection legislation, PDPA governs the collection, use, and disclosure of personal data by organizations.
Cyber Hygiene Notice: Mandatory conditions emphasizing vulnerability assessments, data loss prevention, and incident response strategies.
The Implications of Non-Compliance
Ignoring MAS regulations isn’t just frowned upon—it's a surefire way to invite financial disaster and brand tarnishing. Organizations face penalties that range from fiscal fines to potential operational shutdowns. Moreover, non-compliance damages client trust and can erode a company's market position.
How Financial Institutions Can Stay Ahead
To remain compliant, institutions should implement these best practices:
Regular Audits and Assessments: Frequent compliance checks ensure any gaps are identified and rectified promptly.
Employee Training Programs: By fostering a security-informed culture, employees become the first line of defense in preventing cyber intrusions.
Invest in Technology: Utilizing updated cybersecurity tools and platforms is essential to match the evolving threat landscape.
Instituting these measures not only aligns with MAS standards but also fortifies the institution's reputation among clients and stakeholders alike.
A Future Proof Plan
The landscape for cyber regulations is continuously evolving. Not only must financial institutions meet current MAS guidelines, but they also need to anticipate future adjustments and potential new regulations. Engaging in proactive planning will render these potential changes executions rather than emergencies.
Quirky Take: A Treasured Compliance Embrace
Ultimately, the quest for MAS compliance in Singapore may seem like a formidable challenge, yet it's a critical part of maintaining a stable and trustworthy financial ecosystem. Joining rigorous regulations may feel like embracing a crocodile, but once acquainted, navigating becomes smoother.
In a world where regulatory compliance might seem a cumbersome task, viewing it as a catalyst for organizational fortitude changes the perspective entirely. When approached proactively, these regulations empower rather than restrain. For Singapore's financial institutions, riding the regulatory dragon is not just about survival—it's about thriving in a world where trust remains currency's truest form.
*
Vendor Diligence Questions
1. How does your solution align with current MAS Technology Risk Management Guidelines?
2. What measures do you have in place to ensure compliance with the Personal Data Protection Act?
3. Can you provide case studies or testimonials from other Singapore-based financial institutions?
Action Plan
1. Risk Assessment: Conduct a comprehensive evaluation of the current cybersecurity posture and identify gaps.
2. Training & Awareness: Roll out updated training sessions for all employees with a focus on regulatory compliance and phishing risks.
3. Technology Updates: Ensure all systems are current with the latest cybersecurity software and IT infrastructure meets MAS standards.
4. Incident Response Plan: Revamp and routinely test the breach response plan to guarantee swift action if an incident occurs.
5. Policy Review: Continuously review and update compliance policies to reflect any amendments in MAS regulations.
*
Sources:
[MAS Compliance 101: Key Regulations for Financial Institutions in Singapore](https://www.tripwire.com/state-of-security/mas-compliance-key-regulations-financial-institutions-singapore)
Research findings from the Monetary Authority of Singapore's official publications
Industry insights from data protection and regulatory experts
*
Help Wanted: Bad Actors Apply Within
_Now hiring: No skills necessary, Ransomware-as-a-Service will teach you (terms and conditions apply)_
What You Need to Know
The emergence of Ransomware-as-a-Service (RaaS) platforms represents a significant threat in the cybersecurity landscape. These platforms are democratizing cybercrime, allowing inexperienced individuals to launch ransomware attacks with relative ease. Executive management is advised to prioritize robust security strategies to combat this growing threat, emphasizing the need for investment in cybersecurity tools and training for staff awareness.
CISO focus: Emerging Threats in Ransomware
Sentiment: Negative
Time to Impact: Short (3-18 months)
*
In today's interconnected world, you can be a hacker without even understanding what code is. Welcome to the era of Ransomware-as-a-Service (RaaS), where cybercriminal activity has been streamlined for mass participation. With user-friendly interfaces and questionable ethics, anyone with a Wi-Fi signal can become a cyber menace overnight.
This piece draws attention to the sobering reality of growing democratization in cyber threats made possible by Ransomware-as-a-Service platforms. Security preparedness has never been more essential as new players join the game who lack professionalism but not intent.
Bridging the Gap: From Novice to Nuisance
Raas platforms have transformed the world of cybercrime, making sophisticated attacks available to the general public. These platforms function similar to legitimate SaaS businesses, where buyers pay for the service via subscription, a one-time payment, or a profit share.
* No Experience Required : These "plug-and-play" tools have removed the technical barriers traditionally associated with hacking, creating a surge of 'junk gun' ransomware attacks – low-level, unsophisticated disturbances that flood the market.
* Targeting the Vulnerable : Small businesses are now the favored targets due to their typically weaker cybersecurity measures. Often under-resourced and lacking in advanced security protocols, smaller enterprises are perfect prey for novice threat actors armed with Raas tools.
The Precarious New Normal
The democratization of ransomware not only emboldens novice hackers but also puts unprecedented pressure on cyber infrastructures globally. As the threat landscape continuously evolves, organizations are struggling to maintain defenses against a wide and unpredictable array of attackers.
* Proliferation of Attacks : The rise of affordable cybercrime tools has led to an uptick in ransomware incidents globally, forcing companies to reassess their security measures.
* Economic Impact : The cost implications for companies are enormous—ransom payments, system recovery, and reputational damage all add up significantly. Companies are implored to strengthen their cybersecurity frameworks to mitigate these potential costs.
DIY Cybercrime
Ransomware-as-a-Service not only democratizes cybercrime; it also commercializes it. Much like how platforms have changed other industries, RaaS puts a whole cyber-hacking arsenal into the hands of amateurs. It’s the gig economy, but for cybercrime—an assertion corroborated by cybersecurity experts who observe this surge in attacks.
* Lucrative ‘Business’ Models : The RaaS platforms operate with a business-like acumen, providing customer support and ensuring customer satisfaction—only it's criminals being served instead of customers.
* Future Projections : Unless measures are taken, the accessibility of these platforms will likely cause a long-term proliferation of cyber threats, particularly in ransomware.
Preparing for the Onslaught
Counteracting the threat posed by RaaS platforms requires a multi-faceted security strategy. Companies need to continuously adapt and upgrade their defenses, ensuring they are not caught off guard by these emerging threats.
* Invest in Proactive Security Measures : Equip IT teams with the tools needed to identify and dismantle threats before they impact your systems.
* Employee Training : Train staff to understand and recognize threats, enabling them to act as a first line of defense against potential breaches.
* Strong Cyber Hygiene Practices : Regularly update your cybersecurity protocols and software to protect against evolving threats.
*
Vendor Diligence Questions
1. Does your security software provider incorporate emerging threat intelligence specific to RaaS platforms?
2. How frequently does your vendor update their system to thwart ransomware developments?
3. Can your vendor provide demonstrable success in defending against low-grade ransomware attacks?
Action Plan
1. Conduct a Ransomware Readiness Assessment : Audit existing systems to identify vulnerabilities and potential entry points for attackers.
2. Upgrade Endpoint Protection : Implement advanced endpoint detection and response tools to manage any potential incursions effectively.
3. Security Training and Awareness Programs : Launch a comprehensive training program to instill a culture of vigilance and cybersecurity awareness across all organizational levels.
4. Establish a Response Protocol : Set up clear guidelines for an immediate and organized response to any detected ransomware threat, minimizing downtime and financial impact.
*
Source: Security.com
*
Mind Your Mask: Privacy Engineering's New Hero
_Data masking: Because snooping is so last season._
What You Need to Know
The cyber landscape is poised for a transformation that executives can't afford to ignore. As data breaches become more sophisticated, it's vital to implement measures that safeguard sensitive information. One approach that stands out is data masking, a technique that obscures private data by substituting it with fictitious yet convincing equivalents. Your leadership is critical in approving investments and ensuring policies focus on thorough data security, primarily through effective data masking practices. This board briefing demands your urgency in validating and solidifying data privacy strategies.
CISO focus: Data Privacy and Management
Sentiment: Positive
Time to Impact: Short (3-18 months)
*
Mask On: An Emphatic Introduction to Data Masking in Privacy Engineering
In a world where data is king, protecting private information has never been more crucial. Data masking, a potent tool in the cyber arsenal, has emerged as the unsung hero that can change the game. Just like donning a disguise, data masking replaces the original data with inauthentic yet realistic information, ensuring potential breaches result in an impenetrable wild goose chase.
What is Data Masking?
Data masking is the art of concealing sensitive data under layers of fictitious information, allowing organizations to maintain privacy while still utilizing the data for insights. This technique ensures that anyone without proper authorization remains clueless about underlying, sensitive details.
* Static Data Masking (SDM): Primarily used for offline databases or non-production environments, SDM ensures data is masked at rest. Once modified, the data remains in this masked state.
* Dynamic Data Masking (DDM): Functions on-the-fly and is applicable to production environments. With DDM, sensitive data is masked in real-time during text retrieval, allowing unauthorized users to see only scrambled data.
Why is Data Masking essential? Consider reports indicating that roughly 45% of organizations have experienced data breaches in the last five years due to unsecured databases (Source: Cybersecurity Ventures). Data masking steps in as a powerful yet simple way to mitigate such risks, ensuring compliance and protecting organizational reputation.
Data Masking vs. Data Encryption
While encryption aims to encode data to prevent unauthorized access, data masking focuses on creating a non-sensitive equivalent. Data masking's beauty lies in the fact that it needs no decryption, dodging complexities associated with exposing the data when accessing. This makes it a pragmatic choice for entities that require fast data processing without venturing into high-risk territories.
Benefits of Data Masking
1. Enhanced Privacy: By substituting sensitive data with false replicas, unauthorized users gain no actual insight.
2. Regulatory Compliance: Safeguarding data helps enterprises adhere to regulations like GDPR, CCPA, and more, evading hefty fines and legal troubles.
3. Data Utility for Testing and Development: Developers and testers can work with real-world scenarios without compromising actual sensitive information.
4. Reduced Risk of Breach Impact: If an intrusion does occur, attackers encounter non-valuable data, making the breach inconsequential in terms of sensitive loss.
Potential Pitfalls in the Data Masking Landscape
Although promising, data masking is not devoid of challenges. Implementation requires careful planning and constant alignment with evolving compliance mandates. Misconfigured masking might lead to vulnerabilities, underscoring the need for vigilance and expertise in its application.
A Call to Action
With innumerable organizations moving towards digitization, ignoring data privacy is an invitation to disaster. Data masking needs to be your frontrunner in combating data breaches. Not only is it a requisite for regulatory compliance, but it's also an investment in user trust and brand integrity.
So next time you're securing data, remember, nothing screams fashion-forward quite like a robust data mask. Keep those sensitive details on the down low and let the world chase shadows.
*
Vendor Diligence Questions
1. Does your solution support both Static and Dynamic Data Masking techniques?
2. How frequently are updates and audits conducted to ensure the solution aligns with latest compliance protocols?
3. What provisions do you offer for integration with existing organizational infrastructure?
Action Plan
1. Evaluate Current Data Handling Practices: Conduct a comprehensive audit of how data is managed and identify areas for improvement.
2. Implement Data Masking Solutions: Prioritize solutions offering robust Static and Dynamic Data Masking capabilities.
3. Training & Awareness: Educate organizational stakeholders and tech teams on the significance and deployment of masking techniques.
4. Continual Monitoring: Establish regular review sessions to confirm consistent compliance and adaptability to emerging threats.
*
Source: An Introduction to Data Masking in Privacy Engineering
*
Microsoft's Remote Desktop Snafu: Just Another Day at the Digital Office
_When updates break more things than they fix, and IT cries in binary._
What You Need to Know
Microsoft's latest Windows updates have caused disruptions with Remote Desktop services. As a result, users and IT departments worldwide are experiencing connectivity issues. Your immediate concern is to assess the impact on your organization and coordinate an update rollback or other mitigation strategies to ensure business continuity.
CISO Focus: Endpoint Security and Access Management
Sentiment: Negative
Time to Impact: Immediate
*
Following a set of recent updates, many users and organizations relying on Windows Remote Desktop for their remote work setups are encountering troubling connectivity issues. As we learn to navigate the ever-evolving landscape of cyber vulnerabilities, it seems our trusted partners can sometimes unwittingly become part of the problem rather than the solution.
Microsoft’s Unfortunate Update
In a classic case of unintended consequences, several Windows system updates released by Microsoft took a sledgehammer to Remote Desktop services used by countless businesses and individuals across the globe. Particularly on systems running Windows 11, users are noticing significant disruptions, leading to an outcry among IT professionals who see more fixing than thanking.
The Symptom Parade
Users are either completely unable to connect or experiencing intermittent connection drops.
Performance issues when connections are established — with lag that could rival your grandma's Internet speed.
In some cases, Remote Desktop simply refused to initialize properly.
Why It Matters
With remote work entrenched as a key component of modern business operations, any disruption in Remote Desktop services hits where it hurts most — the ability to connect safely and efficiently from anywhere.
For organizations managing sensitive data, these connectivity issues compound security concerns, as staff might resort to less secure methods to complete their tasks.
Mitigation Strategies
Before we collectively scream at our screens, there are actionable steps to alleviate these issues:
Rollback Offender Updates
Though this might feel like moving backwards, rolling back the updates is currently a primary troubleshooting step until Microsoft releases subsequent fixes.
Enable and Disable Workarounds
Tweaking Group Policy settings or registry entries related to Remote Desktop Services might temporarily mitigate issues.
Explore alternative remote access solutions as a stop-gap.
Communication is Key
Ensure users are informed about the issue and provide tips for workarounds while awaiting a more permanent fix. Communication prevents frustration from turning into chaos.
Beyond the Kerfuffle
While we eagerly await Microsoft's detailed communication and solution, organizations must consider long-term strategies:
Incremental Testing: Before committing to widespread updates, implement optimistic rollouts followed by rigorous in-the-wild testing to catch potential issues earlier.
Diversifying Remote Access: Re-evaluating reliance entirely on a single provider or solution helps build resilience against such hiccups.
*
Vendor Diligence Questions
What is your track record in update reliability and incident resolution concerning remote services?
How do you handle regression testing, and what steps are taken to ensure previous functionalities remain intact?
How do you communicate urgent patches or workarounds to global users efficiently and accurately?
Action Plan
1. Impact Assessment: Task your IT team to determine which areas and personnel are most affected by the issues. Prioritize teams that require immediate solutions.
2. Coordinate Rollback: Identify the updates linked to the problems and execute rollbacks where feasible, following best practices to minimize data disruption.
3. Implement Workarounds: Advise on practical solutions involving registry or policy changes that are well documented.
4. Enhance Security Posture: Deploy secondary access solutions on critical systems to prevent downtime.
5. Monitor Vendor Communications: Keep tabs on Microsoft updates and advisories for new patches addressing the problems.
*
Sources:
[Microsoft: Recent Windows updates cause Remote Desktop issues](https://www.bleepingcomputer.com/news/microsoft/microsoft-recent-windows-updates-cause-remote-desktop-issues/)
_Further information extrapolated from industry best practices and IT forums._
*
A Sneaky Phish Just Grabbed my Mailchimp Mailing List
_When phishers come knocking, it's your data they're shocking!_
What You Need to Know
A recent and formidable phishing attack has compromised the integrity of the popular email marketing platform, Mailchimp. This cyber intrusion has resulted in unauthorized access to mailing lists stored by users, leading to potential data breaches across numerous businesses. It is crucial for board members and executive management to understand the gravity of the situation and actively participate in crafting robust security protocols to protect client and company data. Immediate action to tighten security measures is expected for prevention and damage control.
CISO focus: Phishing prevention and response
Sentiment: Strong Negative
Time to Impact: Immediate
*
Phishing attacks continue to evolve in sophistication, and now it seems that phishers have set their sights on the email giant, Mailchimp. A cunning phishing breach has potentially handed sensitive mailing lists over to cybercriminals, leaving businesses scurrying to mitigate the possible fallout.
The Anatomy of a Breach
It all began with a typical day at Mailchimp, until the occurrence of an unsettling noticeable spike in complaints regarding unauthorized access to mailing lists. As detailed by DataBreaches.net, cybercriminals employed a deceptive and strategically targeted phishing scheme, which effectively ensnared several unsuspecting employees and clients. With crisp impersonation techniques, phishers misled targets into relinquishing credentials, allowing unauthorized access to select mailing lists.
Immediate Risks and Implications
Data Exposure : The primary risk involves sensitive data exposure potentially leading to customer distrust and reputational damage.
Identity Theft : Mailing list access might facilitate further phishing projects or identity theft attempts, multiplying potential breaches.
Regulatory Scrutiny : Post-breach, companies could face significant regulatory repercussions if data protection laws are found to be inadequately addressed.
Withstanding the Impact
Organizations using Mailchimp's services should immediately implement enhanced email security protocols. Engaging in comprehensive user awareness training that focuses on recognizing phishing attempts can reduce risk. Security teams should ramp up monitoring of mailing activities and be on the alert for any abnormal access patterns or signs of tampering in their digital correspondence structures.
Lessons and Precautionary Measures
The Mailchimp breach serves as a stark reminder of the potency of phishing attacks in today's digital landscape. Here's what organizations can consider moving forward:
1. Revisit Authentication Methods : Multi-factor authentication (MFA) should be mandatory to mitigate unauthorized access even if credentials are compromised.
2. Regular Penetration Testing : Conduct periodic tests to evaluate the network's resilience against phishing and general security breaches.
3. Data Encryption : Ensure mailing lists and sensitive data remain encrypted during storage and transit to minimize damage even if accessed.
4. Incident Response Team : Establish a dedicated incident response team ready to act quickly should another breach occur.
Tailor-Made Defense
According to Cybersecurity & Infrastructure Security Agency (CISA), businesses should employ user education programs, simulate phishing attacks to measure employee responses, and use AI-driven solutions to detect phishing attempts.
While the digital waters still ripple from this phishing breach, Mailchimp users must seize the initiative, shore up their defenses, and navigate with caution lest they become the next catch of the day.
*
Vendor Diligence Questions
1. What measures is Mailchimp implementing to strengthen its authentication mechanisms against phishing scams?
2. How frequently does Mailchimp perform penetration tests and security audits to identify vulnerabilities?
3. What advancements has Mailchimp made in their breach notification process to ensure timely and efficient communication?
Action Plan
1. Conduct an immediate internal audit of Mailchimp-related mailing activities to identify unusual access.
2. Update and enforce company-wide cybersecurity policies focusing on phishing defense.
3. Implement bi-weekly phishing simulation exercises and workshops to continuously educate employees.
4. Allocate resources towards upgrading to more sophisticated security software capable of detecting and neutralizing phishing threats.
*
Source: A Sneaky Phish Just Grabbed my Mailchimp Mailing List
*
_CISO Intelligence is lovingly curated from open source intelligence newsfeeds and is aimed at helping cybersecurity professionals be better, no matter what their stage in their career._
_We’re a small startup, and your subscription and recommendation to others is really important to us._
*Thank you so much for your support!(