Spider Client Mod Menu for Gorilla Tag – What's Known & Ban Risk

You’ll mostly see Spider Client Mod Menu in YouTube thumbnails and Discord download channels. There’s no public repository, store listing or official changelog we could verify, so we’ve left version numbers and feature lists off. What follows is the stuff that applies to it either way: how it loads, where it works, and how people get banned using menus like this.

One public trace exists: a GitHub repository, VisionMakesMods/SpiderClientGT, created in April 2026 and described by its author (“visionnn”) as “a gtag mod menu with alot of cool mods”. It has no README, releases or changelog, so there is nothing more to verify.

Installing a PC plugin like this

Setup is the standard PC routine. Install BepInEx 5.4.23.x (x64) and launch once, add Utilla if the mod needs it, then place the DLL in the plugins folder. Monke Mod Manager can install BepInEx and Utilla for you, but it won’t list most unofficial mods.

Does it work on Quest?

Short answer: only through a PC. The game has to be running on Steam with BepInEx; a Quest connected by Link or Virtual Desktop counts, a Quest on its own doesn’t.

Malware warning

Be careful where the file comes from. The community wiki warns that some menus passed around as free downloads have been RATs (remote-access trojans). A real menu is a single DLL; an installer .exe or a “key system” is a red flag.

Public lobbies: don’t

Yes, it can. Another Axiom’s terms prohibit cheating, and features that affect other players are exactly what reports and the anti-cheat flag. Steam forum threads are full of people banned while running an “anti-report” option. Joining a Modded gamemode separates you from regular players, but the wiki notes reporting and anti-cheat work the same there.

If you try it at all, do it on a spare account, in a private room code, with nobody else in it.

Common problems

• Defender removed something: BepInEx’s winhttp.dll proxy gets quarantined fairly often. Restoring it is fine if BepInEx came from its GitHub releases. A flagged menu DLL deserves more suspicion, not less.
• Crash at startup: Take Spider Client Mod Menu out of plugins first. If the game starts, the mod is the problem. If it still crashes, update BepInEx: 5.4.22 and older crash on current builds.
• Broke after an update: Game patches change the code mods hook into. If nobody maintains Spider Client Mod Menu, it stays broken. There’s no setting to fix that.
• Nothing happens in-game: Open BepInEx/LogOutput.log and search for Spider Client Mod Menu. No mention means BepInEx never loaded it. Usually that’s the wrong folder, a missing dependency, or a build compiled against an older game.

Questions people ask