# Exploit found which can lead cheating

**URL:** <https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665>\
**Category:** Racing\
**Created:** [February 23, 2022, 5:59pm UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665 "2022-02-23T17:59:32Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![James\_McLean\_Watt](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/james_mclean_watt/32/532130_2.png) [@James\_McLean\_Watt](https://forums.zwift.com/u/James_McLean_Watt)\
**Post date:** [February 24, 2022, 8:18am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/21 "2022-02-24T08:18:35Z")

</div>

Yep WTRL’s response is trying to assure all past and current events were not victim of this exploit which is utterly false a seasoned cheat will know how much weight they can deduct to keep their HR in the correct zone so not to arouse any suspicion. One of current ZRL teams which was high up on the table got disqualified from this weeks TTT because one rider was 0.1 w/kg over cat limits and it was his 4th race of the season not due to cheating, cruising or sandbagging just a full on maximum effort for his team.

---

<div class="post-metadata">

**Author:** ![Lee\_H](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/lee_h/32/502965_2.png) [@Lee\_H](https://forums.zwift.com/u/Lee_H)\
**Post date:** [February 24, 2022, 8:37am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/22 "2022-02-24T08:37:08Z")

</div>

Another absolute PR Disaster.

How do you spot a company in turmoil - Constantly fire fighting, and doesn’t take responsibility for their own mistakes. Its a fairly cowardly action to ban @Luciano_Pollastri_ZE .

or was this maintenance again @Marc_Cote

---

<div class="post-metadata">

**Author:** ![Steve\_Hammatt](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/steve_hammatt/32/210763_2.png) [@Steve\_Hammatt](https://forums.zwift.com/u/Steve_Hammatt)\
**Post date:** [February 24, 2022, 8:56am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/23 "2022-02-24T08:56:20Z")

</div>

Seems like another victim of “maintenance”.

Very sadly unsurprising that Zwift have known about this exploit for years but done absolutely nothing about it.

---

<div class="post-metadata">

**Author:** ![Jon\_Stevens-Hall](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/jon_stevens-hall/32/36294_2.png) [@Jon\_Stevens-Hall](https://forums.zwift.com/u/Jon_Stevens-Hall)\
**Post date:** [February 24, 2022, 9:26am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/24 "2022-02-24T09:26:44Z")

</div>

This is appalling, toxic behaviour by Zwift.

There is no doubt, reading the blog, that the article was well researched and was made in good, inquisitive faith.

The correct response, Zwift, is to say “thank you”. You’re acting in a toxic and irresponsible way by banning them, and the notion that this should have been disclosed privately is ridiculous given that this is clearly a known bug already.

This is retaliation. No good company should ever retaliate in this way against good-faith disclosure. It enables cheating and even security risks to flourish.

You owe them a climbdown and an apology.

---

<div class="post-metadata">

**Author:** ![Basti\_R2](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/basti_r2/32/542002_2.png) [@Basti\_R2](https://forums.zwift.com/u/Basti_R2)\
**Post date:** [February 24, 2022, 9:36am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/25 "2022-02-24T09:36:52Z")

</div>

also in FB Said: #freeluciano

---

<div class="post-metadata">

**Author:** ![Marco\_Derix](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/marco_derix/32/448216_2.png) [@Marco\_Derix](https://forums.zwift.com/u/Marco_Derix)\
**Post date:** [February 24, 2022, 9:38am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/26 "2022-02-24T09:38:24Z")

</div>

Crazy that @Luciano_Pollastri_ZE is banned over this. Zwift should be all over this, and make an emergency patch so this cannot be exploited anymore. Especially with the upcoming World Championship. They can’t afford there to be ANY discussion on the results of that race.

---

<div class="post-metadata">

**Author:** ![Luciano\_Pollastri\_ZE](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/luciano_pollastri_ze/32/460859_2.png) [@Luciano\_Pollastri\_ZE](https://forums.zwift.com/u/Luciano_Pollastri_ZE)\
**Post date:** [February 24, 2022, 9:43am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/27 "2022-02-24T09:43:16Z")

</div>

Just to give more context and detail, I have received a further email from Zwift Support explaining reasons of the ban. Reproducing the part suggesting I will be still banned as long as the article on wordpress is not removed… "Your ban was both in relation to the performance metrics found by our team, but also the blog post in which you created an extensive guide about how to cheat.

Both of those issues are violations of our Terms of Service (mentioned in the Community Guidelines that were sent to you in the previous message). To be honest, your violations warrant a longer shadowban term than what you had received. As such, your ban will not be reduced or removed before the 30 days are complete.

Further, your wordpress article is still published. So long as it is, your shadowban may be extended."

---

<div class="post-metadata">

**Author:** ![gloscherrybomb](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/gloscherrybomb/32/493046_2.png) [@gloscherrybomb](https://forums.zwift.com/u/gloscherrybomb)\
**Post date:** [February 24, 2022, 9:47am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/28 "2022-02-24T09:47:00Z")

</div>

Just drives this sort of thing underground, Before you know it, there will be sites with much more than just this exploit, which will not be traceable back to a specific user account.

If they fix the exploit, the existence of the wordpress site is irrelevant. Classic case of shooting the messenger rather than having a look at why this hasn’t been resolved in the 2 years they have known about it.

---

<div class="post-metadata">

**Author:** ![Jonas\_H](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/jonas_h/32/511149_2.png) [@Jonas\_H](https://forums.zwift.com/u/Jonas_H)\
**Post date:** [February 24, 2022, 9:48am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/29 "2022-02-24T09:48:42Z")

</div>

Quite simply. Zwift, you’re in the wrong here. Do the right thing.

#FreeLuciano

---

<div class="post-metadata">

**Author:** ![Steve\_Cl](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/steve_cl/32/19534_2.png) [@Steve\_Cl](https://forums.zwift.com/u/Steve_Cl)\
**Post date:** [February 24, 2022, 9:50am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/30 "2022-02-24T09:50:53Z")

</div>

The right thing as in remove the ability to change weight and height on the fly during the current Zwift session in progress. Changes only come into effect after terminating Zwift and restarting the game.

---

<div class="post-metadata">

**Author:** ![Lee\_H](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/lee_h/32/502965_2.png) [@Lee\_H](https://forums.zwift.com/u/Lee_H)\
**Post date:** [February 24, 2022, 9:52am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/31 "2022-02-24T09:52:08Z")

</div>

Just taking a guess… Zwift are currently embarrassed this was released 2 days before the World Championships.

They now have multiple fires to fight and this action is making someone feel good and have some retribution.

Did they ban anyone else who had posted this cheat online over the last 18 months? Answer is no.

---

<div class="post-metadata">

**Author:** ![Dean](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/dean/32/489893_2.png) [@Dean](https://forums.zwift.com/u/Dean)\
**Post date:** [February 24, 2022, 9:53am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/32 "2022-02-24T09:53:57Z")

</div>

Talking about exploits, sticky watts …

---

<div class="post-metadata">

**Author:** ![Luciano\_Pollastri\_ZE](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/luciano_pollastri_ze/32/460859_2.png) [@Luciano\_Pollastri\_ZE](https://forums.zwift.com/u/Luciano_Pollastri_ZE)\
**Post date:** [February 24, 2022, 10:10am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/33 "2022-02-24T10:10:44Z")

</div>

By the way, sticky watts post with clear instructions how the cheat works is all over the place, including in ZI. What is the difference between that post nbeing there for ages and my post?

> **[Sticky Watts: Why They Exist, and How They Affect the Zwift Experience](https://zwiftinsider.com/sticky-watts/)**
>
> Take a trip down the power data rabbit hole!

---

<div class="post-metadata">

**Author:** ![gloscherrybomb](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/gloscherrybomb/32/493046_2.png) [@gloscherrybomb](https://forums.zwift.com/u/gloscherrybomb)\
**Post date:** [February 24, 2022, 10:24am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/34 "2022-02-24T10:24:09Z")

</div>

![image](https://global.discourse-cdn.com/gozwift/original/4X/e/7/4/e74c2a0969f3861fbb16dc07f04b925395456d78.png)

Common sense left ZHQ a long time ago.

---

<div class="post-metadata">

**Author:** ![Marco\_Derix](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/marco_derix/32/448216_2.png) [@Marco\_Derix](https://forums.zwift.com/u/Marco_Derix)\
**Post date:** [February 24, 2022, 10:26am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/35 "2022-02-24T10:26:57Z")

</div>

The way Zwift is handeling this is creating a PR sh\*tshow for themselves. This was exemplary on how NOT to react to such a blogpost. They knew of the problem. Somehow it slipped their minds, got a low priority, or something else why it hasn’t been resolved already.

Why they choose to ban the guy disclosing it is beyond me. They should be thankful.

It’s like a lock producing company suing a locksmith/lockpicker when they show how a lock can be opened easily without a key, instead of recalling the lock and fixing the issue (YT: Lockpickinglawyer very interesting for anyone who has bought a lock).

---

<div class="post-metadata">

**Author:** ![Rich](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/rich/32/431690_2.png) [@Rich](https://forums.zwift.com/u/Rich)\
**Post date:** [February 24, 2022, 10:30am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/36 "2022-02-24T10:30:55Z")

</div>

zwift really aren’t having a good time are they lately with the issues with wtrl banning people and now this

---

<div class="post-metadata">

**Author:** ![Vi\_Dude4005](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/vi_dude4005/32/47767_2.png) [@Vi\_Dude4005](https://forums.zwift.com/u/Vi_Dude4005)\
**Post date:** [February 24, 2022, 10:49am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/37 "2022-02-24T10:49:28Z")

</div>

Totally supporting your action @Luciano_Pollastri_ZE and thanks @gloscherrybomb for giving evidence of this here. I think this whole situation makes clear what we are for ZwiftHQ (paying customers, not allowed to interfere in any way in the business, apart from paying the monthly fee) and what many of us hope to find in Zwift (a civil and very lively community, where fair rules should be respected). The ones to be sanctioned are those breaking the rules, not the ones trying to improve things as you did, Luciano.

---

<div class="post-metadata">

**Author:** ![gloscherrybomb](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/gloscherrybomb/32/493046_2.png) [@gloscherrybomb](https://forums.zwift.com/u/gloscherrybomb)\
**Post date:** [February 24, 2022, 11:01am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/38 "2022-02-24T11:01:53Z")

</div>

The WTRL false accusations have now been deleted.

![image](https://global.discourse-cdn.com/gozwift/original/4X/b/a/4/ba4d72ec2ddb9d35a0bbe963d5cf9d6d793227fe.png)

---

<div class="post-metadata">

**Author:** ![Basti\_R2](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/basti_r2/32/542002_2.png) [@Basti\_R2](https://forums.zwift.com/u/Basti_R2)\
**Post date:** [February 24, 2022, 11:02am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/39 "2022-02-24T11:02:21Z")

</div>

It could have been so easy:

1. contact Luciano and ask him to remove the article
2. say thank you to Luciano for finding out the Problem
3. Write him that the Team at zwift HQ is working on a solution.

No need to ban him.

---

<div class="post-metadata">

**Author:** ![Luciano\_Pollastri\_ZE](https://sea2.discourse-cdn.com/gozwift/user_avatar/forums.zwift.com/luciano_pollastri_ze/32/460859_2.png) [@Luciano\_Pollastri\_ZE](https://forums.zwift.com/u/Luciano_Pollastri_ZE)\
**Post date:** [February 24, 2022, 11:03am UTC](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665/40 "2022-02-24T11:03:25Z")

</div>

Thank you. The situation is total nonsense. I have been a firm supporter of Zwift and quite contributing to the community for two years. Yesterday has been a breach of trust and faith on the platform and on the corporation, but not on the community who has been extremely supportive.

[Previous page](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665.md?page=1)

[Next page](https://forums.zwift.com/t/exploit-found-which-can-lead-cheating/578665.md?page=3)
