[Block Rhythm] has recently encountered a serious security issue that requires everyone's vigilance. Someone has hidden malicious code in the Polymarket copy trading Bots program released on GitHub—what appears to be a normal project is actually secretly reading users' .env configuration files. As you know, this file typically contains the wallet Private Key, and once read, it means that funds are directly being moved by someone.
What’s even worse is that this developer repeatedly modified the code and submitted it to GitHub multiple times, deliberately hiding this malicious package. The security team has issued a warning, advising all users to check the trading Bots they have used, especially automated programs for copy trading. Before launching any third-party scripts, be sure to review the source code first, and don’t be tempted by convenience.
View Original
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.
11 Likes
Reward
11
6
Repost
Share
Comment
0/400
FloorSweeper
· 11h ago
lol watched three people lose their entire stacks to this already... paper hands panic selling rn but the real alpha was never trusting github randos in the first place ngl
Reply0
ContractTester
· 11h ago
Damn, is this trap coming again? Bots on GitHub can't be trusted at all.
View OriginalReply0
CryingOldWallet
· 11h ago
Oh my god, it's this trap again, the Bots on GitHub are becoming increasingly untrustworthy...
Damn, the Private Key in the .env is gone? How careless do you have to be...
Developers repeatedly submit hidden malicious code, this is clearly premeditated...
Brothers who have used copy trading Bots should check quickly, don't wait until the Wallet is emptied to regret.
View OriginalReply0
FadCatcher
· 12h ago
This is that broken place called GitHub again, really have to be careful, you can't slack off when it comes to reading code.
View OriginalReply0
GateUser-ccc36bc5
· 12h ago
Here it comes again, these open source projects on GitHub really can't be trusted blindly. Moving warning, be sure to protect your Private Key.
Daring to move the private key, this developer is really bold.
How can there still be people using unaudited Bots? If you rush, you'll end up losing money.
The .env file configuration must be strictly protected, don’t foolishly run someone else’s code directly.
Planning to hide malicious code, this is no longer a bug, it’s outright Be Played for Suckers.
Now anything can be listed on GitHub, you have to keep your eyes open.
View OriginalReply0
RooftopVIP
· 12h ago
Wow, this method is too damaging. It maliciously submits hidden code repeatedly with premeditation, making it almost impossible to defend against.
---
No wonder my previous copy trading Bots ran out of money after a while; it turns out there are really such unscrupulous developers.
---
Now even GitHub has to be cautious. I have to review the Source Code myself before I dare to use it... web3 really can't tolerate any carelessness.
---
Reading the Private Key directly from the .env file is insane; who would have thought? It's so malicious.
---
Again it's the crypto world, again it's GitHub, and again the Private Key is stolen... when will this life ever be peaceful?
---
Damn, I'm glad I've never used copy trading Bots; it seems I need to be more vigilant.
---
This kind of premeditated attack is scarier than random vulnerabilities; there's simply no way to prevent it.
Beware of Polymarket copy trading Bots hiding malicious code, hackers steal Private Key through .env file.
[Block Rhythm] has recently encountered a serious security issue that requires everyone's vigilance. Someone has hidden malicious code in the Polymarket copy trading Bots program released on GitHub—what appears to be a normal project is actually secretly reading users' .env configuration files. As you know, this file typically contains the wallet Private Key, and once read, it means that funds are directly being moved by someone.
What’s even worse is that this developer repeatedly modified the code and submitted it to GitHub multiple times, deliberately hiding this malicious package. The security team has issued a warning, advising all users to check the trading Bots they have used, especially automated programs for copy trading. Before launching any third-party scripts, be sure to review the source code first, and don’t be tempted by convenience.