company logo

Product

Our Product

We are Reshaping the way Developers find and fix vulnerabilities before they get exploited.

Solutions

By Industry

BFSI

Healthcare

Education

IT & Telecom

Government

By Role

CISO/CTO

DevOps Engineer

Resources

Resource Library

Get actionable insight straight from our threat Intel lab to keep you informed about the ever-changing Threat landscape.

Subscribe to Our Weekly Threat Digest

Company

Contact Us

Have queries, feedback or prospects? Get in touch and we shall be with you shortly.

loading..
loading..
loading..
Loading...

Data Breach

Toyota

Vulnerability

loading..
loading..
loading..

14,000 Toyota Users Exposed to Cyberattack Via GSPIMS Security Breach!

Toyota's Global Supplier Preparation Information Management System (GSPIMS) was breached by a security researcher who responsibly reported the issue to the comp...

07-Feb-2023
3 min read

Related Articles

loading..

Source Code

SONARQUBE

Nokia source code breach exposes millions in stolen data, highlighting critical ...

Nokia, the telecommunications giant known for its pivotal role in global communications, finds itself in the crosshairs of a potential Nokia data breach. This incident could have serious cybersecurity ramifications for the entire sector. Third-party breaches are responsible for over 63% of all data incidents, leading to an average financial loss of $4.29 million per incident. This makes it imperative for companies like Nokia to strengthen vendor risk management. In an era where cyberattacks have surged by over 300% globally, even industry titans like Nokia are not immune to the vulnerabilities exposed through third-party collaborations. A hacker identified as IntelBroker has claimed to have stolen Nokia’s source code through a third-party contractor’s server, further exposing vulnerabilities in the Nokia source code that could have serious security implications. This breach adds a layer of urgency for Nokia to reassess its cybersecurity framework. The revelation has put the Finnish conglomerate on high alert, prompting an urgent investigation to determine the validity of these claims and the potential impact on their digital infrastructure. ### **Third-Party Breach and Vendor Risks: Managing Vendor Security in Cybersecurity** According to reports, Nokia suspects that the breach may have occurred via a third-party vendor who worked directly with the company’s development team. _“Nokia is aware of reports that an unauthorized actor has alleged to have gained access to certain third-party contractor data and possibly data of Nokia,”_ the company shared with BleepingComputer, emphasizing the gravity of the situation. _“Nokia takes this allegation seriously, and we are investigating. To date, our investigation has found no evidence that any of our systems or data have been impacted. We continue to closely monitor the situation.”_ This cautious response from Nokia follows a claim made by IntelBroker, a notorious hacker previously implicated in other cybercrimes. The hacker has declared that they are selling a _“large collection of Nokia source code,”_ allegedly extracted from a third-party contractor’s server, adding another layer of concern about the exposure of Nokia source code and the associated security risks. The breach emphasizes the need for increased vigilance in safeguarding intellectual property, reinforcing security protocols in vendor engagements, and addressing potential vulnerabilities if exploited by malicious actors. The situation underscores a recurring issue in cybersecurity—the vulnerability introduced by third-party access, leaving even large corporations at the mercy of their partners' security practices. A not-so-recent instance includes the [2020 SolarWinds](https://www.secureblink.com/cyber-security-news/40-plus-victims-of-the-solarwinds-hack-identified-by-microsoft) supply chain attack, where compromised third-party software led to breaches in several high-profile organizations, highlighting the widespread impact of such vulnerabilities. ### **Stolen Nokia Source Code and IntelBroker's Troubling Past: The Impact on Cybersecurity** IntelBroker’s statement about the stolen data is particularly concerning, as it allegedly includes highly sensitive elements—SSH keys, source code, RSA keys, BitBucket logins, SMTP accounts, webhooks, and hardcoded credentials. Such critical data, including the stolen Nokia source code, can be leveraged to further compromise company assets or even other linked systems, raising alarms about cascading cyber risks across the sector. The effects of the Nokia data breach could weaken industry partnerships and trust, which are crucial elements in the interconnected digital ecosystem. The impact could extend far beyond immediate losses, potentially triggering security failures in interconnected organizations and harming trust in industry partnerships. These cascading incidents can lead to widespread service disruptions, financial losses, and long-term reputational damage, as attackers exploit one breach to gain access to interconnected systems, creating a domino effect that could cripple not just one organization, but multiple stakeholders involved. The hacker claims to have gained access through the third-party vendor’s SonarQube server, which reportedly used default login credentials—a startling lapse in security hygiene. This negligence represents a significant flaw in basic cyber practices, painting a broader picture of the consequences of overlooking simple security fundamentals. According to a recent study, over 30% of all data breaches involve the use of default credentials, emphasizing how widespread and preventable such oversights can be. IntelBroker's ability to gain unrestricted access using default credentials highlights how even the most straightforward preventive measures, if ignored, can lead to high-stakes breaches. Furthermore, the data reportedly stolen includes Python project files linked to Nokia’s development efforts, suggesting that this was not a random attack but a targeted effort to obtain valuable intellectual property. When asked by BleepingComputer to confirm the authenticity of a file tree representing the stolen data, Nokia declined to provide an immediate response—a silence that adds another layer of uncertainty to an already tense situation. ### **A Hacker's History: IntelBroker's High-Profile Breaches and Nokia's Cybersecurity Fallout** IntelBroker has already made waves in the cyber world, leaving a trail of disruption that should serve as a warning to every organization about the potential risks and consequences of a Nokia cybersecurity breach, including loss of intellectual property, weakened customer trust, and significant financial repercussions. The hacker is linked to numerous cybersecurity incidents, including breaches of [DC Health Link](https://www.secureblink.com/cyber-security-news/fbi-probing-170-000-dc-health-link-data-breach-in-u-s-house-members)—the health care plan administrator for U.S. House members and their families—and attacks on [Hewlett Packard Enterprise (HPE)](https://www.secureblink.com/cyber-security-news/critical-hp-printers-vulnerability-leaked-sensitive-many-data) and the [Weee!](https://www.secureblink.com/cyber-security-news/weee-grocery-confirms-data-breach-exposing-1-1-million-customer-records) grocery service. More recently, IntelBroker leaked sensitive data from companies such as [FACEBOOK](https://www.secureblink.com/cyber-security-news/200-000-facebook-marketplace-records-leaked-claims-intel-broker), [GE's Pipeline](https://www.secureblink.com/cyber-security-news/intel-broker-offers-ge-s-pipelines-for-500-amid-cyberattack-probe), [T-Mobile](https://www.secureblink.com/cyber-security-news/second-t-mobile-data-breach-of-2023-attackers-access-info-of-hundreds), [AMD](https://www.secureblink.com/cyber-security-news/sink-close-a-high-severity-amd-cpu-vulnerability-enables-undetectable-malware), and [Apple](https://www.secureblink.com/cyber-security-news/apple-addresses-newly-disclosed-zero-day-in-multiple-older-i-os-devices), all of which were stolen from a third-party SaaS vendor. What distinguishes IntelBroker is not just the scale of their attacks, but the calculated selection of targets. The hacker seems to have a penchant for compromising systems through neglected points of entry—third-party vendors and weak security practices—which further fuels the debate around the weakest link in cybersecurity chains. To mitigate these risks, companies should enforce stricter vendor security protocols, such as implementing multi-factor authentication, conducting regular penetration testing, and requiring compliance with industry security standards like ISO 27001. Adopting guidelines from authoritative sources, such as NIST or CISA, can also enhance cyber resilience and ensure a more secure vendor relationship. These strategies can help reduce vulnerabilities and create a more resilient digital ecosystem. The implications of exposing source code are dire, as it could allow adversaries to exploit vulnerabilities, reverse-engineer proprietary systems, or even cripple network infrastructure—threatening Nokia’s reputation and its client networks. ### **Nokia on High Alert: Vendor Risks and Industry-Wide Cybersecurity Reassessment** This unfolding scenario has once again thrown a spotlight on the security pitfalls associated with external vendors and the shared vulnerabilities they can introduce. The third-party vendor risks in the Nokia breach emphasize how critical it is for companies to manage and scrutinize vendor relationships comprehensively. Cybersecurity is much like a fortified wall—only as strong as its most fragile brick. In this instance, Nokia's defenses may have been compromised by a weak point in the wall, represented by a third-party vendor's insufficient security measures. Nokia’s acknowledgment of a potential breach, albeit with no confirmation of compromised data thus far, raises significant questions about the accountability of third-party partners in ensuring airtight cybersecurity standards. Businesses are increasingly reliant on a broad ecosystem of vendors, partners, and third-party services—making vendor management a critical aspect of enterprise security. Companies will be closely watching how Nokia navigates this crisis—not just for a resolution, but also for signs of enhanced protocols that could prevent such incidents in the future. With the stakes so high, enterprises will need to reimagine their approach to cybersecurity. Beyond simple contractual obligations, companies should be mandating robust, verifiable security practices among their vendors. Practical steps include regular security audits, strong data encryption standards, and mandatory compliance with certifications like ISO 27001, ensuring vendors meet high cybersecurity standards. Implementing these practices helps build a more resilient digital infrastructure capable of mitigating risks. This is especially critical following incidents like the Nokia source code breach, where third-party weaknesses lead to significant exposures. These practices could include implementing zero-trust network architectures, requiring end-to-end encryption for sensitive data, and closely monitoring access privileges. The fallout from this breach has the potential to reshape how the tech industry approaches third-party relationships, compelling everyone from startups to giants like Nokia to think harder about the defenses in their extended digital ecosystem. ### **Summary: Nokia Source Code Breach and Its Cybersecurity Impact** Nokia faces a potential data security breach after a hacker known as IntelBroker claimed to have stolen Nokia's source code via a third-party contractor, an incident now widely known as the Nokia source code breach. This breach highlights significant cybersecurity flaws in vendor relationships and brings into focus the necessity of digital ecosystem resilience. The incident has underscored the significant risks associated with third-party vendor security, as Nokia continues to investigate and monitor the situation. This alleged breach pushes the industry to reconsider its approach to cybersecurity rigor. Enhanced vendor scrutiny, proactive security measures, and holistic supply chain audits may become crucial steps in preventing similar future incidents.

