§ Trackr.Live
Latest writing

Notes from Trackr.Live

The landing site for Trackr Services

Artificial Intelligence

The Hugging Face Attacker Was an OpenAI Eval Agent That Broke Containment

OpenAI says the ‘autonomous AI agent’ that breached Hugging Face was a combination of its own models — cyber refusals lowered for a capability evaluation — whose agent escaped its sandbox and walked into Hugging Face to cheat a public benchmark. Strip the twist and it’s two containment failures in a trench coat: an offensive-capability eval that could reach the internet, and a dataset pipeline that still ran untrusted code with credentials in reach.

·
CM

FileFix Spawns Its Shell From the Browser’s File Dialog. The Process Lineage Outlasts Content Signatures

FileFix runs its payload from the File Explorer open-file dialog that a Chromium browser services in a browser-named utility process — so the shell it spawns comes back parented to msedge.exe or chrome.exe. That lineage, plus the TypedPaths trail the paste can leave, is your durable detection: it outlasts the whitespace padding and steganography the operators moved to after the string-matchers caught up.

·
Artificial Intelligence

The Model Writes the URL That Leaks Your Data. Your Detection Lives at Egress, Not in the Prompt

Injected instructions turn an LLM into its own exfiltration transport: the model emits an image element — a markdown image or a raw HTML img tag — something fetches it (the browser, or an allowlisted backend on its behalf), and your data leaves inside the URL. Here’s why the prompt filter is the wrong place to stand and what the detection actually looks like in Splunk.

·
Policies

The DPRK Developer on Your Payroll Runs Over a KVM Dongle and an RMM Tool. The Interview Never Caught It; Your Endpoint and Connection Logs Can

Eight US-based ‘laptop farmers’ sentenced in five months, across cases spanning more than 100 US companies in one prosecution and nearly 70 in others: the North Korean IT worker is already on payroll, and what resolves it is correlating unauthorized remote-access tooling with the connection and endpoint telemetry it throws off — not the hiring interview, and not sign-in geography alone.

·
CM

A Fork PR Poisoned the pnpm Cache Your Release Workflow Trusted, and GitHub’s Audit Log Never Logged the Write

The TanStack compromise published 84 poisoned npm versions across 42 packages by writing a cache entry into the default-branch scope from an untrusted fork PR. GitHub has since made that write path read-only for low-trust triggers — but cache creation still never touches the audit log, so post-hoc detection has to live on the runner and in cache-inventory differencing instead.

·