<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Credential-Reset on CuraSec</title><link>https://curasec.metacog.co.kr/tags/credential-reset/</link><description>Recent content in Credential-Reset on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 27 Oct 2026 16:34:51 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/credential-reset/index.xml" rel="self" type="application/rss+xml"/><item><title>DreamHost forces FTP/SFTP/email password resets amid ongoing incident</title><link>https://curasec.metacog.co.kr/insights/2026-10-27-dreamhost-forces-password-resets-in-ongoing-incident/</link><pubDate>Tue, 27 Oct 2026 16:34:51 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-27-dreamhost-forces-password-resets-in-ongoing-incident/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> If your org hosts anything on DreamHost, verify the forced credential resets completed for all FTP/SFTP and email accounts and review access logs since the incident began for any unauthorized file access.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> Confirm whether your organization uses DreamHost for any hosting services; if so, request an incident scope update from them and verify all affected credentials have been rotated by impacted teams.&lt;/li>
&lt;/ul></description></item></channel></rss>