WardenGG - Price, Setup & History

A Retail Lua unlocker available by application, with support for the separately subscribed Murloc, Phoenix, EpicSyncPro and LootRoute products.

WindowsRetailTPM 2.0Application required

Listed price

EUR 39.99/month; CN EUR 20/month

This buys the framework; third-party scripts cost extra.

Visit provider website

Provider informationWhat the check mark meansEdited by M1Sources checked 12 September 2026Why this rank

Overview

WardenGG is a Windows framework for WoW Retail that gives compatible rotations and gathering products access to protected Lua functions. Admission requires an approved application, and the framework subscription does not include those products, so the advertised WGG price is only part of the cost. [1]

More about this product

The listed integrations are Murloc, Phoenix, EpicSyncPro and LootRoute, alongside WGG's own plugin library, Warden Insight spell-decision view and developer inspection tools. Each script and region still needs a compatibility check; an integration listing is not evidence that every combination has been tested. [1]

Before you buy

Windows and TPM requirements exclude some computers.
Support is limited to Retail, and each third-party provider determines which scripts and regions it covers.
WoW and Windows updates can change compatibility, so the current provider notices matter more than an older working setup.
Admission requires an approved application, and the total bill also includes any paid third-party software you choose.

Pricing and access

WGG EU/US framework

EUR 39.99Month

Framework only

Required: Accepted application and compatible Retail/Windows setup

Paid time starts when you redeem the key, and third-party scripts cost extra. [1][2]

WGG CN framework

EUR 20Month

CN framework access

Required: Accepted application and supported CN setup

Third-party scripts and regional support are handled separately. [1]

Historical pricing

Not reliably establishedEarlier releases

Pre-current offer

Required: Not applicable

Requirements

Scroll sideways to see all columns.

Game branch	System / region	Coverage and limits
WoW RetailCurrently provider documented	Windows 10 22H2; Windows 11 22H2,23H2,24H2,25H2EU,US,CN	TPM2.0 must be enabled, and compatibility should be checked against the provider's latest notices after game or Windows changes. [1][2]
WoW ClassicCurrently unsupported	AnyAll	An older forum analysis identified Classic-related code in the binary, but code left in a build does not establish current Classic support. [1][10]
macOSUnsupported	macOSAll	The current product offer does not include a Mac version. [1]

Community and support

The official Discord handles applications, with community and subscription access following approval. WGG describes places as limited without publishing a current member count or capacity.

Official websiteWebsite / Public.Application DiscordDiscord / The invite is public, while member access depends on application approval.Access, billing and compatibility policySupport documentation / Public.Launcher data policyData disclosure / Public.Security statement and source reviewIncident disclosure / Public.

Support details

WGG manually reviews applications submitted through the official Discord. Approval opens the main community and subscription options, although the claim of limited access comes without a published member count or capacity.

WGG reviews refund requests after troubleshooting, and its published policy is narrow: it covers confirmed WGG-side faults that make the service completely unusable. Setup errors, incompatible environments and changes of mind fall outside it. [2]

WGG's published downtime policy awards seven subscription days for each full unavailable day beyond three. Four full days offline would therefore earn seven added WGG days; the credit does not extend your WoW subscription. [2]

The launcher-data page says license, IP and hardware identifiers verify sessions, while diagnostic logs remain on your computer unless you send them to support. Those logs can include computer, driver, process and crash details. The statement covers the launcher, leaving Discord, payment and website data outside its scope. [3]

Features and plugins (10)

Protected Lua access for compatible scripts [source]
Murloc, Phoenix and EpicSyncPro integrations [source]
LootRoute gathering and fishing support; formerly Trinket [source]
Warden Insight displays rotation spell decisions [source]
Dashboard plugin library controls [source]
In-game Object Manager, cast history, combat log and Lua console [source]
Custom plugin framework and private developer documentation [source]
Training-dummy support and status-frame customization [source]
Loader designed to reject unsupported game builds [source]
Published subscription credit policy for extended downtime [source]

