Jump to content

Recommended Posts

Posted

🚀 IronLock Shield - Closed Beta Testing

Hello everyone,

We are currently looking for Lineage II Interlude server owners interested in participating in the closed beta phase of IronLock Shield.

IronLock Shield is a security platform designed specifically for Interlude servers.

Features include:

✓ Secure Launcher Architecture
✓ HWID-Based Licensing
✓ Anti-Debug Protection
✓ DLL Injection Detection
✓ Manual Map Detection
✓ Session Protection
✓ Replay Protection
✓ Runtime Integrity Verification
✓ Secure Update System

Selected servers will receive 1 month of free access in exchange for testing and feedback.

Website:
https://ilshield.com

If you are interested, feel free to send me a private message or contact me through Discord.

Thank you.

Posted

Anything that is not a kernel level anticheat is totally useless on todays market. You cannot properly prevent botting because, without kernel access, you cannot detect injected DLLs or inspect processes at the level required to stop them.

It's good to see people contributing and trying different approaches, but in general, you won't be able to prevent bots from accessing and operating on your server with a usermode anticheat alone.

There is a solution that I have not posted or shared with anyone that can fully prevent Adrenaline/Helper from being used on servers. However, I want to give it more time before discussing it publicly so I can see how people attempt to bypass anticheat systems. As I said, kernel level protection is the only thing that can effectively stop Adrenaline usage. When combined with HWID bans, TPM validation, and other hardware based checks, bypassing the protection becomes significantly harder.

Posted
41 minutes ago, Celestine said:

Anything that is not a kernel level anticheat is totally useless on todays market. You cannot properly prevent botting because, without kernel access, you cannot detect injected DLLs or inspect processes at the level required to stop them.

It's good to see people contributing and trying different approaches, but in general, you won't be able to prevent bots from accessing and operating on your server with a usermode anticheat alone.

There is a solution that I have not posted or shared with anyone that can fully prevent Adrenaline/Helper from being used on servers. However, I want to give it more time before discussing it publicly so I can see how people attempt to bypass anticheat systems. As I said, kernel level protection is the only thing that can effectively stop Adrenaline usage. When combined with HWID bans, TPM validation, and other hardware based checks, bypassing the protection becomes significantly harder.

not true, you can change any bot program name so the ones that are injecting aint a problem any more, you can aswell bypass everything in a dll so his way of thinking isnt bad at all

Posted
1 hour ago, Celestine said:

Anything that is not a kernel level anticheat is totally useless on todays market. You cannot properly prevent botting because, without kernel access, you cannot detect injected DLLs or inspect processes at the level required to stop them.

It's good to see people contributing and trying different approaches, but in general, you won't be able to prevent bots from accessing and operating on your server with a usermode anticheat alone.

There is a solution that I have not posted or shared with anyone that can fully prevent Adrenaline/Helper from being used on servers. However, I want to give it more time before discussing it publicly so I can see how people attempt to bypass anticheat systems. As I said, kernel level protection is the only thing that can effectively stop Adrenaline usage. When combined with HWID bans, TPM validation, and other hardware based checks, bypassing the protection becomes significantly harder.

I agree that kernel-level protection offers much deeper visibility and control, especially when it comes to advanced bots and bypass techniques.

That said, I'm not trying to claim that a usermode solution is impossible to bypass. My goal is simply to increase the cost and complexity of bypassing the protection while keeping deployment simple, stable, and compatible for server owners.

A lot of Interlude server operators don't want to install kernel drivers or deal with the risks and maintenance that come with them. That's why I'm currently focusing on a layered approach: secure launcher architecture, HWID licensing, session validation, anti-debugging, injection detection, integrity checks, replay protection, and heartbeat monitoring.

I'm not ruling out kernel support in the future. Right now, my priority is gathering real-world feedback, improving the product, and learning how people attempt to bypass different protection layers.

I appreciate the feedback and the discussion.

Posted

🚀 IronLock Shield - Closed Beta Update

Hello everyone,

Since our first announcement, IronLock Shield has received several major protection upgrades.

IronLock Shield is a security platform developed specifically for Lineage II Interlude servers, focused on launcher integrity, runtime protection, session security, and anti-bot hardening.

Current protection features:

✓ Secure Launcher Architecture
✓ HWID-Based Licensing
✓ Signed Launcher Session System
✓ Gateway Session Verification
✓ Automatic Session Revoke on Critical Detection
✓ Replay Protection with Nonce Validation
✓ Runtime Integrity Verification
✓ Secure Update System

Client-side protections:

