Rome’s La Sapienza University is continuing to experience major operational disruption after a cyber intrusion forced administrators to take its digital infrastructure offline as a safety measure. The shutdown began on February 2 and has affected core online services used by students, faculty, and administrative staff.
Since the incident, students have been unable to complete basic academic and administrative tasks such as registering for examinations, viewing tuition-related records, or accessing official contact information for teaching staff. With internal platforms unavailable, the university has relied mainly on its social media channels to share updates. These notices have acknowledged the disruption but have not provided detailed technical explanations or a confirmed date for when full access will be restored.
University officials confirmed that their systems were deliberately powered down to contain the threat and to prevent malicious software from spreading to other parts of the network. Emergency shutdowns of this kind are typically used when there is a risk that an attack could compromise additional servers, user accounts, or stored data. This response suggests that the incident involved harmful software capable of moving across connected systems.
According to publicly available reporting, the disruption was caused by ransomware, a category of cyber attack in which criminals attempt to lock organizations out of their own systems or data. Some media sources have claimed that a newly observed cybercrime group may be linked to the breach and that a ransomware variant referred to in security research as Bablock, also known as Rorschach, may have been involved. These attributions are part of ongoing assessments and have not been formally confirmed by authorities.
Technical analyses cited in public reporting describe this malware family as drawing components from previously leaked cybercrime tools, allowing attackers to combine multiple techniques into a single, highly disruptive program. Such ransomware is designed to operate rapidly and can spread across large digital environments, which helps explain the scale of the disruption experienced by one of Europe’s largest universities by student enrollment.
The university has formally reported the incident to Italian law enforcement and to the National Cybersecurity Agency, both of which are now involved in the investigation and response. Administrators have stated that emergency management is being coordinated across academic offices, administrative departments, and student representatives, with discussions underway to introduce deadline extensions and flexible arrangements to limit academic harm.
Due to the ongoing shutdown of internal systems, campus information desks are currently unable to access digital records that would normally support student inquiries. Updates about service availability and office hours are being shared through official faculty social media pages.
Meanwhile, technical teams are examining the full scope of the breach before restoring systems from backups. This step is necessary to ensure that no malicious code remains active. It is still unclear whether all stored data can be fully recovered or whether some information may remain inaccessible following the attack.
A dangerous piece of malware has been discovered hidden inside a Python software package, raising serious concerns about the security of open-source tools often used by developers.
Security experts at JFrog recently found a harmful package uploaded to the Python Package Index (PyPI) – a popular online repository where developers share and download software components. This specific package, named chimera-sandbox-extensions, was designed to secretly collect sensitive information from developers, especially those working with cloud infrastructure.
The package was uploaded by a user going by the name chimerai and appears to target users of the Chimera sandbox— a platform used by developers for testing. Once installed, the package launches a chain of events that unfolds in multiple stages.
It starts with a function called check_update() which tries to contact a list of web domains generated using a special algorithm. Out of these, only one domain was found to be active at the time of analysis. This connection allows the malware to download a hidden tool that fetches an authentication token, which is then used to download a second, more harmful tool written in Python.
This second stage of the malware focuses on stealing valuable information. It attempts to gather data such as Git settings, CI/CD pipeline details, AWS access tokens, configuration files from tools like Zscaler and JAMF, and other system-level information. All of this stolen data is bundled into a structured file and sent back to a remote server controlled by the attackers.
According to JFrog’s research, the malware was likely designed to go even further, possibly launching a third phase of attack. However, researchers did not find evidence of this additional step in the version they analyzed.
After JFrog alerted the maintainers of PyPI, the malicious package was removed from the platform. However, the incident serves as a reminder of the growing complexity and danger of software supply chain attacks. Unlike basic infostealers, this malware showed signs of being deliberately crafted to infiltrate professional development environments.
Cybersecurity experts are urging development and IT security teams to stay alert. They recommend using multiple layers of protection, regularly reviewing third-party packages, and staying updated on new threats to avoid falling victim to such sophisticated attacks.
As open-source tools continue to be essential in software development, such incidents highlight the need for stronger checks and awareness across the development community.
Many organisations tend to focus on immediate threats, prioritising the detection and mitigation of the latest vulnerabilities. However, this approach overlooks a broader issue: many cyberattacks exploit vulnerabilities that have existed for years. In fact, 76% of vulnerabilities targeted by ransomware were identified more than three years ago, highlighting a critical gap in long-term security strategies.
Why VOCs Matter
To effectively address this gap, organisations should adopt a more centralised and automated approach to vulnerability management. This is where a dedicated Vulnerability Operations Center (VOC) comes into play. A VOC serves as a specialised unit, either integrated within or operating alongside a Security Operations Center (SOC), with the primary task of managing security flaws within the IT infrastructure. Unlike a SOC, which focuses on real-time threat alerts and incidents, a VOC zeroes in on vulnerabilities—identifying, prioritising, and mitigating them before they escalate into serious security breaches.
What Is a VOC?
Creating a seamless connection between a SOC and a VOC is crucial for effective cybersecurity. This integration ensures that vulnerability data is quickly and efficiently passed to threat response teams. The process begins with appointing a team to set up the VOC, overseen by the Chief Information Security Officer (CISO) or another senior security leader. Given the scope of this initiative, it should be treated as a major security operations project, with clear roles and responsibilities outlined from the start.
Connecting VOC and SOC
The initial step involves using vulnerability assessment tools to evaluate the organisation’s current security posture. This assessment helps to identify existing vulnerabilities across all assets. The next phase is to aggregate, clean, and organise this data, making it actionable for further use. Once this dataset is established, it is integrated into the SOC’s security information and event management (SIEM) systems, thereby enhancing the SOC’s ability to monitor and respond to threats with greater context and clarity.
Focusing on Risk
An essential component of VOC operations is moving beyond just technical vulnerability assessments to a more risk-based prioritisation approach. This means evaluating vulnerabilities based on their potential impact on the business and addressing the most critical ones first. Automating routine SOC tasks—such as regular vulnerability scans, alert handling, and patch management—also plays a vital role. By implementing automation tools that leverage the VOC’s data, SOC teams can focus on more complex tasks that require human intervention, improving overall efficiency and effectiveness.
Continuous Improvement
Once the VOC is fully operational, the focus should shift to continuous improvement and adaptation. As new vulnerabilities and trends emerge, the SOC must update its monitoring and response strategies to keep pace. Establishing feedback loops between the SOC and VOC ensures that both teams are aligned and responsive to the incessant development of threats.
Building a Strong Policy
Moreover, a strong policy and governance framework is necessary to support the integration of the VOC and SOC. Security teams need to define clear schedules, rules, and Service Level Agreements (SLAs) for addressing vulnerabilities. For example, vulnerabilities like Log4j, which are widely exploited, should trigger immediate notifications to SOC teams to ensure a swift response.
The Future of Security
While setting up a VOC may seem challenging, it is a critical step towards addressing the persistent vulnerability issues. Unlike the current reactive approach, a VOC allows for a more proactive, risk-based management of vulnerabilities across IT and security teams. By moving beyond the outdated, piecemeal strategies of the past, organisations can achieve a higher level of security, protecting their assets from both old and new threats.
In a survey of 500 IT security experts, Exabeam researchers discovered that nearly two-thirds of their respondents (65%) prioritize prevention over detection as their number one endpoint security objective. For the remaining third (33%), detection remained their utmost priority.
To make the situation worse, the businesses actually act on this idea. The majority (59%) allocate the same amount to detection, investigation, and response, while nearly three-quarters (71%) spend between 21% and 50% of their IT security resources on prevention.
According to Steve Moore, chief security strategist at Exabeam, the issue with this strategy is that the businesses concentrate on prevention while threat actors are already there, rendering their efforts useless.
“As is well known, the real question is not whether attackers are on the network, but how many there are, how long they have had access and how far they have gone[…]Teams need to raise awareness of this question and treat it as an unwritten expectation to realign their investments and where they need to perform, paying due attention to adversary alignment and response to incidents. Prevention has failed,” says Moore.
The majority of responders said yes when asked if they are confident, they can prevent attacks. In fact, 97% of respondents indicated they felt confident in the ability of their tools and processes to detect and stop attacks and data breaches.
Only 62% of respondents agreed when asked if they could easily inform their boss that their networks were not compromised at the time, implying that over a third were still unsure.
Exabeam explains that security teams are overconfident and have data to support it. The company claims that 83% of organizations experienced more than one data breach last year, citing industry reports.
Among the many approaches implemented in order to combat security affairs, most organizations appear to be inclined towards the prevention-based strategy. The reason is, it strives to make systems more resistant to attack. Contrary to detection-based security, this approach is more effective in a variety of situations.
Implementing a preventive approach could aid a company in significantly reducing the risk of falling prey to a potential cyberattack if it applies appropriate security solutions like firewalls and antivirus software and patches detected vulnerabilities.