These details come from the linked published sources; we have not tested the software ourselves.

Privacy and security

WGG acknowledges historical Discord-token collection and says it removed the feature, while denying the separate theft allegations. The public evidence we reviewed does not establish the wider claims of financial, browser-credential or account compromise. The history above sets out the disclosure, the responses and the limits of each technical report.

Data collection and privacy

According to the provider, license, IP and HWID details are stored to verify sessions. Diagnostic logs can contain process, driver and hardware details, but stay on your computer unless you send them to support.

Accusations need evidence

A forum post becomes useful when it includes the original evidence, the software version and a clear link to the alleged harm. Repeated accusations do not fill in those gaps, whether they concern WGG, another provider or a competing seller.

WGG's acknowledgment supports the historical token-collection finding, but leaves wider accusations and the contents of later builds as separate questions. Accusing rivals of fabricating or coordinating the allegations requires evidence too, which we have not established here.

Read the dated reports and responses

Read the provider's full security statement

Update record

In five selected EU/US examples, the gap from a WoW build notice to WGG's compatibility announcement ranges from 24 minutes to 10 hours 38 minutes. These are announcement intervals, so they cannot tell us total downtime or promise the next turnaround, and the original Discord timestamps are not public.

Update log and evidence (10)

WGG publishes dated product changes and five selected EU/US examples pairing a WoW build notice with a compatibility announcement. They give a useful but limited view of announcement timing because the original Discord messages are not public.

The published BlizzTrack-to-WGG announcement sample runs from 24 minutes to 10 hours 38 minutes. It cannot establish complete downtime, an uptime percentage or CN response time, and it gives no promise about future turnaround.

2026-08-1312.1.0.69283
Build notice 01:33 UTC; WGG notice 09:49 UTC
EU/US compatibility-announcement sample
Timing: 8h16m
[2]
2026-08-1312.1.0.69299
Build notice 18:59 UTC; WGG notice 20:07 UTC
EU/US compatibility-announcement sample
Timing: 1h08m
[2]
2026-08-1712.1.0.69323
Build notice 20:19 UTC; WGG notice 20:43 UTC
EU/US compatibility-announcement sample
Timing: 24m
[2]
2026-08-1812.1.0.69382
Build notice 00:59 UTC; WGG notice 11:37 UTC
EU/US compatibility-announcement sample
Timing: 10h38m
[2]
2026-08-2012.1.0.69404
Build notice 19:19 UTC; WGG notice 22:20 UTC
EU/US compatibility-announcement sample
Timing: 3h01m
[2]
2026-08-26
WGG added dashboard controls for managing the plugin library.
Product feature
[2]
2026-08-28V2
WGG's security statement dates the V2 release to this day.
Release boundary; no measured downtime
[4]
2026-08-312.1
The update addressed spell replacements, interrupts and training dummies, and added status-frame customization.
Framework change
[2]
2026-09-08
WGG's security statement dates the core rebuild to this day.
Release boundary; no incident-clearance proof
[4]
2026-09-09
WGG fixed launcher errors and server-plugin loading; the plugin fix did not require a new download.
Product fixes
[2]

The timestamp pairs were reproduced by the provider, which says it reviewed them on September 11; we did not observe the original messages independently.
The public material does not supply a complete outage history or release list, a CN timing sample or independent uptime monitoring.
A quick compatibility update says nothing about earlier account flags, which may still result in delayed enforcement.

Ban reports and history

The CN and EU ban reports remain unverified, including the submitted one-sixth estimates and claims that leaks caused them. WGG's privacy dispute needs to be assessed separately through its disclosures and responses.

About these reports

The privacy dispute and game-ban reports concern different questions. The public CN allegation has no verified affected-user count or established cause, while the newer CN and EU submission below still lacks the original announcements needed to verify its figures and leak explanations. The dated history sets out WGG's disclosures and responses alongside what the technical reports can actually establish.

