Search/sentry
● Vendor

sentry

Known CVEs
0
Highest CVSS
—
In KEV
0
Vendor
sentry software development kit
Connections
22 relationships
177: National Public Data
This is the story of the hacker known as “USDoD”. When he was young he had a vengeance on the US, and this lead him down a road of continual data breaches, until he hacked into National Public Data, which is when his spree went one step too far. Sponsors Support for this show comes from ThreatLocker. ThreatLocker is a Zero Trust Platform that gives organizations control over what can run and what users and devices can access. It combines prevention with real time detection and automated response, helping security teams stop unauthorized activity and quickly contain compromised machines. Learn how ThreatLocker can strengthen your defenses at threatlocker.com/Darknet. This show is sponsored by Maze. Maze uses AI agents to triage and remediate cloud vulnerabilities by figuring out what’s actually exploitable, not just what’s theoretically risky. They remove the noise, prioritize vulns that matter, and manage remediation, so your team stops wasting time on meaningless vulns. Visit MazeHQ.com/darknet for more information. This show is sponsored by Sentry.IO. Sentry wants to help you monitor your environment for problems. They do error tracking, stack tracing, debugging, all so that your developers can diagnose, fix, and optimize the performance of their code. This makes it so developers ship more reliable code faster. Learn more at sentry.io. Sources https://www.latimes.com/california/story/2024-04-09/william-woods-identity-theft-social-security-matthew-david-kierans https://predictalab.medium.com/how-to-discover-a-major-hackers-identity-with-osint-solution-1-625deff0f0ac https://databreaches.net/2023/09/17/im-not-pro-russia-and-im-not-a-terrorist-infragard-and-airbus-hacker-usdod-unveils-his-new-campaigns/ https://cyble.com/blog/u-s-armed-forces-and-defense-industrial-base-under-cyber-attack/ https://krebsonsecurity.com/2022/12/fbis-vetted-info-sharing-network-infragard-hacked/ https://krebsonsecurity.com/2024/08/national-public-data-published-its-own-passwords/ https://www.hudsonrock.com/blog/an-avoidable-breach-fbi-hacker-leaks-sensitive-airbus-data https://www.gov.br/pf/pt-br/assuntos/noticias/2024/10/pf-prende-hacker-suspeito-de-invadir-sistemas-da-pf-e-de-outras-instituicoes-internacionais https://ritchietorres.house.gov/posts/congressman-ritchie-torres-releases-investigative-report-on-last-months-national-public-data-breach https://krebsonsecurity.com/2024/08/nationalpublicdata-com-hack-exposes-a-nations-data/ https://www.tecmundo.com.br/seguranca/288570-hacker-roubou-3-bilhoes-dados-eua-descoberto-brasileiro.htm https://hackread.com/usdod-hacker-ssn-leak-reveals-brazilian-citizen/ https://www.latimes.com/business/technology/story/2022-10-26/identity-theft-nightmare https://www.akleg.gov/basis/get_documents.asp?session=29&docid=65936 https://abc7news.com/post/oakland-ransomware-attack-identity-theft-mayor-sheng-thao-fraud/14227735/ Attribution Darknet Diaries is created by Jack Rhysider. Written by Nate Nelson. Assembled by Tristan Ledger. Sound Design by Garrett Tiedemann. Episode artwork by odibagas. Mixing by Proximity Sound. Theme song created by Breakmaster Cylinder. Theme song available for listen and download at bandcamp. Or listen to it on Spotify. Transcript JACK: So, back in 1988 there was this identity theft incident that happened which, when I read it, it infuriated me so badly and, well, now I want to infuriate you. So, check this story out. [Music] This all started in Albuquerque, New Mexico, like I said, 1988, and there was a hot dog stand there which seemed to hire people who were really down and out.
darknetdiaries.comJul 21, 2026extracted
Microsoft Working on Patch for ‘RoguePlanet’ Zero-Day
Microsoft on Wednesday published an advisory acknowledging the public disclosure of a vulnerability in Defender that could lead to privilege escalation. The security defect, now tracked as CVE-2026-50656 (CVSS score of 7.8), was dropped last week by security researcher Nightmare Eclipse (also known as Chaotic Eclipse). “Microsoft is aware of an elevation of privilege in the Microsoft Malware Protection Engine in Microsoft Defender publicly referred to as ‘RoguePlanet’,” the tech giant’s advisory reads. “We are working to provide a high-quality security update that addresses this vulnerability. We will provide information in this CVE when the update is available,” Microsoft adds. RoguePlanet, Nightmare Eclipse explained last week, targets a race condition in Microsoft Defender and allows attackers to gain System privileges. The researcher released a proof-of-concept (PoC) exploit that demonstrates local privilege escalation (LPE) on Windows 11 and Windows 10 systems with the June 2026 patches installed. Initially, Nightmare Eclipse noted, the bug could be abused for remote code execution (RCE), but some of the exploitation paths were closed in May, when Microsoft rolled out updates that hardened Defender. The RoguePlanet PoC was reworked to circumvent these mitigations and can be unreliable. However, the researcher was confident that it could be refined to work at all times, even on Windows Server systems. On Wednesday, Nightmare Eclipse pointed out that the PoC works regardless of whether Defender’s real-time protection is enabled or disabled. It may even work in passive mode, the researcher said. Over the past couple of months, driven by discontent towards Microsoft’s vulnerability disclosure process, Nightmare Eclipse dropped several zero-day exploits targeting the company’s products, including BlueHammer (CVE-2026-33825), RedSun (CVE-2026-41091), and UnDefend (CVE-2026-45498), which have been exploited in the wild. Microsoft rolled out fixes for all three, and the June 2026 Patch Tuesday updates included patches for two other Nightmare Eclipse exploits, namely GreenPlasma and YellowKey. RoguePlanet is the second Nightmare Eclipse exploit mentioned in a Microsoft advisory. The first was YellowKey, in a May advisory providing mitigations while accusing the researcher of violating coordinated vulnerability best practices. Microsoft’s comments sparked backlash from the cybersecurity community. Related: Joomla, LiteSpeed Vulnerabilities Exploited in Attacks Related: 3 Recently Patched Fortinet FortiSandbox Vulnerabilities in Hacker Crosshairs Related: Ivanti Sentry Exploitation Attempts Hitting Honeypots
securityweek.comJun 17, 2026extracted
Joomla, LiteSpeed Vulnerabilities Exploited in Attacks
Threat actors are targeting vulnerabilities in Joomla and the LiteSpeed cPanel plugin for code execution and privilege escalation. Affecting the Joomla Content Editor (JCE) for Joomla and tracked as CVE-2026-48907, the first bug is described as an improper access issue that allows unauthenticated attackers to upload editor profiles. Attackers have been exploiting the flaw to upload arbitrary files to the server, leading to arbitrary PHP code execution. All JCE Pro versions before 2.9.99.5 are affected. The security defect was addressed on June 3, and additional protections were included in version 2.9.99.6, released on June 6. Over the weekend, Joomla urged users to update their deployments to the latest version as soon as possible, warning that CVE-2026-48907 has been exploited in the wild. “The vulnerability is being actively exploited, working exploit code is public, and the attacks are automated, so a site with no public registration is not safe,” Joomla warned. It also provided indicators of compromise (IoCs) to help site admins hunt for potential compromises. “Updating closes the entry point but does not clean a site that was already compromised. If you were hit before updating, the update will not remove what the attacker left behind,” Joomla said. LiteSpeed’s user-end plugin for cPanel was found vulnerable to CVE-2026-54420, a UNIX Symbolic Link (symlink) following vulnerability. Due to improper handling of symlinks, users with FTP or web shell access could elevate their privileges to root on the shared hosting servers running CloudLinux/CageFS. The security defect impacts all versions of the user-end cPanel plugin before 2.4.8, which was released on June 1, and has been exploited in the wild since May. LiteSpeed users are advised to update their deployments immediately and to use the command provided by the maintainers to check whether their servers have been compromised. This week, the US Cybersecurity and Infrastructure Security Agency (CISA) added the LiteSpeed and Joomla bugs to its Known Exploited Vulnerabilities (KEV) catalog, urging federal agencies to patch them by June 18 and June 19, respectively. Per CISA’s BOD 26-04, security weaknesses that require immediate patching pose the highest risks to federal agencies, as they can be abused in automated attacks that could lead to asset takeover. Related: Tech Coalition ‘Athena’ Targets OSS Vulnerabilities Ahead of Disclosure Related: Cisco Patches Another SD-WAN Zero-Day Exploited in Attacks Related: Ivanti Sentry Exploitation Attempts Hitting Honeypots Related: Chrome 149 Update Patches 28 Vulnerabilities
securityweek.comJun 17, 2026extracted
Agentjacking Attack Tricks AI Coding Agents Into Running Malicious Code
Cybersecurity researchers have described what they say is a new class of attack that can trick artificial intelligence (AI) coding agents into running arbitrary code on developer machines. Called Agentjacking by Tenet Security, the attack can be triggered by means of a fake error report crafted using Sentry, an open-source error-tracking and performance-monitoring platform. "The attack exploits a critical architectural flaw at the intersection of Sentry's event ingestion (which accepts arbitrary payloads from anyone with the DSN) and the Sentry MCP server (which returns this data to AI agents as trusted system output)," security researchers Ron Bobrov, Barak Sternberg, and Nevo Poran said. The idea is to inject crafted input into Sentry error events, which are then interpreted by coding agents like Claude Code and Cursor as legitimate diagnostic resolution steps and run attacker-controlled code. A successful attack of this kind can expose sensitive data, including environment variables, Git credentials, private repository URLs, and developer identities, without having to rely on methods like phishing or prior server compromise. The problem is rooted in the implicit trust associated with connecting to external services using Model Context Protocol (MCP). Because an AI agent is unable to distinguish between an error event generated by a real application crash or injected by an attacker, it creates a pathway to arbitrary code execution when the agent processes the response. The attack chain devised by Tenet is as follows - An attacker finds a target's Sentry Data Source Name (DSN), a public, write-only credential that's embedded in websites. The attacker sends a malicious error event to Sentry's ingest endpoint via a POST request using the DSN. The injected event contains "carefully formatted markdown" in the message field and context key names. When the Sentry MCP server returns this event to an AI agent, it is rendered as structured content visually identical to the Sentry's system template. When a developer asks their AI coding agent to "fix unresolved Sentry issues" (or a similar prompt), the agent queries Sentry via MCP and receives the malicious event. The agent executes malicious code, which runs with the developer's full privileges. "The attacker never touches the victim's infrastructure," the researchers explained. "The malicious instruction arrives disguised as a legitimate 'Resolution' inside an ordinary error. When a developer asks their AI agent to fix the Sentry issue, the agent reads the attacker's command as trusted guidance and runs it - with the developer's own privileges, on the developer's own machine." Agentjacking stands out because it targets the AI agent a developer trusts and uses a Sentry DSN as a starting point. In addition, the markdown injection is rendered such that the agent cannot distinguish it from legitimate Sentry guidance. The AI cybersecurity company said it found at least 2,388 organizations exposed with valid injectable DSNs, and that it tested the attack in a controlled manner against over 100 organizations, achieving an 85% exploitation success rate against injected errors across some of the most widely used AI coding assistants. Sentry, for its part, has acknowledged the issue, but opted not to fix it, stating it's "technically not defensible." However, the company is said to have activated a global content filter that blocks a "specific payload string." "As enterprises race to deploy AI coding agents, this research proves the agents themselves are now the attack surface - turned against the developers who trust them, using nothing but data those organizations publish about themselves," Tenet said. "The attack bypasses EDR, WAF, IAM, VPN, Cloudflare, and firewalls - because there is nothing malicious to detect. Every action in the chain is authorized."
thehackernews.comJun 12, 2026extracted
Ivanti Sentry Exploitation Attempts Hitting Honeypots
The US Cybersecurity and Infrastructure Security Agency (CISA) flagged a recently patched Ivanti Sentry vulnerability as exploited, but Ivanti says the activity was observed only on honeypots. Tracked as CVE-2026-10520 (CVSS score of 10/10), the security defect is described as an OS command injection issue that could be exploited remotely, without authentication, to execute arbitrary code with root privileges. Ivanti rolled out patches for the flaw on June 10, saying it has no evidence of in-the-wild exploitation. Ivanti Sentry versions 10.5.2, 10.6.2, and 10.7.1 contain the fixes. On Thursday, CISA added the bug to its Known Exploited Vulnerabilities (KEV) catalog, urging federal agencies to address it within three days, in line with BOD 26-04 guidance to prioritize patching based on risk. “This vulnerability can be successfully exploited in cases where the Sentry appliance is in an unmanaged state with its endpoints externally reachable. The use of mTLS with EPMM or restricted HTTPS access through Neurons for MDM makes interfaces inaccessible to external actors,” CISA notes. Ivanti has updated its advisory to reflect the CVE’s addition to CISA’s KEV list, but pointed out that it was based on “attempted exploitation of honeypots”. “It is important for customers to know that exploitation of CVE-2026-10520 requires access to the management port (8443). Management interfaces should never be exposed to the internet, though honeypots often have misconfigurations to identify malicious behavior,” Ivanti says. The company also underlines that, despite the vulnerability’s CVSS score, the risk it poses is significantly decreased based on deployment and configuration. Ivanti’s note, which is mirrored in CISA’s KEV entry, explains that the vulnerable APIs are protected by mTLS for EPMM-managed Sentry appliances, and that unmanaged Sentry instances cannot be used in production, “as the management is what pushes the configuration for device connectivity and authentication”. For Neurons for MDM-managed Sentry appliances, the company recommends restricting internet access to the vulnerable API, regardless of deployment. Related: Google Confirms Exploitation of Oracle PeopleSoft Zero-Day by ShinyHunters Related: Alert Fatigue Is Becoming a Security Threat of Its Own Related: Splunk, Palo Alto Networks Patch Severe Vulnerabilities
securityweek.comJun 12, 2026extracted
CISA orders feds to patch actively exploited Ivanti flaw by Sunday
Update June 15, 00:54 EDT: An Ivanti spokesperson told BleepingComputer that CISA added the flaw to its KEV catalog based on reports of attempted exploitation of honeypots. "While this CVE carries a CVSS score of 10, the risk posed to customers is decreased significantly based on deployment and configuration," the spokesperson added. "Successful exploitation requires access to the management port 8443 and this port should never be exposed to the internet. Honeypots often have misconfigurations to identify and track malicious behavior." The U.S. Cybersecurity and Infrastructure Security Agency (CISA) ordered government agencies to patch an actively exploited Ivanti Sentry flaw within three days, as mandated by the newly issued Binding Operational Directive (BOD) 26-04. Tracked as CVE-2026-10520, this maximum-severity vulnerability was found in Ivanti's security gateway appliance (formerly known as MobileIron Sentry) and stems from an OS command injection weakness. On Wednesday, one day after Ivanti released patches for CVE-2026-10520 and said that it had no evidence of in-the-wild exploitation, the Shadowserver Internet security watchdog reported that attackers had already backdoored many of the Sentry gateways exposed online. While Shadowserver now tracks just over 50 Sentry admin portals exposed online, it says the number of Internet-exposed Ivanti Sentry instances it can detect is likely limited by organizations blocking its security scanner, and warns that systems that weren't already patched are likely compromised. "We are observing a large amount of Ivanti Sentry CVE-2026-10520 exploitation attempts based on the public PoC today," it said. "While our detection is on the lowish side due to multiple Ivanti Sentry instances not reachable in our scans (blocklisted?), if you have not patched now you are most likely compromised." On Thursday, CISA also confirmed that the CVE-2026-10520 vulnerability is now actively exploited in attacks and added it to its Known Exploited Vulnerabilities Catalog (KEV), ordering Federal Civilian Executive Branch (FCEB) agencies to secure their Ivanti Sentry instances within three days, as required by Binding Operational Directive (BOD) 26-04. "This type of vulnerability is a frequent attack vector for malicious cyber actors and poses significant risks to the federal enterprise," the cybersecurity agency warned. "Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines." BOD 26-04 was issued on Wednesday (superseding and revoking the older BOD 19-02 and BOD 22-01), and it requires U.S. federal agencies to prioritize patching if the asset is publicly exposed online, if the security flaw was added to CISA's KEV catalog, if exploitation can be automated for large-scale attacks, and if successful exploitation gives attackers partial or total control of a targeted system. While CVE-2026-10520 is the first vulnerability for which BOD 26-04 applies, in recent weeks CISA has ordered federal agencies to patch other security flaws within three days, including a Check Point VPN zero-day, a high-severity Oracle WebLogic Server vulnerability exploited in the wild, and an actively exploited cPanel plugin flaw. Over the past several years, CISA has flagged 35 vulnerabilities across a wide range of Ivanti products that have been abused in attacks, with 12 targeted by ransomware gangs. Overall prevention scores can hide what happens after initial access. Once attackers are using valid credentials, prevention drops sharply. The Blue Report 2026 measures defenses technique by technique across 338 million simulations run in customer production environments. Get the report
bleepingcomputer.comJun 12, 2026extracted
Max severity Ivanti Sentry vulnerability now exploited in attacks
Attackers are now targeting a recently patched maximum-severity flaw in Ivanti Sentry, enabling them to execute code with root privileges on Internet-exposed secure mobile gateways. Formerly known as MobileIron Sentry, the Ivanti Sentry security gateway appliance secures traffic between back-end corporate systems and remote mobile devices. Tracked as CVE-2026-10520, the maximum-severity vulnerability stems from an OS command injection weakness and was patched by Ivanti on Tuesday with the release of Sentry versions R10.5.2, R10.6.2, and R10.7.1. While the company said at the time that it had no evidence of in-the-wild exploitation, the Shadowserver nonprofit security organization reported the next day that attackers had already backdoored most of the Sentry gateways exposed online. The Internet security watchdog also added that, while its scans detect only a very limited number of exposed Sentry instances, there are likely more due to its search engine being blocklisted. "We are observing a large amount of Ivanti Sentry CVE-2026-10520 exploitation attempts based on the public PoC today. We see 19 vulnerable instances in our own scans, with at least 2 backdoored (thanks to Saudi NCA for the tip!). However, all remaining likely compromised too," Shadowserver warned. "While our detection is on the lowish side due to multiple Ivanti Sentry instances not reachable in our scans (blocklisted?), if you have not patched now you are most likely compromised." Ivanti has yet to update the security advisory issued on Tuesday, which still states that "We are not aware of any customers being exploited by these vulnerabilities at the time of disclosure." An Ivanti spokesperson was not immediately available for comment when BleepingComputer reached out today for further details on these ongoing attacks. Hackers often target Ivanti security flaws because they provide an entry point into targets' enterprise networks, enabling the theft of sensitive customer and corporate data. For instance, Multiple Ivanti zero-days have been exploited in recent years to breach a wide range of targets (such as government agencies worldwide), including two critical Endpoint Manager Mobile (EPMM) vulnerabilities that Ivanti addressed in January after they were exploited as zero-days against a "very limited number of customers." More recently, the Cybersecurity and Infrastructure Security Agency (CISA) ordered U.S. federal agencies last month to patch Ivanti systems on their networks after the company warned customers about a high-severity remote code execution EPMM flaw that was abused in zero-day attacks. Over the past several years, CISA has flagged 34 vulnerabilities across various Ivanti products as actively exploited in the wild, with 12 of them also targeted in ransomware attacks. Ivanti has a network of over 7,000 partners and over 3,000 employees, and its IT asset management solutions are used by over 40,000 customers worldwide. Overall prevention scores can hide what happens after initial access. Once attackers are using valid credentials, prevention drops sharply. The Blue Report 2026 measures defenses technique by technique across 338 million simulations run in customer production environments. Get the report
bleepingcomputer.comJun 11, 2026extracted
Critical Ivanti Sentry flaw allows root-level remote code execution (CVE-2026-10520)
Critical Ivanti Sentry flaw allows root-level remote code execution (CVE-2026-10520) Ivanti has patched two critical vulnerabilities (CVE-2026-10520 and CVE-2026-10523) in Ivanti Sentry and has urged customers to implement the fix right away. Though the vulnerabilities are not known to be actively exploited, security researchers have already released technical details about the former, which may be used by attackers to craft a working exploit. About Ivanty Sentry and the vulnerabilities Ivanti Sentry is a security gateway that acts as a gatekeeper between mobile devices outside of the corporate network and a company’s internal systems (e.g., email servers, internal applications). Ivanti Sentry is usually reachable from the internet, though it’s often deployed on an isolated subnetwork of the corporate network, to prevent attackers from using it for lateral movement into the latter. Unfortunately, compromising Sentry allows attackers to expose credentials, session tokens, and impersonate legitimate users, thus gaining access the organizations’ apps and email servers. Both of the fixed flaws are critical: CVE-2026-10520 is an OS command injection vulnerability that can allow remote unauthenticated users to achieve root-level remote code execution, and CVE-2026-10523 an authentication bypass flaw that allows them to create admin accounts on a vulnerable device. WatchTowr researchers have compared a vulnerable and patched version of Ivanti Sentry, and found that CVE-2026-10520 arises from Sentry having an API that’s designed to accept internal configuration commands, but accepts a command from anyone who could reach it over the internet, without having to authenticate first. Check your exposure and patch CVE-2026-10520 and CVE-2026-10523 affect Ivanty Sentry versions 10.5.1, 10.6.1, 10.7.0 and prior, and have been fixed in versions 10.5.2, 10.6.2 and 10.7.1. WatchTowr researchers have released a script that defenders can used to determine whether their environment is vulnerable. Ivanti has also shipped fixes for two high-severity vulnerabilities in Ivanti Endpoint Manager Mobile (EPMM). While EPMM flaws are regularly exploited by attackers, the only Sentry vulnerability known to have been leveraged by attackers is CVE-2023-38035, an authentication bypass bug that was exploited as a zero-day in 2023. UPDATE (June 11, 2026, 05:30 a.m. ET): The Shadowserver Foundation has observed a large amount of Ivanti Sentry CVE-2026-10520 exploitation attempts based on the public PoC by watchTowr, and say that at least two of the 19 vulnerable instances they are seeing have been backdoored. “However, all remaining likely compromised too,” the organization added. “While our detection is on the lowish side due to multiple Ivanti Sentry instances not reachable in our scans (blocklisted?), if you have not patched now you are most likely compromised.” Subscribe to our breaking news e-mail alert to never miss out on the latest breaches, vulnerabilities and cybersecurity threats. Subscribe here!
helpnetsecurity.comJun 10, 2026extracted
Ivanti tells Sentry customers to patch now as critical bugs hit 10.0 and 9.9
SYSTEMS What Nvidia's first Groq 3 LPU benchmarks tell us about its $20B gambleGemma 4 31B performance tests offer a best-case scenario for next-gen dataflow accelerators ON-PREM US datacenters tripled their water footprint in 10 years... and those are figures from the start of the AI boom. It can only be worse now. Silo-ed reporting isn't helping ai and ML AI slop is good for business if you know what you're doingYour irresponsibility is someone else's opportunity SAAS Salesforce partners not seeing meaningful revenue from Agentforce AI platform, report saysShow us the money ai and ml AI companies are burning books, advocates complain to FTCFahrenheit 203, the temperature GPUs stop gorging on literature Security Russians are posing as Signal support to launch phishing attacksPLUS: US takes down Iranian propaganda sites; Marketing company asks 'Why Do We Have Your Information?' And more! Security Microsoft patches failed to fix on-prem SharePoint, which is now under zero-day attackPLUS: China upgrades smartphone surveillance tools; Ring eases anti-snooping stance; and more Black Hat and DEF CON DEF CON Franklin project enlists hackers to harden critical infrastructureVoting village reports have been so successful, says Jeff Moss, that the whole of DEF CON will now be included Security EQT buys majority share in Swiss cybersecurity biz AcronisWent at equivalent of $3.5B+ valuation for entire firm, though portion sold not specified Malware Month Ten years since the first corp ransomware, Mikko Hyppönen sees no end in sightOn the plus side, infosec's a good bet for a long, stable career Emperor Penguin Linus Torvalds banishes a bug – with a botThe lad himself finds and fixes a tricky one… or does he? FOSS smashed one Microsoft monopoly. After 20 years of failure, it's time to smash anotherWord up GNOME can look like Windows – and Flashback can do it without extensionsNew 'Simple-taskbar' is an option, but there's a simpler, stabler way A moment of silence, please, for the final release of Debian on x86-32New Debian versions hit FOSSland in the form of 13.6 and 12.15 Baddies caught exploiting extensions bugs with perfect 10 scores on vulnerable Joomla websitesFlaws in iCagenda, Balbooa Forms extensions can impact open source CMS that powers a million sites worldwide Frame: A new X11 server – implemented directly in assemblyJoins yserver, Phoenix, and of course XLibre – and outlier Arcan
theregister.comJun 10, 2026extracted
Ivanti: Max severity Sentry flaw allows code execution as root
Security software company Ivanti has released patches to address two critical vulnerabilities in its Sentry secure mobile gateway solution, including a maximum-severity flaw that enables remote attackers to execute code with root privileges. Formerly known as MobileIron Sentry, Ivanti Sentry is a security gateway appliance that secures traffic between back-end corporate systems and remote mobile devices. Tracked as CVE-2026-10520, the maximum-severity vulnerability stems from an OS command injection weakness. The second Sentry security flaw patched on Tuesday (tracked as CVE-2026-10523) is a critical authentication bypass that can be exploited remotely by unauthenticated attackers to create rogue administrative accounts and gain full administrative access. Ivanti patched both security issues on Tuesday with the release of Sentry versions R10.5.2, R10.6.2, and R10.7.1. Luckily, the company said it has no evidence that the two vulnerabilities are being exploited in the wild and advised admins to upgrade their systems to protect against potential attacks. "We are not aware of any customers being exploited by these vulnerabilities at the time of disclosure," Ivanti said. "Currently, there is no known public exploitation of this vulnerability that could be used to provide a list of indicators of compromise." In recent years, Ivanti vulnerabilities have often been targeted in attacks because they provide an easy way for cybercriminals to breach targets' enterprise networks and steal sensitive corporate and customer data. For instance, most recently, the Cybersecurity and Infrastructure Security Agency (CISA) ordered U.S. federal agencies in May to patch their Ivanti devices after the company warned customers to immediately patch a high-severity remote code execution vulnerability in Endpoint Manager Mobile (EPMM) that was exploited in zero-day attacks. Multiple other Ivanti zero-days have been exploited in recent years to breach a wide range of targets, including government agencies worldwide, including two other critical EPMM vulnerabilities addressed by Ivanti in January after being exploited as zero-days in attacks against a "very limited number of customers." In total, CISA has tagged 34 vulnerabilities across various Ivanti products as actively exploited in attacks over the past several years, with 12 of them also used in ransomware attacks. Ivanti's IT asset management solutions are used by over 40,000 clients worldwide and are supported by a network of over 7,000 partners and over 3,000 employees. Overall prevention scores can hide what happens after initial access. Once attackers are using valid credentials, prevention drops sharply. The Blue Report 2026 measures defenses technique by technique across 338 million simulations run in customer production environments. Get the report
bleepingcomputer.comJun 10, 2026extracted
NCSC-2026-0135 [1.00] [H/H] Kwetsbaarheden verholpen in Ivanti Endpoint Manager Mobile
Ivanti heeft vijf kwetsbaarheden verholpen in Endpoint Manager Mobile (EPMM), ook wel bekend als MobileIron. De kwetsbaarheid met het kenmerk CVE-2026-6973 stelt een geauthenticeerde kwaadwillende met administratieve toegang in staat om op afstand willekeurige code uit te voeren met beheerdersrechten. Van de kwetsbaarheid met kenmerk CVE-2026-6973 meldt Ivanti dat deze actief is misbruikt bij een zeer beperkt aantal klanten. Om succesvol misbruik te bewerkstelligen moet de kwaadwillende beschikken over valide inloggegevens van een account met adminrechten. Ivanti geeft aan dat klanten die het advies in januari hebben opgevolgd om hun inloggegevens te vernieuwen, aanzienlijk minder risico lopen. De kwetsbaarheid met CVE-2026-5786 stelt een geauthenticeerde kwaadwillende op afstand in staat om beheertoegang te verkrijgen. De kwetsbaarheid met CVE-2026-5787 stelt een niet-geauthenticeerde kwaadwillende in staat om zich voor te doen als een geregistreerd Sentry systeem, om zodoende door een Certificate Authority (CA) ondertekende client certificaten te verkrijgen. De kwetsbaarheid CVE-2026-5788 stelt een niet-geauthenticeerde kwaadwillende op afstand in staat om willekeurige code uit te voeren. De kwetsbaarheid CVE-2026-7821 stelt een niet-geauthenticeerde kwaadwillende in staat om een apparaat te registreren aan een set van niet-geregistreerde apparaten en toegang te verkrijgen tot (gevoelige) gegevens. Het NCSC verwacht dat op korte termijn Proof-of-Concept code publiek beschikbaar komt. Dit vergroot de kans grootschalig misbruik aanzienlijk.
advisories.ncsc.nlMay 7, 2026extracted
DataBahn brings AI-driven intelligence into the security pipeline
DataBahn brings AI-driven intelligence into the security pipeline DataBahn.ai has announced Autonomous In-Stream Data Intelligence (AIDI), a new operating model for security data pipelines in which data is continuously interpreted, validated, and acted on in real time as it flows. Building on its AI-native foundation, DataBahn advances the pipeline from intelligent data preparation to an active system of in-stream decision-making, enabling organizations to detect issues earlier, adapt dynamically and ensure data is trusted before it reaches downstream systems. DataBahn is also introducing the DataBahn Agent Farm, a coordinated system of specialized AI agents that operationalize AIDI across the data lifecycle, continuously building, validating, optimizing and protecting data in-stream. The impact of these enhancements on security operations teams is immediate and measurable. Early design partners using AIDI have compressed SIEM onboarding timelines from months to days through AI-driven connectors that automatically normalize, enrich and route telemetry from more than 500 sources. Organizations have optimized log volume by 40 to 70 percent without sacrificing security value, while eliminating blind spots caused by silent data loss and misconfigured pipelines. The result is clean, enriched and contextually complete data delivered in real time, ready for detection, investigation and response the moment it arrives at its destination. The DataBahn platform takes an AI-native approach to the security data pipeline, embedding intelligence directly into how data is ingested, transformed and routed. That approach has enabled organizations to eliminate manual data engineering, accelerate SIEM onboarding and bring structure and control to rapidly growing telemetry. AIDI represents the next stage of that architecture, and with it, pipelines can now understand, analyze, detect, decide and act on data as it flows. AIDI represents an evolution in security that DataBahn calls “shift up.” Rather than waiting for data to land in a SIEM or analytics platform before applying logic to it, shift up moves interpretation, enrichment and decision-making into the pipeline itself. The concept parallels the transformation that reshaped enterprise data engineering a generation ago with the advent of ETL workflows. AIDI applies a similar inversion to security telemetry: the intelligence work that once happened after delivery now happens in transit, so that data arrives at its destination already normalized, classified and ready for use. “We have always believed that intelligence belongs inside the pipeline, not bolted on after the fact,” said Nanda Santhana, CEO of DataBahn. “Autonomous In-Stream Data Intelligence is the natural next step. The pipeline no longer just prepares data. It understands context, detects gaps and makes real-time decisions. That is how you evolve from data movement to data intelligence.” How Autonomous In-Stream Data Intelligence works AIDI operates as a continuously running intelligence layer embedded in the DataBahn pipeline. As telemetry enters the platform from cloud, hybrid and SaaS environments, the system performs several operations simultaneously. It interprets each data stream against its known context, including source identity, asset classification, environment topology and historical behavior patterns. It then applies schema normalization and enrichment automatically, eliminating the manual parser creation and brittle scripting that have historically slowed SIEM onboarding. Based on the content and risk profile of each stream, AIDI determines how data should be routed, enriched, suppressed or protected, directing high-fidelity detection data to the analytics tier and high-volume retention data to lower-cost storage. Throughout this process, specialized AI agents monitor for coverage gaps, schema drift, data loss and policy violations, taking corrective action without waiting for human intervention. For organizations that have standardized on Microsoft Sentinel or other leading SIEM platforms, AIDI is designed to accelerate time to value from those investments. Building on DataBahn’s recently announced expanded partnership with Microsoft, AIDI applies continuous intelligence to every data stream entering the SIEM. The DataBahn Agent Farm As part of the AIDI platform, DataBahn is also introducing the DataBahn Agent Farm, a set of specialized AI agents that extend the platform’s capabilities across the data lifecycle. Each agent handles a distinct operational function, giving security teams continuous, hands-off coverage across ingestion, validation, mapping and protection: Forge (Build): Automatically creates and maintains connectors and integrations, accelerating onboarding of new data sources. Atlas (Map): Builds a real-time asset inventory from telemetry, providing deep context across devices, identities and environments. Compass (Guide): Maps data against MITRE ATT&CK to identify detection gaps and strengthen security posture. Pulse (Monitor): Tracks data health, freshness and schema drift to keep pipelines reliable and performant. Signal (Validate): Verifies that data reaches its intended destinations completely and accurately, eliminating blind spots. Sentry (Protect): Detects and enforces controls on sensitive data in-stream, enabling real-time data security and compliance. Multiple tiers based on data maturity Recognizing that organizations are at different stages of their data maturity, DataBahn offers a tiered adoption model for AIDI: Foundation: Operational Data Pipelines. High-performance pipelines with built-in data engineering and observability. Organizations gain structured and cost-optimized data with faster onboarding of new sources. AI Assist: Intelligent Data Insights. AI agents provide continuous visibility into data quality, pipeline integrity and security coverage, surfacing gaps, blind spots and validation issues without taking direct action. AI Autonomy: Self-Operating Data Fabric. The full power of AIDI, where AI agents move from insight to action, enabling autonomous connector creation, self-healing pipelines, inline data protection and continuous adaptation to evolving environments. With AIDI, DataBahn’s pipeline continues to integrate with leading SIEM, observability and AI platforms, now delivering validated, enriched and context-aware data wherever it is needed. By converting the pipeline into an active intelligence layer, organizations can decouple data preparation from analytics, build a trusted and AI-ready data foundation and scale operations without increasing complexity.
helpnetsecurity.comMar 26, 2026extracted
Guerra ibrida, operazioni di sabotaggio russo contro infrastrutture critiche: ecco le contromisure
Il rapporto, pubblicato dall’International Institute for Strategic Studies nell’agosto 2025, ha posto l’attenzione su una dinamica di crescente rilevanza per la sicurezza europea: l’intensificarsi delle operazioni di sabotaggio condotte dalla Federazione Russa contro infrastrutture critiche civili e militari. L’analisi, fondata su dati raccolti da fonti pubbliche, mostra come tali azioni non costituiscano episodi isolati, ma parte di una strategia più ampia volta a ridurre la resilienza europea e a condizionare le posizioni politiche degli Stati membri nei confronti del conflitto in Ucraina. Indice degli argomenti Il documento sottolinea come il sabotaggio rappresenti un pilastro della cosiddetta “guerra non convenzionale” russa, condotta in parallelo alle operazioni militari. L’obiettivo non è soltanto quello di generare danni materiali, ma anche di alimentare un clima di incertezza e di minaccia permanente. L’Europa, con la sua fitta rete di infrastrutture interconnesse – energetiche, logistiche, di telecomunicazione e di supporto alle operazioni militari – costituisce un terreno particolarmente vulnerabile a questo tipo di attività. Il rapporto evidenzia che nel 2024 i casi accertati di sabotaggio contro infrastrutture critiche europee hanno registrato un incremento del 246% rispetto all’anno precedente, più che triplicando il numero di episodi documentati. Una dinamica che conferma l’esistenza di una campagna su larga scala, piuttosto che di azioni occasionali. L’anno successivo ha mostrato un’apparente contrazione, che gli analisti collegano a fattori sia politici che operativi: la necessità di calibrare il livello di pressione in funzione del contesto internazionale, la possibilità di temporanee difficoltà logistiche o di una riallocazione delle risorse verso altri fronti operativi. Un aspetto centrale riguarda il modello operativo utilizzato. Dopo le espulsioni di circa 600 funzionari russi dall’Europa nel 2022 – di cui circa 400 appartenenti ai servizi di intelligence – le agenzie di Mosca hanno progressivamente adottato modalità indirette, facendo ricorso a intermediari reclutati online. Si tratta di individui o piccoli gruppi spesso privi di una preparazione professionale di alto livello, ma disposti a compiere atti di sabotaggio minore – incendi dolosi, danneggiamenti, ricognizioni fotografiche – in cambio di compensi. Questa scelta riduce i rischi per la catena di comando russa e rende più difficile attribuire con certezza le responsabilità, aumentando al contempo il numero di operazioni possibili grazie a un approccio a basso costo e ad alta frequenza. Gli obiettivi principali individuati includono centrali elettriche, sottostazioni, linee ferroviarie, depositi logistici e impianti di telecomunicazione. In diversi casi sono stati presi di mira asset connessi al supporto militare occidentale a Kyiv, come basi di stoccaggio e nodi di trasporto. Tuttavia, la logica non si esaurisce nel perimetro strettamente militare: il danneggiamento di infrastrutture civili ad alto valore simbolico o economico contribuisce a generare costi aggiuntivi per i governi europei e a indebolire la percezione di sicurezza da parte dei cittadini. Il dominio marittimo rappresenta un ulteriore ambito di particolare attenzione. Cavi sottomarini e gasdotti sono stati oggetto di attività di ricognizione e, in alcuni casi, di danneggiamenti attribuiti con livelli di probabilità variabili, ma comunque riconducibili a operazioni di sabotaggio. Il rapporto ricorda che la riparazione di un singolo cavo può richiedere settimane e investimenti di decine di milioni di euro, mentre l’attribuzione delle responsabilità rimane complessa a causa della difficoltà di monitorare aree estese e profonde. Il rischio per il traffico dati transatlantico e per le forniture energetiche europee rende questa tipologia di operazioni una delle più critiche nel lungo termine. L’analisi dell’IISS sottolinea che l’elemento più problematico per la difesa europea è la combinazione tra basso costo delle operazioni e alto costo delle contromisure. Sorvegliare costantemente migliaia di chilometri di cavi, linee elettriche e snodi logistici richiede risorse ingenti, mentre la realizzazione di un atto di sabotaggio può essere affidata a soggetti con competenze limitate. Si genera così un rapporto di asimmetria che favorisce l’attaccante, in grado di saturare le capacità di difesa degli Stati presi di mira. Le risposte messe in campo dalle istituzioni europee e dalla Nato hanno compreso il lancio di iniziative dedicate, come la creazione di task force per la protezione delle infrastrutture critiche e la realizzazione di esercitazioni congiunte. Operazioni come Baltic Sentry – a guida NATO – e NorthSeal – uno sforzo congiunto di Paesi affacciati sul Mare del Nord – si focalizzano sul monitoraggio delle infrastrutture marittime e sul rafforzamento della cooperazione regionale. Parallelamente, è aumentata la disponibilità a rendere pubblici i risultati delle indagini di attribuzione, con l’obiettivo di rafforzare la deterrenza e la consapevolezza pubblica. Il rapporto rileva come l’approccio complessivo, per proteggersi dal sabotaggio russo contro infrastrutture critiche, rimanga prevalentemente reattivo. La protezione si basa soprattutto sulla deterrenza per negazione ovvero sull’aumento dei livelli di sorveglianza e protezione fisica, mentre la deterrenza per punizione rimane limitata da vincoli politici e legali che impediscono risposte rapide e proporzionate alle operazioni ostili. La frammentazione tra iniziative nazionali e il coordinamento ancora incompleto a livello europeo contribuiscono a mantenere un divario tra la velocità delle minacce e quella delle contromisure. Sul piano della resilienza, il documento invita a considerare un approccio più integrato, che tenga conto non soltanto degli aspetti militari e di intelligence, ma anche delle vulnerabilità civili e industriali. Le interdipendenze tra sistemi energetici, reti di telecomunicazione e logistica possono amplificare gli effetti di un singolo sabotaggio, generando conseguenze sistemiche anche in assenza di danni fisici su larga scala. In questo contesto, l’impiego di simulazioni “what if” permette di testare scenari ipotetici e valutare la capacità di assorbimento delle reti, fornendo indicazioni utili per la pianificazione della continuità operativa e per la definizione di soluzioni alternative in grado di limitare l’impatto di eventuali interruzioni. L’analisi conclude che la scala e la natura delle operazioni di sabotaggio in corso rappresentano una sfida di lungo periodo per la sicurezza europea. Non si tratta soltanto di proteggere singoli asset, ma di rafforzare la resilienza complessiva delle società europee a fronte di un modello di minaccia che unisce convenzionale e non convenzionale, fisico e digitale, diretto e per procura. La capacità di affrontare questa sfida richiede un equilibrio tra prevenzione, sorveglianza e cooperazione multilaterale, con l’obiettivo di ridurre l’asimmetria che oggi favorisce gli attori ostili.
cybersecurity360.itOct 2, 2025extracted
Submarine cable security is all at sea, and UK govt 'too timid' to act, says report
FEATURE The first transatlantic cable, laid in 1858, delivered a little over 700 messages before promptly dying a few weeks later. 167 years on, the undersea cables connecting the UK to the outside world process £220 billion in daily financial transactions. Now, the UK Parliament's Joint Committee on National Security Strategy (JCNSS) has told the government that it has to do a better job of protecting them. The Committee's report, released on September 19, calls the government "too timid" in its approach to protecting the cables that snake from the UK to various destinations around the world. It warns that "security vulnerabilities abound" in the UK's undersea cable infrastructure, when even a simple anchor-drag can cause major damage. There are 64 cables connecting the UK to the outside world, according to the report, carrying most of the country's internet traffic. Satellites can't shoulder the data volumes involved, are too expensive, and only account for around 5 percent of traffic globally. These cables are invaluable to the UK economy, but they're also difficult to protect. They are heavily shielded in the shallow sea close to those points. That's because accidental damage from fishing operations and other vessels is common. On average, around 200 cables suffer faults each year. But as they get further out, the shielding is less robust. Instead, the companies that lay the cables rely on the depth of the sea to do its job (you'll be pleased to hear that sharks don't generally munch on them). The report praises a strong cable infrastructure, and admits that in some areas at least we have the redundancy in the cable infrastructure to handle disruptions. For example, it notes that 75 percent of UK transatlantic traffic routes through two cables that come ashore in Bude, Cornwall. That seems like quite the vulnerability, but it acknowledges that we have plenty of infrastructure to route around if anything happened to them. There is "no imminent threat to the UK's national connectivity," it soothes. But it simultaneously cautions against adopting what it describes as "business-as-usual" views in the industry. The government "focuses too much on having 'lots of cables' and pays insufficient attention to the system's actual ability to absorb unexpected shocks," it frets. It warns that "the impacts on connectivity would be much more serious," if onward connections to Europe suffered as part of a coordinated attack. "While our national connectivity does not face immediate danger, we must prepare for the possibility that our cables can be threatened in the event of a security crisis," it says. Reds on the sea bed Who is the most likely to mount such an attack, if anyone? Russia seems front and center, according to experts. It has reportedly been studying the topic for years. Keir Giles, director at The Centre for International Cyber Conflict and senior consulting fellow of the Russia and Eurasia Programme at Chatham House, argues that Russia has a long history of information warfare that stepped up after it annexed Crimea in 2014. "The thinking part of the Russian military suddenly decided 'actually, this information isolation is the way to go, because it appears to win wars for us without having to fight them'," Giles says, adding that this approach is often combined with choke holds on land-based information sources. Cutting off the population in the target area from any source of information other than what the Russian troops feed them achieves results at low cost. In a 2021 paper he co-wrote for the NATO Cooperative Cyber Defence Centre of Excellence, he pointed to the Glavnoye upravleniye glubokovodnykh issledovaniy (Main Directorate for Deep-Water Research, or GUGI), a secretive Russian agency responsible for analyzing undersea cables for intelligence or disruption. According to the JCNSS report, this organization operates the Losharik, a titanium-hulled submarine capable of targeting cables at extreme depth. Shenanigans under the sea You don't need a fancy submarine to snag a cable, as long as you're prepared to do it in plain sight closer to the coast. The JNCSS report points to several incidents around the UK and the Baltics. November last year saw two incidents. In the first, Chinese-flagged cargo vessel Yi Peng 3 dragged its anchor for 300km and cut two cables between Sweden and Lithuania. That same month, the UK and Irish navies shadowed Yantar, a Russian research ship loitering around UK cable infrastructure in the Irish sea. The following month saw Cook Islands-flagged ship Eagle S damage one power cable and three data cables linking Finland and Estonia. This May, unaffiliated vessel Jaguar approached an underseas cable off Estonia and was escorted out of the country's waters. The real problem with brute-force physical damage from vessels is that it's difficult to prove that it's intentional. On one hand, it's perfect for an aggressor's plausible deniability, and could also be a way to test the boundaries of what NATO is willing to tolerate. On the other, it could really be nothing. "Attribution of sabotage to critical undersea infrastructure is difficult to prove, a situation significantly complicated by the prevalence of under-regulated and illegal shipping activities, sometimes referred to as the shadow fleet," a spokesperson for NATO told us. "I'd push back on an assertion of a coordinated campaign," says Alan Mauldin, research director at analyst company TeleGeography, which examines undersea cable infrastructure warns. He questions assumptions that the Baltic cable damage was anything other than a SNAFU. The Washington Post also reported comment from officials on both sides of the Atlantic that the Baltic anchor-dragging was probably accidental. Giles scoffs at that. "Somebody had been working very hard to persuade countries across Europe that this sudden spate of cables being broken in the Baltic Sea, one after another, was all an accident, and they were trying to say that it's possible for ships to drag their anchors without noticing," he says. One would hope that international governance frameworks could help. The UN Convention on the Law of the Sea [PDF] has a provision against messing with undersea cables, but many states haven't enacted the agreement. In any case, plausible deniability makes things more difficult. "The main challenge in making meaningful governance reforms to secure submarine cables is figuring out what these could be. Making fishing or anchoring accidents illegal would be disproportionate," says Anniki Mikelsaar, doctoral researcher at Oxford University's Oxford Internet Institute. "As there might be some regulatory friction, regional frameworks could be a meaningful avenue to increase submarine cable security." The difficulty in pinning down intent hasn't stopped NATO from stepping in. In January it launched Baltic Sentry, an initiative to protect undersea infrastructure in the region. That effort includes frigates, patrol aircraft, and naval drones to keep an eye on what happens both above and below the waves. Preparing for the worst Regardless of whether vessels are doing this deliberately or by accident, we have to be prepared for it, especially as cable installation shows no sign of slowing. Increasing bandwidth needs will boost global cable kilometers by 48 percent between now and 2040, says TeleGeography, adding that annual repairs will increase 36 percent between now and 2040. "Many cable maintenance ships are reaching the end of their design life cycle, so more investment into upgrading the fleets is needed. This is important to make repairs faster," says Mikelsaar. There are 62 vessels capable of cable maintenance today, and TeleGeography predicts that'll be enough for the next 15 years. However, it takes time to build these vessels and train the operators, meaning that we'll need to start delivering new vessels soon. The problem for the UK is that it doesn't own any of that repair capacity, says the JNSS. It can take a long time to travel to a cable and repair it, and ships can only work on one at a time. The Committee reported that the UK doesn't own any sovereign repair capacity, and advises that it gets some, prescribing a repair ship by 2030. "This could be leased to industry on favorable terms during peacetime and made available for Government use in a crisis," it says, adding that the Navy should establish a set of reservists that will be trained and ready to operate the vessel. Sir Chris Bryant MP, the Minister for Data Protection and Telecoms, told the Committee it that it was being apocalyptic and "over-egging the pudding" by examining the possibility of a co-ordinated attack. "We disagree," the Committee said in the report, arguing that the security situation in the next decade is uncertain. "Focusing on fishing accidents and low-level sabotage is no longer good enough," the report adds. "The UK faces a strategic vulnerability in the event of hostilities. Publicly signaling tougher defensive preparations is vital, and may reduce the likelihood of adversaries mounting a sabotage effort in the first place." To that end, it has made a battery of recommendations. These include building the risk of a coordinated campaign against undersea infrastructure into its risk scenarios, and protecting the stations - often in remote coastal locations - where the cables come onto land. The report also recommends that the Department for Science, Innovation and Technology (DSIT) ensures all lead departments have detailed sector-by-sector technical impact studies addressing widespread cable outages. "Government works around the clock to ensure our subsea cable infrastructure is resilient and can withstand hostile and non-hostile threats," DSIT told El Reg, adding that when breaks happen, the UK has some of the fastest cable repair times in the world, and there's usually no noticeable disruption." "Working with NATO and Joint Expeditionary Force allies, we're also ensuring hostile actors cannot operate undetected near UK or NATO waters," it added. "We're deploying new technologies, coordinating patrols, and leading initiatives like Nordic Warden alongside NATO's Baltic Sentry mission to track and counter undersea threats." Nevertheless, some seem worried. Vili Lehdonvirta, head of the Digital Economic Security Lab (DIESL) and professor of Technology Policy at Aalto University, has noticed increased interest from governments and private sector organizations alike in how much their daily operations depend on oversea connectivity. He says that this likely plays into increased calls for digital sovereignty. "The rapid increase in data localization laws around the world is partly explained by this desire for increased resilience," he says. "But situating data and workloads physically close as opposed to where it is economically efficient to run them (eg. because of cheaper electricity) comes with an economic cost." So the good news is that we know exactly how vulnerable our undersea cables are. The bad news is that so does everyone else with a dodgy cargo ship and a good poker face. Sleep tight. ®
go.theregister.comSep 29, 2025extracted
Massive npm infection: the Shai-Hulud worm and patient zero
Introduction The modern development world is almost entirely dependent on third-party modules. While this certainly speeds up development, it also creates a massive attack surface for end users, since anyone can create these components. It is no surprise that malicious modules are becoming more common. When a single maintainer account for popular modules or a single popular dependency is compromised, it can quickly turn into a supply chain attack. Such compromises are now a frequent attack vector trending among threat actors. In the last month alone, there have been two major incidents that confirm this interest in creating malicious modules, dependencies, and packages. We have already discussed the recent compromise of popular npm packages. September 16, 2025 saw reports of a new wave of npm package infections, caused by the self-propagating malware known as Shai-Hulud. Shai-Hulud is designed to steal sensitive data, expose private repositories of organizations, and hijack victim credentials to infect other packages and spread on. Over 500 packages were infected in this incident, including one with more than two million weekly downloads. As a result, developers who integrated these malicious packages into their projects risk losing sensitive data, and their own libraries could become infected with Shai-Hulud. This self-propagating malware takes over accounts and steals secrets to create new infected modules, spreading the threat along the dependency chain. Technical details The worm’s malicious code executes when an infected package is installed. It then publishes infected releases to all packages the victim has update permissions for. Once the infected package is installed from the npm registry on the victim’s system, a special command is automatically executed. This command launches a malicious script over 3 MB in size named bundle.js, which contains several legitimate, open-source work modules. Key modules within bundle.js include: Library for interacting with AWS cloud services GCP module that retrieves metadata from the Google Cloud Platform environment Functions for TruffleHog, a tool for scanning various data sources to find sensitive information, specifically secrets Tool for interacting with the GitHub API The JavaScript file also contains network utilities for data transfer and the main operational module, Shai-Hulud. The worm begins its malicious activity by collecting information about the victim’s operating system and checking for an npm token and authenticated GitHub user token in the environment. If a valid GitHub token is not present, bundle.js will terminate. A distinctive feature of Shai-Hulud is that most of its functionality is geared toward Linux and macOS systems: almost all malicious actions are performed exclusively on these systems, with the exception of using TruffleHog to find secrets. Exfiltrating secrets After passing the checks, the malware uses the token mentioned earlier to get information about the current GitHub user. It then runs the extraction function, which creates a temporary executable bash script at /tmp/processor.sh and runs it as a separate process, passing the token as an argument. Below is the extraction function, with strings and variable names modified for readability since the original source code was illegible. The bash script is designed to communicate with the GitHub API and collect secrets from the victim’s repository in an unconventional way. First, the script checks if the token has the necessary permissions to create branches and work with GitHub Actions. If it does, the script gets a list of all the repositories the user can access from 2025. In each of these, it creates a new branch named shai-hulud and uploads a shai-hulud-workflow.yml workflow, which is a configuration file for describing GitHub Actions workflows. These files are automation scripts that are triggered in GitHub Actions whenever changes are made to a repository. The Shai-Hulud workflow activates on every push. This file collects secrets from the victim’s repositories and forwards them to the attackers’ server. Before being sent, the confidential data is encoded twice with Base64. This unusual method for data collection is designed for a one-time extraction of secrets from a user’s repositories. However, it poses a threat not only to Shai-Hulud victims but also to ordinary researchers. If you search for “shai-hulud” on GitHub, you will find numerous repositories that have been compromised by the worm. The main bundle.js script then requests a list of all organizations associated with the victim and runs the migration function for each one. This function also runs a bash script, but in this case, it saves it to /tmp/migrate-repos.sh, passing the organization name, username, and token as parameters for further malicious activity. The bash script automates the migration of all private and internal repositories from the specified GitHub organization to the user’s account, making them public. The script also uses the GitHub API to copy the contents of the private repositories as mirrors. We believe these actions are intended for the automated theft of source code from the private repositories of popular communities and organizations. For example, the well-known company CrowdStrike was caught in this wave of infections. The worm’s self-replication After running operations on the victim’s GitHub, the main bundle.js script moves on to its next crucial stage: self-replication. First, the script gets a list of the victim’s 20 most downloaded packages. To do this, it performs a search query with the username from the previously obtained npm token: Next, for each of the packages it finds, it calls the updatePackage function. This function first attempts to download the tarball version of the package (a .TAR archive). If it exists, a temporary directory named npm-update-{target_package_name} is created. The tarball version of the package is saved there as package.tgz, then unpacked and modified as follows: The malicious bundle.js is added to the original package. A postinstall command is added to the package.json file (which is used in Node.js projects to manage dependencies and project metadata). This command is configured to execute the malicious script vianode bundle.js . The package version number is incremented by 1. The modified package is then re-packed and published to npm as a new version with the npm publish command. After this, the temporary directory for the package is cleared. Uploading secrets to GitHub Next, the worm uses the previously mentioned TruffleHog utility to harvest secrets from the target system. It downloads the latest version of the utility from the original repository for the specific operating system type using the following link: The worm also uses modules for AWS and Google Cloud Platform (GCP) to scan for secrets. The script then aggregates the collected data into a single object and creates a repository named “Shai-Hulud” in the victim’s profile. It then uploads the collected information to this repository as a data.json file. Below is a list of data formats collected from the victim’s system and uploaded to GitHub: Infection characteristics A distinctive characteristic of the modified packages is that they contain an archive named package.tar. This is worth noting because packages usually contain an archive with a name that matches the package itself. Through our research, we were able to identify the first package from which Shai-Hulud began to spread, thanks to a key difference. As we mentioned earlier, after infection, a postinstall command to execute the malicious script, node bundle.js, is written to the package.json file. This command typically runs immediately after installation. However, we discovered that one of the infected packages listed the same command as a preinstall command, meaning it ran before the installation. This package was ngx-bootstrap version 18.1.4. We believe this was the starting point for the spread of this infection. This hypothesis is further supported by the fact that the archive name in the first infected version of this package differed from the name characteristic of later infected packages (package.tar). While investigating different packages, we noticed that in some cases, a single package contained multiple versions with malicious code. This was likely possible because the infection spread to all maintainers and contributors of packages, and the malicious code was then introduced from each of their accounts. Infected libraries and CrowdStrike The rapidly spreading Shai-Hulud worm has infected many popular libraries that organizations and developers use daily. Shai-Hulud has infected over 500 popular packages in recent days, including libraries from the well-known company CrowdStrike. Among the infected libraries were the following: @crowdstrike/commitlint versions 8.1.1, 8.1.2 @crowdstrike/falcon-shoelace versions 0.4.1, 0.4.2 @crowdstrike/foundry-js versions 0.19.1, 0.19.2 @crowdstrike/glide-core versions 0.34.2, 0.34.3 @crowdstrike/logscale-dashboard versions 1.205.1, 1.205.2 @crowdstrike/logscale-file-editor versions 1.205.1, 1.205.2 @crowdstrike/logscale-parser-edit versions 1.205.1, 1.205.2 @crowdstrike/logscale-search versions 1.205.1, 1.205.2 @crowdstrike/tailwind-toucan-base versions 5.0.1, 5.0.2 But the event that has drawn significant attention to this spreading threat was the infection of the @ctrl/tinycolor library, which is downloaded by over two million users every week. As mentioned above, the malicious script exposes an organization’s private repositories, posing a serious threat to their owners, as this creates a risk of exposing the source code of their libraries and products, among other things, and leading to an even greater loss of data. Prevention and protection To protect against this type of infection, we recommend using a specialized solution for monitoring open-source components. Kaspersky maintains a continuous feed of compromised packages and libraries, which can be used to secure your supply chain and protect development from similar threats. For personal devices, we recommend Kaspersky Premium, which provides multi-layered protection to prevent and neutralize infection threats. Our solution can also restore the device’s functionality if it’s infected with malware. For corporate devices, we advise implementing a comprehensive solution like Kaspersky Next, which allows you to build a flexible and effective security system. This product line provides threat visibility and real-time protection, as well as EDR and XDR capabilities for investigation and response. It is suitable for organizations of any scale or industry. Kaspersky products detect the Shai-Hulud threat as HEUR:Worm.Script.Shulud.gen. In the event of a Shai-Hulud infection, and as a proactive response to the spreading threat, we recommend taking the following measures across your systems and infrastructure: Use a reliable security solution to conduct a full system scan. Audit your GitHub repositories: Check for repositories named shai-hulud . Look for non-trivial or unknown branches, pull requests, and files. Audit GitHub Actions logs for strings containing shai-hulud . Reissue npm and GitHub tokens, cloud keys (specifically for AWS and Google Cloud Platform), and rotate other secrets. Clear the cache and inventory your npm modules: check for malicious ones and roll back versions to clean ones. Check for indicators of compromise, such as files in the system or network artifacts. Indicators of compromise Files: bundle.js shai-hulud-workflow.yml Strings: shai-hulud Hashes: C96FBBE010DD4C5BFB801780856EC228 78E701F42B76CCDE3F2678E548886860 Network artifacts: https://webhook.site/bb8ca5f6-4175-45d2-b042-fc9ebb8170b7 Compromised packages: @ahmedhfarag/ngx-perfect-scrollbar @ahmedhfarag/ngx-virtual-scroller @art-ws/common @art-ws/config-eslint @art-ws/config-ts @art-ws/db-context @art-ws/di @art-ws/di-node @art-ws/eslint @art-ws/fastify-http-server @art-ws/http-server @art-ws/openapi @art-ws/package-base @art-ws/prettier @art-ws/slf @art-ws/ssl-info @art-ws/web-app @basic-ui-components-stc/basic-ui-components @crowdstrike/commitlint @crowdstrike/falcon-shoelace @crowdstrike/foundry-js @crowdstrike/glide-core @crowdstrike/logscale-dashboard @crowdstrike/logscale-file-editor @crowdstrike/logscale-parser-edit @crowdstrike/logscale-search @crowdstrike/tailwind-toucan-base @ctrl/deluge @ctrl/golang-template @ctrl/magnet-link @ctrl/ngx-codemirror @ctrl/ngx-csv @ctrl/ngx-emoji-mart @ctrl/ngx-rightclick @ctrl/qbittorrent @ctrl/react-adsense @ctrl/shared-torrent @ctrl/tinycolor @ctrl/torrent-file @ctrl/transmission @ctrl/ts-base32 @nativescript-community/arraybuffers @nativescript-community/gesturehandler @nativescript-community/perms @nativescript-community/sentry @nativescript-community/sqlite @nativescript-community/text @nativescript-community/typeorm @nativescript-community/ui-collectionview @nativescript-community/ui-document-picker @nativescript-community/ui-drawer @nativescript-community/ui-image @nativescript-community/ui-label @nativescript-community/ui-material-bottom-navigation @nativescript-community/ui-material-bottomsheet @nativescript-community/ui-material-core @nativescript-community/ui-material-core-tabs @nativescript-community/ui-material-ripple @nativescript-community/ui-material-tabs @nativescript-community/ui-pager @nativescript-community/ui-pulltorefresh @nstudio/angular @nstudio/focus @nstudio/nativescript-checkbox @nstudio/nativescript-loading-indicator @nstudio/ui-collectionview @nstudio/web @nstudio/web-angular @nstudio/xplat @nstudio/xplat-utils @operato/board @operato/data-grist @operato/graphql @operato/headroom @operato/help @operato/i18n @operato/input @operato/layout @operato/popup @operato/pull-to-refresh @operato/shell @operato/styles @operato/utils @teselagen/bio-parsers @teselagen/bounce-loader @teselagen/file-utils @teselagen/liquibase-tools @teselagen/ove @teselagen/range-utils @teselagen/react-list @teselagen/react-table @teselagen/sequence-utils @teselagen/ui @thangved/callback-window @things-factory/attachment-base @things-factory/auth-base @things-factory/email-base @things-factory/env @things-factory/integration-base @things-factory/integration-marketplace @things-factory/shell @tnf-dev/api @tnf-dev/core @tnf-dev/js @tnf-dev/mui @tnf-dev/react @ui-ux-gang/devextreme-angular-rpk @ui-ux-gang/devextreme-rpk @yoobic/design-system @yoobic/jpeg-camera-es6 @yoobic/yobi ace-colorpicker-rpk airchief airpilot angulartics2 another-shai browser-webdriver-downloader capacitor-notificationhandler capacitor-plugin-healthapp capacitor-plugin-ihealth capacitor-plugin-vonage capacitorandroidpermissions config-cordova cordova-plugin-voxeet2 cordova-voxeet create-hest-app db-evo devextreme-angular-rpk devextreme-rpk ember-browser-services ember-headless-form ember-headless-form-yup ember-headless-table ember-url-hash-polyfill ember-velcro encounter-playground eslint-config-crowdstrike eslint-config-crowdstrike-node eslint-config-teselagen globalize-rpk graphql-sequelize-teselagen json-rules-engine-simplified jumpgate koa2-swagger-ui mcfly-semantic-release mcp-knowledge-base mcp-knowledge-graph mobioffice-cli monorepo-next mstate-angular mstate-cli mstate-dev-react mstate-react ng-imports-checker ng2-file-upload ngx-bootstrap ngx-color ngx-toastr ngx-trend ngx-ws oradm-to-gql oradm-to-sqlz ove-auto-annotate pm2-gelf-json printjs-rpk react-complaint-image react-jsonschema-form-conditionals react-jsonschema-form-extras react-jsonschema-rxnt-extras remark-preset-lint-crowdstrike rxnt-authentication rxnt-healthchecks-nestjs rxnt-kue swc-plugin-component-annotate tbssnch teselagen-interval-tree tg-client-query-builder tg-redbird tg-seq-gen thangved-react-grid ts-gaussian ts-imports tvi-cli ve-bamreader ve-editor verror-extra voip-callkit wdio-web-reporter yargs-help-output yoo-styles
securelist.comSep 25, 2025extracted
Sentry’s AI code review automates testing and error detection across pull requests
Sentry’s AI code review automates testing and error detection across pull requests Sentry released the beta of AI code review, an AI-powered solution that identifies and fixes code issues before they reach production. Following its acquisitions of Codecov (2022) and Emerge Tools (2025), AI code review marks a step in Sentry’s expansion into the pre-release phase of software development. Like Sentry’s AI debugging agent Seer, AI code review leverages the power of artificial intelligence to predict errors, review pull requests (PRs) for accuracy, and even auto-generate unit tests, all before shipping code to production. “AI code review gives developers the edge to stop errors before they ever reach production,” said Milin Desai, CEO of Sentry. “AI has already reshaped how software is built, and with Seer we proved it could revolutionize debugging by root causing issues with over 94% accuracy and delivering context-aware fixes in seconds. Now Sentry users can benefit from that intelligence earlier in the build cycle, powered by Sentry’s deep context and code insights, so teams can ship cleaner code with speed and confidence.” AI code review is designed to bring speed, accuracy, and confidence to software development. Instead of catching errors only after code is deployed, developers can now prevent them from ever reaching production. Key capabilities include: Error prediction: Automatically flags high-confidence, high-impact issues in pull requests, showing developers where and why a bug will occur and suggesting actionable fixes. Smart PR review: Detects typos, formatting errors, and logical mistakes so human reviewers can focus on architecture and design decisions. Test generation: Uses AI to generate unit tests for code in a pull request, accelerating test coverage without draining developer time. “The only thing easier than debugging errors with Sentry is having fewer errors to debug in the first place,” said Rohan Bhaumik, Senior Product Manager at Sentry. “By combining predictive error detection with automated testing, AI code review reduces wasted time in code reviews, strengthens test coverage, and lets teams merge with confidence.” With AI code review, Sentry expands upstream into pre-release, uniting testing and observability to ensure stability across the software lifecycle. The benefits of Sentry AI code review include: Reduced downtime risk: Catch high-impact bugs earlier, avoiding costly production incidents. Faster release velocity: Streamlined code reviews and automated testing accelerate delivery. Improved developer productivity: Developers spend less time chasing typos and more time building features.
helpnetsecurity.comSep 24, 2025extracted