[WoW][Warden] Watched Address List - Including Length & Bytes!

[-Ryuk-]

Hello MMOwned,

From now on, I will be posting the all my Warden info on the MMOwned Wiki.

Click here for the info!

Enjoy

[danbirk]

So awesome, wish i knew how to do that.
I mean how you got acces to find such stuff

Good release.

[oldmanofmen]

There's a strong smell of borgulshant in this thread.

[yangken]

great work，thx

[Mc-fly]

very awesome, thank you

[RivaLfr]

Good, +rep

[-Ryuk-]

There's a strong smell of borgulshant in this thread.

Nope, this is all real, Try editing any of these on a trial account, wait a little while and you will get banned.

[reggggg]

Edit: Nevermind, posted before I read properly.

However, if it is possible for you to publish this list (perhaps automatically) on a server somewhere, I am sure many would appreciate such a service - good stuff.

[amadmonk]

I swear that a while back, Apoc threatened to insta-ban anyone who published this information (for a number of reasons including letting Blizzard know what we know, since we know for a fact that they read these forums). But I'm getting old and may have misremembered...

[XTZGZoReX]

I think it's common knowledge by now that people know this.

Just saying.

[Xelper]

I don't see a huge issue with publishing Warden's watched address list. Obviously Blizzard knows we have the tools necessary to check and monitor Warden. It would be foolish to think Blizzard doesn't already know we have this information, and it would be foolish for us to think that Blizzard thinks that the 'state of the art' memory editing is being publicly disclosed and they aren't thinking ahead.

[caytchen]

Not to mention there have not been any major changes to warden whatsoever for quite some time now. I guess people up at Activision/Blizzard don't like employing people to reduce their revenue.

[-Ryuk-]

I swear that a while back, Apoc threatened to insta-ban anyone who published this information (for a number of reasons including letting Blizzard know what we know, since we know for a fact that they read these forums). But I'm getting old and may have misremembered...

If this is the case, then apoc can feel free to remove this thread. However if blizzard dont already know that we do this sort of thing, then they really need to hire a new warden guy!

[oldmanofmen]

If this is the case, then apoc can feel free to remove this thread. However if blizzard dont already know that we do this sort of thing, then they really need to hire a new warden guy!

Or just some guy off the street that can google wow memory editing for them?

[amadmonk]

Again, this is secondhand info from my faulty memory. However, I believe that the motivation wasn't specifically to keep the "Warden guy" from knowing that we RE this sort of stuff; any non-chimpanzee security expert should realize that. It's to keep them from knowing the specific addresses that we know about.

I personally have no investment in the matter, since I don't rely on exploits/hacks and none of my bot code touches any protected execution path, so don't flame the messenger. If the Warden guy gets this and uses it somehow to instigate another ban wave (by, say, dynamically checking some address not on this list with a Warden update packet), it's really no skin off my back. The best way to avoid Warden's memory scans is simply to not modify the PE, or to modify it as little as possible (my bot only modifies 5 bytes of randomly-chosen memory with a non-hashable offset, so unless they start checksumming the entire .text section, I'm unlikely to ever be hit by hash checking), so again -- none of this really matters to me personally.

Besides, at this point, it looks like no ban is forthcoming, so *shrug*. I must have remembered it wrong.