This review covers the public website, current disclosures, original beta and leaked-files discussions, August-September security threads and review-list posts through September 12 2026. We obtained no executable, leaked archive, private Discord material, credentials or account telemetry, so the technical reports establish what their authors reported rather than findings we reproduced.

What do the cause labels mean?

Recent community reports

These reports were sent to us, but we have not yet verified the original evidence behind them.

Received 2026-09-12 / Unverified submission

CN report: around one-sixth of users reportedly affected

A submission to this directory says WGG developers acknowledged bans affecting around one-sixth of the CN userbase and blamed a leaked build, distinguishing that explanation from detection of the underlying technology.

What needs checking

The original developer announcement, incident date and user counts have neither been supplied nor found publicly, so this remains a submitted account of the developers' explanation. It verifies neither the proportion nor the cause, and a build leak does not rule out detection of the leaked software.

Received 2026-09-12 / Unverified submission

EU report: similar estimate, with PSP overlap and an alleged leak

The same submission puts a recent EU incident at around one-sixth of that userbase. It says many affected users also used PSP and describes a build leak around the time a developer left.

What needs checking

The incident date, affected-user counts, product-use records and original leak announcement remain unverified, as do the alleged leak and developer departure. Use of both products complicates attribution without establishing which product, if either, caused a ban.

2025-10-30Forum moderation

Initial beta thread closed for sales-category rules

Original moderator action

A moderator closed the first beta thread because the paid offer belonged in the trading section, and directed the seller there. [6][7]

Full report, cause and response

Affected scope: WoW Bots beta announcement

Although the quoted general rules prohibit malware, the moderator's instruction concerned where a paid offer belonged; it was not a malware finding.

Cause: UnknownExplain the labels

The moderator addressed the placement of a sales post without making a detection or technical security finding.

Unknown [6][7]

Provider response: The provider opened a beta thread in the trading section that same day.
What happened next: The offer moved to the trading section, where the discussion later opened applications on November 9.
Attribution: The record consists of the original moderator message and the provider's follow-up.
Date precision: day

Sources [6][7]

2025-11Service history record

Beta access complaints; listing later revised

Dated community replies and mutable provider listing

Replies on November 18 and 23 describe losing beta or server access, while the sales thread's edited first post now says WardenGG is still running as of 2026. [7]

Full report, cause and response

Affected scope: 2025 beta offer

Because the first post has changed, its current wording cannot explain what happened to each earlier beta account or date the access changes.

Cause: UnknownExplain the labels

The surviving discussion does not establish a technical or commercial reason for the access problems.

Unknown [7]

Provider response: The provider's edited first post says the service is still running as of 2026.
What happened next: The earlier access complaints remain part of the record, but do not establish that the current service closed.
Attribution: This combines a provider listing that can be edited with community replies posted at the time.
Date precision: month of dated replies; first-post edit date unknown

Sources [7]

2026-01-26Build exposure claim

Public claim of WGG file redistribution

Original post partially removed; exposure details unverified

A public thread titled WardenGG leaked files appeared on January 26. Although its main post is gone, replies preserve a quoted promise to redistribute product files. [8]

The evidence does not establish a link to game enforcement. [8]

Full report, cause and response

Affected scope: Unidentified WGG files

No archives were downloaded for this review, leaving the alleged files' authenticity, version and scope unestablished.
Replies describing the poster as banned appear to concern platform access and therefore do not establish a Blizzard banwave.

Cause: Build exposure/leakExplain the labels

The thread establishes that redistribution was claimed, while leaving it unknown whether Blizzard obtained a build, derived a signature or used it to issue bans.

Attributed to cited source [8]

Provider response: We found no provider response to this incident that we could authenticate.
What happened next: The available evidence does not connect the alleged redistribution to later game enforcement.
Attribution: The original forum discussion was available, but its underlying files were outside this audit.
Date precision: day of forum post

Sources [8]

