The launcher installed it for you
NIKKE's own CDN carried attacker code from September 27, and by late October the PC launcher was installing a wallet and password stealer. Here is how to check your PC and what to change first.
I corrected the timing. The loader code sat on the CDN from September 27, but on the PC I checked, the stealer itself first arrived on November 1. The launcher logs show it downloading on 3 of the 8 times the launcher opened between November 1 and 3.
Second correction: another player's PC, with three NIKKE installs, shows the stealer starting on October 23 and again through November 2. So it was going out in late October, not from November 1. Their October 23 run also saved the stealer under a different name from every later run, which points to an earlier version of it. A fourth loader name, l.js?f=vue, turned up in someone else's launcher cache.
If you already uninstalled NIKKE, you can still check, but the result is less certain. See the new note under Check your PC.
Another researcher found a third modified file, so it was three files, not two. Level Infinite replaced two of them on November 3, and stale copies of the third were still on some of their CDN servers that evening. None of that cleans a PC that already got hit.
What happened
On September 27, someone changed three JavaScript files on the CDN that NIKKE's PC launcher loads its own pages from. They added a few lines that pull more code from insightjs.com, a domain registered that same day. All you had to do was open the launcher.
The stealer didn't come every time. On the PC I checked it arrived on 3 of 8 launches between November 1 and 3. Another player's logs show it as early as October 23. If you opened the launcher any time since late September, run the check anyway. It costs you a minute.
I took apart the stealer DLL from an infected PC and traced the whole chain on that machine. Everything below is either something I saw on that PC or something I checked against public write-ups. The full source list is in the repo.
How it gets in
- The launcher's built-in browser loads the changed file, and that file pulls a script from
insightjs.com. - The script asks the launcher's own downloader, the one NIKKE signed, to fetch a 205 KB file called
insight.bundle. It saves it under a fake log file name. - That file runs as a hidden Lua program inside the launcher. While the launcher is open it can run commands, read your files, screenshot every monitor, dump Windows Credential Manager, and check 264 places where apps keep keys and config.
- It drops
platform_experience_helper.dllinto your Chrome folder and registers it, in your user registry, as Windows Parental Controls. - Apps built on Chromium load that component when they start, so the DLL starts with them. It needs no admin rights, and a Chrome update leaves it in place.
- Inside those apps it reads saved passwords, login cookies and 28 crypto wallets, and sends them to
analytics.insightjs.com.
On the PC I checked, the DLL was running inside Steam, Spotify, the ChatGPT app, EA Desktop and NVIDIA's overlay. I killed those processes and it was back inside them within seconds.
It downloads the payload again every time it starts.
Uninstalling NIKKE won't remove the DLL either. It lives in your Chrome folder, so you have to remove it yourself.
Before you ever open the launcher again, clear its cache: %APPDATA%\nikke_launcher\tbs_cache. It can still hold the modified files after the CDN fix. -Remove does this for you.
Check your PC
I put the scripts on GitHub: whykusanagi/nikke_malware. They are PowerShell, they change nothing unless you ask them to, and they send nothing anywhere.
- Download the latest kit and unzip it.
START-HERE.txtinside walks you through it. - Open the
scriptsfolder and double-clickRun-Check.cmd. - Read the verdict at the end. A report folder lands on your Desktop.
- CLEAN: nothing found.
- WAS INFECTED: the payload ran at some point and nothing is active now. Your passwords and wallets are still at risk.
- INFECTED: it is running right now.
- SUSPICIOUS: something needs a human look. Open the report.
- UNKNOWN: NIKKE isn't installed any more, so its logs are gone. Nothing is running now, but the check can't tell whether the stealer ran before.
Already uninstalled NIKKE? Uninstalling deletes the launcher's logs, which are the best proof of whether the stealer ran. It doesn't remove the stealer's DLL or its registry entry, and the check still finds those. If you opened the PC launcher between late September and November 3, change your passwords anyway.
If you get INFECTED or WAS INFECTED, double-click Run-Remove.cmd in the same folder.
It backs up the registry key, closes the apps that have the DLL loaded, moves the DLL into a quarantine folder, deletes the agent's temp files and clears the launcher cache. Save your work first. You can reopen everything straight after.
The report folder has your PC name, your Windows username and file paths in it. Don't post it in a public channel.
What to change first
Do this from your phone or another computer. If the stealer is still on the PC, a new password typed there goes the same way as the old one.
| # | What | What to do |
|---|---|---|
| 1 | Crypto wallets | Make a new wallet with a new seed phrase and move your funds now. A seed phrase can't be changed, and theft from a wallet can't be reversed. Revoke your token approvals too. |
| 2 | Your main email | Change the password and sign out of every session. Stolen login cookies get past your password and 2FA, so the sign-out matters more than the new password. |
| 3 | Password manager or browser sync | Change the master password, sign out everywhere, then work through what is saved inside it. |
| 4 | Banks, exchanges, PayPal | New passwords, sign out sessions, new API keys. Check withdrawal allowlists and recent activity. |
| 5 | GitHub, cloud, SSH keys, AI tools | Revoke tokens and API keys and replace SSH keys. Log out of Claude, Codex, Gemini and Cursor and back in. A stolen developer token can be used against other people. |
| 6 | Steam, Discord, Epic, Level Infinite | Change passwords and sign out every session. Check Steam trades and market history. |
| 7 | Everything else | Anything saved in a browser or in Windows Credential Manager. Turn on app-based 2FA as you go. |
Expect phishing for a while. The attacker knows which services you use.
If you want to be sure
Reset Windows. While the launcher was open, the Lua program could run any command on your account, and I can't give you a list of everything it did. The repo has a second script for after the reset. It checks every user profile and confirms the DLL is gone.
If you run security tools for other people, the repo also has YARA and Sigma rules, the indicators and a MITRE ATT&CK mapping. Each victim gets a different build of the DLL, so a hash list won't catch it. The rules look at where it sits, the missing signature and the code inside.
Linux and Steam Deck
Proton doesn't protect you. The Chrome DLL part is Windows-only, so my checker has nothing to find on Linux. But while the launcher was open, the attacker could run commands and read files, and Wine shows your Linux home folder to Windows programs as a drive. If you played through Proton, treat your SSH keys, browser profiles and shell config as exposed and work through the list above.
The launcher doesn't check who it's talking to
On my PC, the launcher's downloader made 30 secure connections, to Level Infinite's own servers and to the attacker's. Every one failed the certificate check, and the launcher carried on anyway. The log line reads unable to get local issuer certificate (20), continuing anyway. It never logged a successful check.
This isn't how the attacker got in. They had a real certificate and real access to the CDN. But it means anyone on your network path, like a hostile café Wi-Fi or a hacked router, could feed the launcher their own files and it would take them. Level Infinite should fix that whatever else they find.
Where I land
NIKKE's own servers handed this out, through NIKKE's own signed downloader. If you got hit, you did nothing wrong.
I'm not opening the PC launcher until Level Infinite says the CDN is clean and explains how three of its files got changed. If you got hit, tell their support. One report is easy to brush off as a single bad PC. A pile of them is harder to ignore.
Sources
- whykusanagi/nikke_malware, detection scripts, rules, indicators and the full write-up
- NGA community thread, where it was first spotted
- CDN and payload teardown, public write-up
- Sheisback/nikke_malware_scanner, another community scanner