A Fortnite hacker was hilariously banned mid-game after being reported and caught live on another player’s stream.

As Fortnite continues to be one of, if not the, most popular games around, players keep finding ways to get around the rules and use some nefarious tactics to get a leg up. 

While some players keep on the lighter side of things in exploiting bugs like the BRUTE invincibility issue or the unlimited shield, some take it that extremes step up and go all out on the hacks. We’ve already streamers like Tyler ‘Ninja’ Blevins and Turner ‘Tfue’ Tenney succumb to their powers, but what about smaller streamers – the likes of who get significantly fewer viewers than the top dogs.

Well, they can have their say too – as Mixer streamer , SlackAttackk_, showcased. 

Tfue Fortnite Hacker
Tfue has suffered death to hackers in the past. Image via Tfue

In a post to the FortniteBR subreddit, SlackAttackk dropped a highlight video from their recent broadcast, showing them falling to the might of the apparent hacker’s powers.

As he suspected something was up, the streamer stuck around and watched the suspected cheater, before dropping a report on them. 

Things became clear that they were using an aimbot as the player made light work of another enemy – racking up perfect headshots, leaving the streamer blown away by what he saw. 

When the ban hammer gets sent in mid game… from r/FortNiteBR

Yet, things weren’t finished there. The hacker then moved on to Fatal Fields – where they were able to replicate that perfect precision while sat in the farm’s cornfields. 

However, karma bit them with some perfect timing as a few moments later, the streamer’s earlier report came full circle, with the player being kicked from the game – prompting celebrations from SlackAttackk.

The hilarious conclusion should probably serve as a warning to anyone who thinks they can get away with hacking – especially as someone is usually streaming.

Even if they aren’t broadcasting to hundreds of thousands of fans, there’s always someone watching, just waiting to hit that report button.