2026-08-20Community ban report

CN ban allegation

Single author's allegation; not independently corroborated

When removing WGG from a community list, tamedbeast alleged that bans had affected much of its CN userbase. [11][12][1]

Neither the reported wave nor its cause has been confirmed. [11][12][1]

Full report, cause and response

Affected scope: WGG CN users; edition/build unspecified

The author repeated the claim in another thread, which remains a second telling rather than independent confirmation.
Without an affected-account list, exact incident date, build, total user count, provider notice or detection method, the post's claimed proportion remains unverified.
A newer submission gives a one-sixth estimate, but no original developer notice or incident date ties it to this allegation.

Cause: UnknownExplain the labels

There is too little evidence to establish a detection method, the time accounts were flagged or the reason for enforcement.

Unknown [11][12][1]

Provider response: The reviewed sources contain no public developer announcement resolving the allegation. A newer submission instead gives a different estimate and blames a leak, as described in the recent community reports above.
What happened next: The allegation remains unresolved: this material establishes neither a banwave nor zero detections.
Attribution: This records an original dated community allegation alongside the provider's separate position.
Date precision: report date; underlying bans undated

Sources [11][12][1]

2026-08-20Security/privacy disclosure

Historical Discord-token collection becomes a public issue

Historical functionality later acknowledged by provider

twasfer warned that WGG collected Discord tokens, and WGG later acknowledged that an earlier build had collected and transmitted session tokens. [9][4]

Full report, cause and response

Affected scope: Older WGG build(s), not an identified complete release range

A Discord session token authenticates an account, which makes it an account secret rather than ordinary diagnostic data.
Forum users put the collection period at approximately six months, but no verified exposure timeline supports that estimate.

Cause: Security/privacy disclosureExplain the labels

WGG says the acknowledged collection and transmission of tokens served an internal leak investigation. That explains its stated motive without independently establishing a need to collect them, and no causal link to game banwaves has been shown.

Attributed to cited source [9][4]

Provider response: WGG's September 1 correction said the feature had been removed.
What happened next: Historical collection is acknowledged, but the public record still leaves the affected users and releases, retention period, access to the data and verification of deletion unresolved.
Attribution: The original warning is supported in part by the provider's admission.
Date precision: first public warning date; collection start/end unknown

Sources [9][4]

2026-08-21Security review

Launcher source review reports no theft or remote-control functionality

Review's stated findings; author/revision unidentified

WGG published a static review of launcher source code that reported no RAT, Discord-token collector or browser-credential theft in the source examined. [5][4]

The review covered the source shown, without matching it to the distributed binary or certifying later builds. [5][4]

Full report, cause and response

Affected scope: First-party launcher source supplied for review

The report omits its author and exact source revision, establishes no match to a shipped executable and documents no runtime tests, with kernel internals largely excluded.
Its observations include optional local storage of WGG login credentials, HWID/IP handling and local anti-analysis checks, but do not cover every product component.

Cause: Security/privacy disclosureExplain the labels

Without a source-to-binary match and release timeline, a review of this source cannot refute a finding about a different historical executable.

Attributed to cited source [5][4]

Provider response: WGG publishes the full report and now sets out its limitations.
What happened next: The finding applies to the source reviewed before the August 28 V2 release and September 8 rebuild. It cannot undo earlier collection or certify the releases that followed.
Attribution: The review is hosted by the provider and has not been independently reproduced.
Date precision: report's stated date

Sources [5][4]

2026-08-25Security allegations

Separate account and financial-compromise allegations

User reports; attribution to WGG unproven

Public posters described compromised accounts, and one August 25 commenter also reported financial and router problems while explicitly allowing that they could be a coincidence. [9][10][4]

Full report, cause and response

Affected scope: Discord/email accounts and separately alleged financial/router incidents

The posts supply no forensic evidence connecting these separate events to WGG.
The acknowledged token collection does not establish these broader allegations, which require evidence of their own.