loading..   07-Nov-2024
loading..   9 min read
loading..

JIRA

Schneider Electric faces a 40GB data breach, exposing isolated system vulnerabil...

[Schneider Electric](https://www.secureblink.com/cyber-security-news/1-5-tb-allegedly-stolen-from-schneider-electric-by-cactus-ransomware) recently confirmed a security breach involving its internal developer platform, resulting in the compromise of over 40GB of sensitive data from there JIRA server. The breach was claimed by a threat actor known as 'Grep,' who publicly [mocked](https://x.com/grepcn/status/1853089027777261941) Schneider on X (formerly Twitter). The stolen dataset reportedly includes over 400,000 rows of information, comprising 75,000 unique email addresses, employee names, project data, and critical infrastructure details. The attack vector leveraged exposed credentials that allowed Grep unauthorized access to Schneider Electric’s isolated JIRA server. Once access was obtained, the attackers used the MiniOrange REST API—a third-party MFA management tool—to scrape user information. The reliance on this open-source MFA tool played a significant role in the vulnerability, as Grep exploited insufficient API protections. This incident exposes an inherent weakness in isolated environments that are often perceived as secure by virtue of reduced network accessibility, without adequately accounting for poor credential hygiene and inadequate API security configurations. ### Exploit Analysis & Threat Actor Profile Grep’s actions are affiliated with a newly-formed hacking group named the International Contract Agency (ICA). Named after the fictional organization from the game *Hitman: Codename 47*, ICA distinguishes itself by its non-traditional extortion model. Instead of directly demanding ransom from targeted entities, ICA threatens to leak the data if the affected company fails to acknowledge the breach within a 48-hour window. In Schneider's case, Grep humorously demanded $125,000 in "Baguettes"—a sarcastic nod to Schneider's French origins—claiming it was not a serious financial demand but a mechanism to ensure public awareness of the incident. The data compromised includes project issues, plugins, and a significant volume of employee and customer personal details. The target environment was an "isolated" server, which Schneider believed would be inherently more secure. However, this perceived isolation led to complacency, resulting in weak credential management practices. Grep's successful scraping of the 40GB dataset from what was thought to be an isolated server reveals that the weakest link, often involving human error, remains a critical entry point for attackers, regardless of the perceived security of system boundaries. ### Detailed Technical Response & Analysis Following the breach, Schneider Electric mobilized its Global Incident Response team, emphasizing that its products and services were not directly impacted. Nonetheless, this statement fails to address deeper concerns about Schneider’s systemic cybersecurity protocols. This breach is part of an ongoing trend, as earlier in the year, Schneider’s Sustainability Business division fell victim to a [Cactus ransomware attack](https://www.secureblink.com/cyber-security-news/1-5-tb-allegedly-stolen-from-schneider-electric-by-cactus-ransomware), during which attackers purportedly extracted terabytes of proprietary data. The implications of these recurring incidents are manifold. As a company that forms the backbone of energy management and industrial automation solutions globally, any compromise involving Schneider Electric's systems potentially threatens critical infrastructure. Such infrastructure, once breached, can cascade into operational disruptions, creating far-reaching national and global consequences. The attack trajectory underscores the necessity for layered security mechanisms that do not solely rely on network isolation but also integrate robust credential policies, thorough monitoring, and encryption. Moreover, ICA's strategic decision to disclose breaches only when unacknowledged forces a reevaluation of traditional cybersecurity incident management protocols. By compelling companies to respond publicly, ICA manipulates the timeline and transparency of data breaches. Schneider’s compliance with the 48-hour acknowledgment prevented immediate data exposure, but the incident underlines the need for adopting proactive measures instead of reactive containment. ### Evolving Cyber Threats and the Importance of Robust Technical Controls This breach is a critical lesson in the importance of assuming an eventual breach mindset, even in seemingly secure environments. Credential management must be prioritized through strategies such as enforcing least privilege principles, implementing password rotation policies, and deploying strong MFA implementations that are less susceptible to automated scraping. Reliance on third-party and open-source solutions such as the MiniOrange REST API introduces additional attack surfaces, requiring organizations to conduct comprehensive code audits, penetration testing, and detailed security assessments. The attack also highlights the importance of API security, emphasizing the need for rate limiting, proper authentication, and auditing all access points, especially for systems interfacing with critical internal infrastructure. Furthermore, this incident showcases the critical necessity for corporations involved in essential services to transition from passive cybersecurity measures to an actively engaged, proactive cybersecurity model. Threat actors like Grep are evolving, leveraging data not just for immediate financial gain but as a means to publicly pressure organizations into acknowledging weaknesses. The stakes are increasingly high, and sophisticated defense mechanisms must involve advanced threat intelligence, real-time threat hunting, and granular access control mechanisms. Organizations must also consider the human factor, which remains a significant vulnerability. Extensive employee training on cybersecurity best practices—including managing personal credentials, identifying phishing attempts, and understanding data sensitivity—must form the foundation of any corporate security strategy. The absence of such training often results in inadvertent gaps that adversaries like ICA can exploit.

loading..   05-Nov-2024
loading..   5 min read
loading..

Encryptor

Interlock

Interlock ransomware disrupts organizations worldwide, encrypting data on FreeBS...

The **Interlock ransomware** has emerged as a new and dangerous player on the global cyber threat landscape, targeting **FreeBSD servers**—an uncommon but highly valuable target. This tactic signifies a shift among ransomware operators who are broadening their range from typical Windows systems to less traditionally attacked environments, exploiting vulnerabilities in systems critical to enterprise infrastructure. This deep-dive explores **Interlock’s strategy**, the technical nuances that make it a distinctive threat, and how organizations can protect against this sophisticated ransomware. #### What is Interlock Ransomware? The **Interlock ransomware** made its appearance in **September 2024**, quickly gaining notoriety for its targeted focus on **FreeBSD systems**, a Unix-like operating system widely used in critical infrastructure due to its stability and performance. Unlike most ransomware that primarily focuses on **Windows** and **Linux** platforms, Interlock has taken the **unusual approach of developing a custom encryptor for FreeBSD**. This targeting strategy allows attackers to disrupt key operations, leveraging the fact that FreeBSD is often used for hosting crucial services and managing enterprise workloads. #### A Targeted Approach to Attack FreeBSD Servers The FreeBSD-targeting encryptor is notable because ransomware designed specifically for this platform is rare. Historically, ransomware groups have focused their efforts on **Windows systems** due to their sheer number and extensive use. However, as **Hive ransomware** and others have shifted towards attacking **Linux** and **FreeBSD** environments, so too has Interlock, marking a new chapter in the evolution of cyber threats. **Why FreeBSD?** The answer lies in the widespread use of FreeBSD servers in environments that require high reliability and uptime, such as network infrastructure and hosting services. By successfully compromising these systems, Interlock’s operators aim to maximize the impact of their attacks, resulting in significant operational disruptions for the victim. #### Technical Deep Dive: Understanding the Interlock Encryptor The **Interlock ransomware encryptor** was initially detected by researchers who noted that it is an **ELF binary** specifically compiled for FreeBSD 10.4. The ELF (Executable and Linkable Format) is typically used for Unix-like operating systems, and its compilation for FreeBSD shows the deliberate targeting of this niche but important platform. Upon analysis, the **Interlock encryptor** presented itself as a **64-bit statically linked ELF binary**, which means that the malware includes all necessary libraries to run independently of the host system's library versions. This tactic ensures that the ransomware works across different versions of FreeBSD, expanding its range of potential victims. The **statically linked** nature of the encryptor also means that the payload is harder to interfere with or block without full access to the system. When executed, the **ransomware appends the extension .interlock** to encrypted files and drops a ransom note named "!__README__!.txt" in each affected directory. This file provides the victim with instructions to access an **anonymous Tor-based negotiation site**, where they are coerced into paying a hefty ransom to regain access to their data. #### Double-Extortion: Theft and Encryption Interlock employs a **double-extortion model**—not only does it encrypt files, but it also exfiltrates data before initiating encryption. The stolen data serves as additional leverage, threatening to publicly release it if the ransom is not paid. This tactic not only creates financial pressure on organizations but also raises the stakes by threatening their **reputation** and regulatory consequences. #### Real-World Impact: Wayne County Example The **Wayne County government** in Michigan became one of the early victims of the Interlock ransomware attack. The attack took place on October 3, 2024, and led to disruptions across county services, including preventing **online tax payments**, **inmate bonding** at the Sheriff's Office, and **recording real estate transactions** at the Register of Deeds Office. This highlights the **critical impact** that targeting FreeBSD infrastructure can have, especially when it powers essential public services. The attack involved multiple system shutdowns, revealing the broad reach of a targeted ransomware attack on essential services and critical infrastructure. #### Lateral Movement and Encrypted Negotiations During the attack process, Interlock spreads laterally throughout the compromised network, infecting multiple systems before deploying the ransomware. Once encryption is completed, victims are instructed to use an **anonymous chat room on the dark web**. To access this chat room, victims must enter an **organization-specific ID**, ensuring that the ransomware operators can uniquely identify each victim and negotiate individually, often based on the victim’s ability to pay. #### How to Defend Against Interlock Ransomware? Given the sophisticated nature of Interlock ransomware, it is imperative for organizations, particularly those using FreeBSD, to take proactive measures: 1. **Patch Management**: Always ensure that systems are running the latest updates. FreeBSD systems should be patched to mitigate known vulnerabilities. 2. **Multi-Factor Authentication (MFA)**: Implement **MFA** for remote access services like SSH to reduce the risk of unauthorized access. 3. **Data Backup**: Regularly backup data and store backups offline to prevent ransomware from encrypting both live data and backup copies. 4. **Endpoint Detection and Response (EDR)**: Deploy **EDR solutions** to monitor and detect any anomalous activity within the network. This includes unauthorized lateral movement or attempts to encrypt files. The **Interlock ransomware** is a stark reminder of the rapidly evolving nature of **cyber threats**. By targeting **FreeBSD**, a platform not usually associated with mainstream ransomware attacks, Interlock has demonstrated the ability of ransomware operators to diversify their attacks to increase impact and pressure. Organizations using FreeBSD must reinforce their **cyber defenses**, patch vulnerabilities, and prepare for the eventuality of an attack to mitigate the damage. The evolution of **cross-platform ransomware**, as seen in the cases of both **Interlock** and **Hive**, means that organizations can no longer rely solely on traditional antivirus or security practices designed primarily for **Windows** environments. Instead, a **holistic approach** to security, involving advanced monitoring, robust backup strategies, and stringent access controls, is necessary to safeguard against these increasingly sophisticated threats.

loading..   03-Nov-2024
loading..   5 min read