MotherSphere

NIKKE PC launcher compromise (November 2026)

Caution

From 2026-09-27, four official JavaScript files on Level Infinite's CDN contained attacker code. The NIKKE PC launcher loads these files. From Oct 24 at the latest, opening the launcher could install a remote-control agent: while the launcher was open, the attacker could run any command on your machine, read any file and take screenshots.

Update, 2026-11-03 20:40 GMT: three of the files were replaced on Nov 3 at 17:04, 17:13 and 17:21 GMT. The fourth, FeedList.feb647c9.js, was cleaned at the origin on Oct 28, but two CDN servers still delivered the modified copy at 20:23 GMT. The attacker's server no longer answered at 18:31 GMT. None of this undoes anything on machines that were already infected, and the old files may still be in your launcher's cache. Do not open the NIKKE PC launcher until Level Infinite confirms the fix, and clear its cache before you do.

This report comes from one infected machine, plus findings from other

neutralnikke

Check-NikkeK2f.ps1

A PowerShell script that checks a Windows PC for the "k2f" remote-access agent that was delivered through the NIKKE PC launcher in late 2026, and, only with your confirmation at each step, removes what it leaves behind.

Do not open the NIKKE PC launcher until Level Infinite confirms that all of its modified web files have been fixed. As of the last gist update, one file (FeedList.feb647c9.js) was still reported as modified.

TheSherlockHomie

Updating expired GPG keys and their backup 🔑🔐💻

I use a GPG key to sign my git commits.

An error like this one might be a sign of an expired GPG key.

error: gpg failed to sign the data fatal: failed to write commit object

krisleech

Renew GPG key

Given that your key has expired.

$ gpg --list-keys
$ gpg --edit-key KEYID

Use the expire command to set a new expire date:

gsimone

See

Léna Piquet (Froyok), [Breakdown] Shadow of the Colossus (PAL, PS2), 2012 https://www.froyok.fr/blog/2012-10-breakdown-shadow-of-the-colossus-pal-ps2/

The Making of Shadow of the Colossus (PDF, hosted with the breakdown above) https://www.froyok.fr/blog/2012-10-breakdown-shadow-of-the-colossus-pal-ps2/resources/making_of_sotc.pdf

Fumito Ueda interview, The Making of the Colossi https://glitterberri.com/extended-developer-interview/making-of-the-colossi/

qoomon

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

git commit -m"<type>(<optional scope>): <description>" \
 -m"<optional body>" \

karpathy

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.