Cause: UnknownExplain the labels

WGG's admission of historical token collection does not, on its own, establish each alleged email, financial or network compromise.

Unknown [9][10][4]

Provider response: In its August 25 statement, WGG denied financial, browser-credential and account theft.
What happened next: No independent finding or adjudication establishing the broader allegations was found in this review.
Attribution: The record here consists of the original community reports and WGG's denial.
Date precision: provider statement date; complaint dates August 25-September 7

Sources [9][10][4]

2026-08-26Security analysis

Forum static binary analysis identifies a Discord-token collector

Detailed public report, not reproduced independently

efinity examined a named, hashed unpacked executable and reported that it collected Discord tokens from Discord and browser session storage before sending them to a separate information endpoint. [10][4]

The analysis concerns a historical artifact and does not establish what later builds contain. [10][4]

Full report, cause and response

Affected scope: Named historical unpacked Windows executable

The author says the sample was neither run nor network-tested, and protected code leaves some implementation details unresolved.
The report distinguishes Discord web-session tokens from general browser-password or cookie theft, and establishes neither ransomware nor network spread.
The report did not identify the current shipping loader or establish whether it matched the sample.

Cause: Security/privacy disclosureExplain the labels

The analyst attributes collection to a dedicated authentication-token feature, a finding about personal-data security that does not explain how WoW detected software.

Attributed to cited source [10][4]

Provider response: WGG later acknowledged historical token collection in its correction and said the feature had been removed.
What happened next: The report supports scrutiny of that historical executable without establishing that every later WGG release retains the same behavior.
Attribution: This is a forum author's technical report, with neither accredited certification nor independent replication.
Date precision: forum post date; sample build/release date not established

Sources [10][4]

2026-09-01Provider correction

Correction acknowledges collection and narrows reinstatement claim

Official current retrospective disclosure

According to WGG, its September 1 correction acknowledged the token feature, said it had been removed and clarified what forum seller verification means. [4]

Full report, cause and response

Affected scope: Historical feature and sales-thread identity verification

Seller verification establishes identity; it cannot certify software safety, resolve every allegation or guarantee future conduct.

Cause: Security/privacy disclosureExplain the labels

The correction concerns disclosure and trust, while forum reinstatement establishes no technical fix, clean executable or immunity from game bans.

Attributed to cited source [4]

Provider response: WGG describes the issue as serious and acknowledges the damage to trust.
What happened next: The claimed removal has not been independently verified across all released components.
Attribution: This relies on the provider's September 12 public account of its earlier correction; the original Discord notice was not publicly accessed.
Date precision: correction date as reproduced by provider

Sources [4]

2026-09-04Forum status allegation

Claim of renewed forum ban after reinstatement

Community statement; official moderator reason not verified

tamedbeast alleged that the WGG sellers had again been permanently banned. [9]

Full report, cause and response

Affected scope: Provider's forum presence

Without an original moderator decision or independently verified current account status, the renewed ban remains an allegation.

Cause: UnknownExplain the labels

Even a confirmed forum ban would not establish software detection or a criminal finding, or explain a game-account ban.

Unknown [9]

Provider response: The reviewed public sources contain no later provider response.
What happened next: Both the forum status and the exact reasons for any enforcement remain unresolved.
Attribution: This comes from a dated community reply rather than a moderator finding.
Date precision: community report date

Sources [9]

Comments and ratings

If you have used WardenGG, this is the place to share how it went. The ratings here come from readers and are separate from the editorial ranking.

Loading ratings...

Latest comments

References

