Choosing a cheat provider: eleven red flags, and the questions worth asking first

The cheat market has a structural problem: the people best placed to judge quality are the ones who have already been burned. Everyone else is buying on marketing copy.

This is a checklist. It applies to us as much as anyone — every point below is something you should verify about splatvik too, not take on faith.

Red flag 1: "Undetectable"

The correct word is undetected, and it describes the present, not the future.

A provider using "undetectable" is either claiming they have defeated statistical behavioural analysis — which is not a solvable problem in software — or they have not thought about it. Neither is reassuring.

Red flag 2: No visible status page

If you cannot see, before paying, whether the build is currently safe, the provider is asking you to trust that they will tell you when it is not.

A real status page has: per-product state, a timestamp for the last change, and a visible history. If the page only ever says "Undetected" for everything and the timestamp is three months old, it is a static image.

Ours is at /status and is written directly from our development channel, so there is no editorial step between what we know and what you see.

Red flag 3: Sales stay open during an update

This is the clearest signal there is.

When a game patches, a responsible provider pauses sales and blocks injection, because selling a subscription that cannot be used — or worse, can be used dangerously — is indefensible. A provider who keeps taking money during a downtime window has told you exactly what they prioritise.

Red flag 4: No changelog, or a changelog that stops

A changelog is a public record of work. A provider with a real development team ships regularly and the changelog shows it. A provider reselling someone else's build has nothing to write, so the changelog is either absent or was last updated in March.

Check the dates before you check the contents.

Red flag 5: Lifetime subscriptions

Cheat development is ongoing work — every patch requires new offsets, re-verified tables and re-testing. A lifetime licence prices that at zero, which means either the provider expects to shut down before the maths catches up, or they expect the product to stop being updated.

Both are common. Neither is what you want.

Red flag 6: Nobody will tell you what it does technically

Ask how the ESP is drawn. Ask whether there is a visibility check. Ask whether the aimbot writes to memory or applies at input level.

A development team can answer these in a sentence each. A reseller cannot answer them at all, because they do not know — they have API access to someone else's product and a Discord server.

Red flag 7: Support is one person in a DM

Real support has a ticket system with a record. DM-only support means no accountability, no history, and no help when that person is asleep.

Check whether they publish a median response time. Then check the reviews to see if it is true.

Red flag 8: Reviews are all five stars

A product with 400 reviews and no four-star entries is a product with curated reviews.

Look for the negatives. What are the complaints actually about? "Setup was fiddly with Secure Boot" is a real customer. "Best cheat ever 10/10 fast delivery" fifty times over is not.

Red flag 9: The refund policy is one line

"No refunds" is at least honest. A policy that does not say what happens if the build is detected is telling you they intend to decide case by case, in their favour.

What you want to see specified: what happens on detection, what happens during extended downtime, and what happens if the product never worked for you at all. Ours is on the refund page and includes automatic credit for downtime, which we apply without you asking.

Red flag 10: Crypto only, no invoice, no company

Crypto-only is not automatically a red flag — plenty of legitimate providers accept it because card processors are hostile to the category. But crypto only, with no alternative and no record of the transaction, means you have no recourse whatsoever.

A provider offering card payment through a real processor has passed at least one layer of external scrutiny.

Red flag 11: Pressure

Countdown timers, "3 slots left", "price goes up tomorrow". A product with genuine demand does not need to manufacture urgency, and a provider confident in their build does not need you to buy before you have researched.

The questions worth asking before you pay

Take these to any provider's Discord, including ours:

1. What is the current status of this build, and when did it last change?
2. What happens to my subscription if the build goes down for a week?
3. Is the aimbot applied at input level or by writing to game memory?
4. Is there a visibility check, and is it on by default?
5. How many HWID resets do I get, and do I need a ticket for one?
6. What is your median first-response time on tickets?
7. Can I see the changelog for the last three months?

The answers matter less than whether they can answer at all. A development team responds in specifics. Everyone else responds with adjectives.

What we would want you to check about us

In the interest of not being hypocritical:

• Status page: /status — live, per product, with history.
• Changelog: /changelog — every build, dated, written from our dev channel.
• Refund policy: /refund — specific about detection and downtime.
• Reviews: /reviews — including the four-star ones.
• Technical detail: the ESP breakdown and anti-cheat explainer exist precisely so you can judge whether we know what we are doing.

If any of those do not hold up, do not buy from us either.

Still deciding? Join the Discord and ask the questions above before you spend anything.