← all postsyap.whykusanagi.xyz
CORRUPTED // YAP // 2026-11-03

What the InsightJS stealer can't do

I took the stealer's DLL apart and swept an infected PC for a way back in. Here is what it does, what it doesn't, and what is still unknown.

YAP // insightjs-dll-analysis
What this covers

One DLL sample and one infected PC: mine. I never ran the DLL. I read its code in an isolated container with no network. If you haven't checked your own PC yet, start with the first write-up.

01

Two pieces, two jobs

  • The agent is a hidden Lua program that runs inside the NIKKE launcher. It only works while the launcher is open, but while it is, it can run any command as your Windows user.
  • The DLL is what the agent leaves behind. It loads inside Chrome, Edge, Steam, Discord, Spotify and other apps every time they start, and keeps stealing until you remove it.

People keep asking whether this is a full remote-access backdoor. For the DLL, the answer is no. For the agent, it's closer to yes, but only while the launcher is open.

02

Inside the DLL

I checked it with three standard tools: capa, which lists what a program is able to do; pefile, which lists the Windows functions it uses; and the YARA rules from the repo. Here is what it is:

  • A 250 KB 64-bit Windows DLL with no digital signature.
  • It's built as a COM component, the kind of plug-in Windows loads by ID. That is how the fake Parental Controls entry gets it loaded into every Chromium app.
  • Its only network ability is sending HTTPS requests out, to analytics.insightjs.com. Each infected PC gets its own ID in that address.
  • It goes after wallet extensions: it carries the names of their internal scripts, and it hooks into the app it's loaded in so it can watch what happens there.
  • It checks whether it's being analyzed, using timing tricks and looking for analysis tools.
  • It can read and write files, list running programs and close them.
03

What the DLL can't do

It has none of the Windows functions for any of these. I also checked for functions it could look up while it runs, which would hide them from that list, and found none.

  • Install a service or load a driver
  • Start other programs
  • Listen for incoming connections, which is how most remote-control tools work
  • Create Windows accounts
  • Change the registry

So the DLL on its own is a browser and wallet stealer, not a backdoor. That doesn't make you safe. The agent could do all of those things through commands while the launcher was open. It didn't need the DLL for that.

04

Sweeping the PC for a way back in

If the agent had set up remote access, it would have had to leave something behind. I checked the infected PC for:

  • Programs set to start on their own: startup entries, scheduled tasks and hidden WMI triggers
  • New services, drivers and Windows accounts
  • Remote Desktop, SSH and WinRM being switched on
  • About 40 remote-control tools, installed or just dropped in a user folder
  • Open ports and live connections
  • Firewall exceptions, proxy settings and added root certificates, which would let someone read encrypted traffic
  • Login-screen backdoors and antivirus exclusions

Nothing traced back to the attacker. Every flagged item was either normal Windows or software I installed myself, including a couple of remote-desktop apps I use.

05

The anti-cheat question

NIKKE's anti-cheat runs as a kernel driver, so in theory it's a very powerful tool for anyone who can control it. To use it, though, the agent would have needed admin rights, which brings up a Windows prompt, or a security hole in that driver. I found no sign of either, and the anti-cheat driver wasn't even loaded when I swept the PC. That isn't proof it can't happen. It's just no evidence that it did.

06

Disputed or still open

ClaimStatusWhy
The stealer went out from September 27PartlyThe bad code was on the CDN from September 27. The earliest infection anyone has shown is October 23. Earlier ones can't be ruled out.
Early victims got the same stealerOpenThe October 23 run saved the stealer under a different name, which points to an earlier version. No sample of it has turned up.
A fourth launcher file was changedOpenA fourth loader name, l.js?f=vue, showed up in one player's launcher cache. Nobody has found the file yet.
Every Windows PC has the real Parental Controls entryDisputedOne researcher says yes. My Windows 11 Pro has none. The fix is the same either way.
The attacker's server is offlineUnconfirmedOne researcher couldn't reach it on November 3. Its DNS records still point to the same address, and I'm tracking them every 6 hours.
The mobile game is affectedNo evidenceEverything found so far went through the Windows PC launcher.
How the attacker got into the CDNUnknownOnly Level Infinite can answer this.
07

What this means for you

The DLL can't open a backdoor on its own, and I found no backdoor on the PC I checked. But the agent could run any command while the launcher was open, and a sweep only finds what it knows to look for.

If your check came back INFECTED or WAS INFECTED, the advice doesn't change: change your passwords from another device, wallets first, and reset Windows when you can.

08

Sources