[1] WardenGG live product, pricing and requirementsWardenGG / Provider website / Checked: 2026-09-12
Source notes: WardenGG live product, pricing and requirements
Search extracts were stale, so we fetched the page directly; its provider claims still require independent verification.
[2] Access, refunds, downtime and update sampleWardenGG / Provider support and changelog summary / Published: 2026-09-12 / Checked: 2026-09-12
Source notes: Access, refunds, downtime and update sample
The provider says it checked five pairs of Discord timestamps on September 11, but the original member messages are not public.
[3] Launcher data and diagnosticsWardenGG / Provider data disclosure / Checked: 2026-09-12
Source notes: Launcher data and diagnostics
This public page was reviewed without logging in.
[4] Security statement: historical collection and review scopeWardenGG / Provider retrospective statement / Published: 2026-09-12 / Checked: 2026-09-12
Source notes: Security statement: historical collection and review scope
Retrieved directly by HTTP, this page summarizes the August 25 and September 1 provider announcements without linking to their originals publicly.
[5] WGG Launcher Analysis, complete source-review reportUnidentified reviewer; hosted by WardenGG / Static source review / Published: 2026-08-21 / Checked: 2026-09-12
Source notes: WGG Launcher Analysis, complete source-review report
The report documents no author, exact revision, released-binary match or runtime test, and largely excludes kernel analysis.
[6] Original WGG beta thread and moderator closureRuno01 / Natsu Dragneel / elitepvpers / Original provider and moderator posts / Published: 2025-10-29/2025-10-30 / Checked: 2026-09-12
Source notes: Original WGG beta thread and moderator closure
This public page was reviewed without logging in.
[7] WGG beta sales threadRuno01 and users / elitepvpers / Historical provider sales thread / Published: 2025-10-30/2025-11-23 / Checked: 2026-09-12
Source notes: WGG beta sales thread
Rechecked September 12, the edited first post says WardenGG is still running as of 2026. The edit date is unknown, while earlier replies preserve the beta-access complaints.
[8] WardenGG leaked files discussiontwasfer and others / elitepvpers / Original dated community discussion / Published: 2026-01-26/2026-02-01 / Checked: 2026-09-12
Source notes: WardenGG leaked files discussion
The main post has been removed, and no leaked files were accessed or downloaded.
[9] Account-security warning and follow-up reportstwasfer, tamedbeast, DMA.Union and others / elitepvpers / Original dated allegations and discussion / Published: 2026-08-20/2026-09-07 / Checked: 2026-09-12
Source notes: Account-security warning and follow-up reports
These user allegations do not independently establish every claimed compromise or a legal finding.
[10] WGG compromise allegation and static binary reportfuturethinkers999 and efinity / elitepvpers / Original allegation and forum-posted static analysis / Published: 2026-08-26 / Checked: 2026-09-12
Source notes: WGG compromise allegation and static binary report
The report identifies UNLKR_STABLE_WEST_unpacked.exe and its hash, but we did not reproduce its findings and no match to the current release was established.
[11] Original list-removal post alleging CN banstamedbeast / elitepvpers / Original dated community allegation / Published: 2026-08-20 / Checked: 2026-09-12
Source notes: Original list-removal post alleging CN bans
The author repeats the claim elsewhere without supplying raw ban evidence, a build, an exact event date or a total user count.
[12] Repeated WGG CN-ban allegationtamedbeast / elitepvpers / Repeated community allegation / Published: 2026-08-20 / Checked: 2026-09-12
Source notes: Repeated WGG CN-ban allegation
This repeats the same author's claim and adds no independent confirmation.

WardenGGOfficial source verified

Overview

Before you buy

Pricing and access

Requirements

Community and support

Privacy and security

Update record

Ban reports and history

Recent community reports

CN report: around one-sixth of users reportedly affected

EU report: similar estimate, with PSP overlap and an alleged leak

Initial beta thread closed for sales-category rules

Beta access complaints; listing later revised

Public claim of WGG file redistribution

CN ban allegation

Historical Discord-token collection becomes a public issue

Launcher source review reports no theft or remote-control functionality

Separate account and financial-compromise allegations

Forum static binary analysis identifies a Discord-token collector

Correction acknowledges collection and narrows reinstatement claim

Claim of renewed forum ban after reinstatement

Comments and ratings

Latest comments

References