Site icon WinCert

Cyberhaven Chrome extension breached

<p>On Christmas Eve&comma; Cyberhaven faced a significant cyberattack that compromised its Google Chrome extension&comma; exposing sensitive customer data&comma; including passwords and session tokens&period; The company revealed that the attack was likely part of a broader campaign targeting multiple organizations&period; The breach began when an employee fell victim to a phishing email&comma; unknowingly providing the attacker with credentials that granted access to Cyberhaven’s systems&period;<&sol;p>&NewLine;<p><img class&equals;"alignnone size-full wp-image-3104" src&equals;"https&colon;&sol;&sol;www&period;wincert&period;net&sol;wp-content&sol;uploads&sol;2019&sol;05&sol;hacker&lowbar;binary&period;jpg" alt&equals;"" width&equals;"640" height&equals;"426" &sol;><&sol;p>&NewLine;<p>Using these credentials&comma; the attacker infiltrated the company’s Google Chrome Web Store account and uploaded a malicious version of Cyberhaven’s Chrome extension&comma; 24&period;10&period;4&period; This tampered version was distributed to users with auto-update enabled on Chrome-based browsers&period; The rogue code was active between 1&colon;32 AM UTC on December 25 and 2&colon;50 AM UTC on December 26&period;<&sol;p>&NewLine;<p>Howard Ting&comma; Cyberhaven’s CEO&comma; praised the swift action of the company’s security team&comma; who detected the breach at 11&colon;54 PM UTC on Christmas Day and removed the compromised extension within an hour&period; &OpenCurlyDoubleQuote;I’m incredibly proud of our team&comma;” Ting stated&period; &OpenCurlyDoubleQuote;They set aside their holiday plans to prioritize our customers&comma; demonstrating the transparency and dedication that define our company&period;”<&sol;p>&NewLine;<p>Fortunately&comma; the attack did not extend to other core systems&comma; such as code-signing keys or CI&sol;CD pipelines&period; However&comma; Cyberhaven cautioned that attackers may have accessed cookies and active sessions for certain websites&period;<&sol;p>&NewLine;<p>The company advised users to take immediate precautions&colon; update to version 24&period;10&period;5 or later&comma; monitor activity logs for anomalies&comma; and reset or rotate passwords&comma; especially those not secured with FIDOv2&period;<&sol;p>&NewLine;

Exit mobile version