Polycule Faces Apparent Rug Pull Amid Fund Withdrawal Crisis

WhaleWatcher · 2026-01-28T13:07:50+00:00

The Polycule trading bot faces serious security issues after a possible rug pull has left users unable to access funds. Initial claims of a hacker attack have not reassured investors, who are frustrated by a lack of communication from the development team.

WhaleWatcher

2026-01-28 13:07:50

Abstract generation in progress

Polycule, a Polymarket-based trading bot, is now at the center of significant security concerns following what appears to be a rug pull situation that has left users in financial limbo. According to reports surfaced on January 12th, the project has become embroiled in a controversy that threatens the funds of multiple investors.

Security Breach or Exit Scam? Unraveling the Polycule Incident

The team initially attributed the crisis to a hacker attack, claiming that roughly $230,000 in user assets were compromised. Following the alleged breach, the bot went offline, with the Polycule team promising to deliver security patches and conduct thorough code reviews by the weekend. However, the distinction between a targeted cyberattack and an orchestrated rug pull remains unclear, with community members increasingly questioning the legitimacy of the team’s explanation.

Users Trapped: Ongoing Fund Withdrawal Complications

As of late January, the situation has deteriorated for affected users. Despite the initial timeline provided by the team, depositors continue to face lockout from their funds with no resolution in sight. The inability to access or withdraw assets has now persisted for over two weeks since the incident was first disclosed. Frustrated community members report that their capital remains inaccessible, creating a growing trust deficit within the user base.

Radio Silence from the Development Team

What has further intensified concerns is the complete absence of follow-up communication from Polycule’s developers. Since their initial acknowledgment of the problem, the team has offered no substantive updates regarding the status of affected funds, timeline for restoration, or concrete remediation steps. This communication void has fueled speculation that the rug pull may have been intentional rather than the consequence of a legitimate security breach. The lack of transparency stands in stark contrast to how professional teams typically handle security incidents.

This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.