Analyst assessment
DysruptionHub assesses with high confidence that Elsevier experienced malicious web-traffic redirection on Sept. 21, 2026. Cloudskope’s live checks found that Elsevier.com, Evolve.elsevier.com and Submit.elsevier.com sent visitors to a page branded “LAPSUS$ GROUP, Chapter II.” In a statement to DataBreaches.net, Elsevier confirmed that visitors to selected platforms were redirected to a third-party page and said its cybersecurity team restored normal service. The redirection is established. Elsevier later said a compromised credential initiated the incident; the operator and how the credential was obtained remain unestablished.
Operational significance
The redirect interrupted access to Elsevier’s company site, education portal and manuscript-submission portal for at least 78 minutes. KTVO reported that Truman State University nursing students were sent to the branded page while trying to use Elsevier for homework. That documents downstream educational disruption, not a breach of Truman’s systems. Grand Canyon University’s tech-support team reported an outage affecting Evolve and other Elsevier resources. Western Governors University nursing students reported that they could not reach Elsevier-linked quizzes and course materials. The GCU notice is institutional; the WGU evidence is student reporting, and neither establishes a breach of the schools’ systems. Sorami Consulting reported that a Gold Standard Drug Database authentication endpoint also redirected token requests, but its public account did not provide request logs or identify a patient-care interruption.
In a filing with the Idaho attorney general, Boise State University said it disabled single sign-on to Interfolio (Faculty 180) as a precaution and re-enabled it at 8:30 a.m. Sept. 22. The university said Interfolio was not affected and no university-hosted service or data was shown compromised. Boise’s restriction continued after the Elsevier web redirects had stopped.
Current status
Cloudskope found the observed redirects cleared Sept. 21, and Elsevier said it restored normal service. Boise State restored its precautionary sign-on restriction the following morning. Elsevier’s trust-center statement describes the event as contained and effectively addressed.
Moffitt Cancer Center’s library retains an undated notice describing a precautionary block on Elsevier resources. The notice still says Elsevier has not issued a public statement, a premise superseded by Elsevier’s published findings. Its continued display does not establish that the block remains enforced. It does not establish a Moffitt breach or patient-care interruption.
Operational disruption is assessed as presumed resolved as of Nov. 2. Current downstream access restrictions and the date every precautionary block ended remain unconfirmed.
Confidence and uncertainty
Confidence is high that the redirects occurred and disrupted access, based on live checks, a university support notice, affected-user reporting and Elsevier’s acknowledgement. The 78-minute duration is a verified minimum, not a precise start-to-finish measure. Sorami’s additional API-endpoint observation remains a single-source report, and it does not establish a clinical-service outage or compromise of core systems. Elsevier said its investigation found no indication that core platforms, customer data, research content or operational systems were compromised; that is not a final public technical report ruling out every possible exposure.
Elsevier’s trust-center statement, updated Oct. 16, said the compromised credential or key had been deprecated and replaced. It said an external forensic firm reviewed extensive logs and system artifacts supplied by Elsevier and found unauthorized activity limited to approximately 15 minutes Sept. 21, with no evidence of access to infrastructure or product platforms, data exfiltration or activity outside that window. Those are attributed findings within the firm’s review. The approximately 15-minute activity window differs from Cloudskope’s minimum 78-minute observation of redirects; the public accounts do not explain that timing difference. Neither duration establishes the complete user-impact period, including downstream precautionary blocks.
The redirect creates a low-confidence association with the “LAPSUS$ Chapter II” persona because Elsevier traffic reached its branded page. It is not an Elsevier-specific actor claim: the page named another victim and an unidentified future target, not Elsevier. Securonix found that the page was staged before the Elsevier redirect and could not tie its operator to the original LAPSUS$ group. The public evidence does not establish who controlled the redirect, ransomware, an Elsevier ransom demand or data theft. The Maryland Heights, Missouri, location is an Elsevier-listed U.S. office, not a documented site of office-specific disruption.
Analytic gaps
Elsevier identified a compromised credential or key but has not publicly explained how it was obtained, which routing control it enabled or who used it. The public record does not reconcile the forensic activity window with the longer observed redirect duration, or identify when every downstream precautionary restriction ended. The number of affected users and the full scope of any additional redirected endpoints remain unverified.