✓ Anti-Debug Protection
✓ Anti-Dump Protection
✓ DLL Injection Detection
✓ Manual Map Detection
✓ Remote Thread Detection
✓ Runtime Patch Detection
✓ Suspicious Handle Detection
✓ Memory Read / Write Guard
✓ Strict DLL Hash / Allowlist Control
✓ Launcher Self-Protection
✓ Watchdog Protection

Bot and automation hardening:

✓ Adrenaline / Memory Reader Hardening
✓ Runtime Decoy Memory Regions
✓ Fake Pointer-Chain / Offset Noise
✓ Per-Build Mutation System
✓ Pointer Scan Disruption
✓ Virtual Keyboard Input Detection
✓ Hookless Virtual Mouse Click Detection
✓ Raw Input Based Mouse Verification

Server and gateway security:

✓ Signed Launcher-to-Server Requests
✓ Build ID Binding
✓ HWID Binding
✓ IP / Session Binding
✓ Expired Session Blocking
✓ Revoked Session Blocking
✓ Gateway Runtime Session Checks
✓ Critical Detection Reporting Panel

Recent improvements:

✓ Improved protection against memory-reading bots
✓ Added decoy pointer-chain memory traps
✓ Added per-build mutation data
✓ Added stricter process handle policy
✓ Added hookless virtual mouse click detection
✓ Improved watchdog stability to reduce false positives
✓ Improved session revoke logic for critical detections
✓ Updated website and protection feature list

IronLock Shield is currently in closed beta.
Selected Lineage II Interlude server owners can receive 1 month of free access in exchange for testing and feedback.

Website:
https://ilshield.com

If you are interested, feel free to send me a private message or contact me through Discord.

Thank you.

IronLock Shield - Latest Closed Beta Update

Hello everyone,

We have released another protection update for IronLock Shield during the closed beta phase.

This update focuses on stronger anti-bot hardening, virtual input detection, suspicious driver traces, and stricter launcher/session enforcement.

Latest improvements:

✓ Known virtual input driver family checks
✓ Detection coverage for Interception, ViGEmBus, HidHide, HidGuardian, vJoy, vMulti, ScpVBus and FakerInput
✓ Active service, loaded-driver and device-object trace checks
✓ Improved virtual keyboard input detection
✓ Hookless virtual mouse click detection without interfering with mouse movement
✓ Raw Input based mouse verification
✓ Critical virtual input detections now close the client and revoke the gateway session
✓ Suspicious driver traces are handled as security events
✓ Stopped driver leftovers are ignored to reduce false positives
✓ Improved gateway disconnect logic for revoked or outdated launcher sessions
✓ Website feature list updated with the latest protection modules

IronLock Shield does not rely on gameplay behavior analysis.
The system focuses on external interference such as memory access, injected input, process handles, DLL injection, manual mapping, runtime patching, suspicious drivers and protected-route bypass attempts.

IronLock Shield is still in closed beta.
Selected Lineage II Interlude server owners can receive 1 month of free access in exchange for testing and feedback.

Website:
https://ilshield.com

If you are interested, feel free to send me a private message or contact me through Discord.

Thank you.

IronLock Shield - Latest Closed Beta Update

Hello everyone,

We have released another protection update for IronLock Shield during the closed beta phase.

This update focuses on stronger anti-bot hardening, virtual input detection, suspicious driver traces, and stricter launcher/session enforcement.

Latest improvements:

✓ Known virtual input driver family checks
✓ Detection coverage for Interception, ViGEmBus, HidHide, HidGuardian, vJoy, vMulti, ScpVBus and FakerInput
✓ Active service, loaded-driver and device-object trace checks
✓ Improved virtual keyboard input detection
✓ Hookless virtual mouse click detection without interfering with mouse movement
✓ Raw Input based mouse verification
✓ Critical virtual input detections now close the client and revoke the gateway session
✓ Suspicious driver traces are handled as security events
✓ Stopped driver leftovers are ignored to reduce false positives
✓ Improved gateway disconnect logic for revoked or outdated launcher sessions
✓ Website feature list updated with the latest protection modules

IronLock Shield does not rely on gameplay behavior analysis.
The system focuses on external interference such as memory access, injected input, process handles, DLL injection, manual mapping, runtime patching, suspicious drivers and protected-route bypass attempts.

IronLock Shield is still in closed beta.
Selected Lineage II Interlude server owners can receive 1 month of free access in exchange for testing and feedback.

Website:
https://ilshield.com

If you are interested, feel free to send me a private message or contact me through Discord.

Thank you.

   

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..