hack.sale
RU EN

What we don't sell, and why

A shop's refusals say more than its shelves. Four kinds of offers we turn down, and what is wrong with each of them.

A storefront shows what a shop can do. Its refusals show what it refuses to get dragged into. For a buyer, the second list is the more useful one.

Free builds

We get asked regularly why nothing in the catalog costs zero. The short answer: a free cheat does not add up financially.

Staying ahead of detection is not a one-off job. The game ships an update, the anti-cheat ships an update, signatures shift. Somebody has to rework the build every week. If the user is not paying for that, the money comes from somewhere else — a miner bundled in, a stealer that walks off with your Steam and Discord sessions, or a deliberately crippled free tier that exists to sell the paid one.

That does not make every free tool malicious. It means you have no way to tell which one you are holding, and the downside is an account with your whole library attached.

“Ban-proof”

That phrase appears on none of our pages, and that is deliberate.

An anti-cheat is under no obligation to catch you today. It can quietly collect telemetry for a month and issue bans in a single wave — every major system works this way. A seller promising a guarantee today has simply not reached the wave yet, or is counting on you not connecting the two events.

Here is what can be said honestly: a given build on a given game has an observable track record — how long it holds, how quickly the developer ships a fix after a patch, whether there were mass incidents. Those are facts and they are worth knowing. “You won’t get banned” is not a fact. There is more on this in our breakdown of why builds get detected.

Lifetime keys

People occasionally ask to buy something outright. We do not sell that, even where a developer formally offers it.

The reason is the horizon of responsibility. A developer can answer for a build over a stretch they can actually see: the current game version, the current anti-cheat version. What happens a year and two engine updates later is genuinely unknown. Selling “lifetime access” moves that risk onto the buyer and charges them up front for the privilege.

Short terms look worse on the price tag. They also mean you are paying for something that works right now.

Anything we cannot verify

The catalog contains no items whose origin we cannot confirm. It is a dull constraint that keeps the catalog smaller than it could be, and it stays.

What follows from this

If you are comparing us against somewhere cheaper that promises more, compare more than the price. Ask what happens after a detection wave, who ships the fix and how fast, and what you will be told if the build dies a week after purchase.

Our answer: the risk is always there, the short terms exist precisely because of it, and it is worth reading the safe launch checklist first — half of all problems start not with the build but with how it was launched.

FAQ

Why not just download a free cheat?
You can, but the economics do not add up. Staying ahead of detection is continuous work, and someone has to fund it. When the user does not, the money usually arrives through whatever else ships alongside the build.
Are there builds that never get detected?
No. There are builds that stay undetected for a long time. That distinction matters: one is a promise, the other is an observation that can change with any patch.
Why are the terms so short — a day, a week, a month?
An honest term matches the horizon the developer can actually stand behind. A yearly key for software that lives patch to patch is a way of selling the risk to you.