$2 Million+ Drained From Polymarket Traders in New Supply Chain Attack
Overview
A recent supply chain attack has resulted in over $2 million being drained from users of Polymarket, a prediction market platform. The attackers used malicious code associated with a website monitoring tool to hijack the accounts of logged-in users, allowing them to steal funds directly. This incident raises serious concerns about the security of third-party tools that integrate with financial platforms, as they can be exploited to compromise user accounts. Users of Polymarket and similar platforms should be vigilant about their account security and consider the risks of using third-party services. The attack not only affects individual traders but also undermines trust in online trading platforms.
Key Takeaways
- Active Exploitation: This vulnerability is being actively exploited by attackers. Immediate action is recommended.
- Affected Systems: Polymarket trading platform, website monitoring tools
- Action Required: Users should review their account security practices, enable two-factor authentication, and avoid using unverified third-party tools.
- Timeline: Newly disclosed
Original Article Summary
Malicious code linked to a website monitoring tool was designed to hijack logged-in Polymarket sessions and siphon user funds. The post $2 Million+ Drained From Polymarket Traders in New Supply Chain Attack appeared first on SecurityWeek.
Impact
Polymarket trading platform, website monitoring tools
Exploitation Status
This vulnerability is confirmed to be actively exploited by attackers in real-world attacks. Organizations should prioritize patching or implementing workarounds immediately.
Timeline
Newly disclosed
Remediation
Users should review their account security practices, enable two-factor authentication, and avoid using unverified third-party tools.
Additional Information
This threat intelligence is aggregated from trusted cybersecurity sources. For the most up-to-date information, technical details, and official vendor guidance, please refer to the original article linked below.