DreamHost and University of Copenhagen incidents reported
Two reported cyber incidents ·
In this episode
- DreamHost reacts to issue affecting some systems, reported
- University of Copenhagen hit by reported cyber incident
The facts
- DreamHost has been hit by a cyber incident.
- University of Copenhagen has been hit by a cyber incident.
Sources
The panel
Jordan Pike AI host
SC Media and Help Net Security report that DreamHost has been hit by a cyber incident.
Sam Kowalski AI analyst
Your SOC should start by pulling web server access logs and any file-manager audit trails. Look for unusual IPs, credential-spray patterns, and any signs of lateral movement toward customer data. Contain any suspicious sessions. Also verify that any file-manager settings haven’t been altered, and confirm that admin accounts require MFA.
Rina Takahashi AI analyst
Monitor any emerging intel that might link the activity to known actor groups, but avoid assumptions without confirmation. Keep an eye on any new chatter in underground forums that could hint at the tools used.
Sam Kowalski AI analyst
Looks like the attackers got the memo before we did.
Jordan Pike AI host
Now over to the university side of the story. We'll now shift focus to the university incident.
Jordan Pike AI host
Infosecurity Magazine and Help Net Security report that the University of Copenhagen has been hit by a cyber incident.
Sam Kowalski AI analyst
For an academic network, start with authentication logs and any research-data repositories. Spot anomalous credential use, especially from external addresses, and isolate affected subnets while you investigate. Check for any reused passwords that might have been exposed elsewhere, and verify backup snapshots are clean.
Rina Takahashi AI analyst
Monitor open-source intel feeds for indicators that might tie the activity to a known campaign. Also treat anything the attackers claim themselves as a claim, not a confirmation.
Sam Kowalski AI analyst
Given the uncertainty, I’d recommend treating the incident seriously and considering isolation of affected services while you investigate. Notify your compliance officer and prepare a brief for senior leadership.
Rina Takahashi AI analyst
I’d argue we should first gather evidence and confirm compromise before taking drastic isolation steps. Document findings thoroughly for future lessons learned.
Jordan Pike AI host
Bottom line: verify the integrity of your critical services, review access logs for anomalies, and apply any vendor guidance as soon as it becomes available. Finally, run a tabletop exercise to test your response plan.