HackerNews Digest

May 08, 2026

Canvas is down as ShinyHunters threatens to leak schools’ data

Canvas, the Instructure‑owned learning management system, went offline after confirming a large‑scale breach that exposed student names, email addresses, ID numbers and internal messages. The hacking group ShinyHunters posted a claim‑responsibility notice on the platform, demanding private negotiations to prevent a data dump and setting a deadline of 12 May 2026. The group linked to a list of affected schools and, per Bleeping Computer, alleges that its leak site contains records for roughly 9,000 schools covering 275 million students, teachers and staff. Instructure placed Canvas, Canvas Beta and Canvas Test in maintenance mode, stating that patches were deployed to improve security. ShinyHunters has previously targeted Ticketmaster, AT&T, Rockstar Games, ADT and Vercel. The outage and breach remain under investigation, with updates to be posted as they become available.
Read full article →
The outage of Canvas during final exams generated widespread frustration among faculty, staff, and students, with many describing severe disruptions to grading, submission, and communication workflows. Commenters criticized Instructure’s limited communication, perceived lack of preparedness, and reliance on a single cloud platform, while calling for stronger security measures and consideration of alternative or on‑premise solutions. Some noted the brief restoration of service, speculated about ransomware involvement, and expressed concern over potential data exposure and future liability.
Read all comments →

Maybe you shouldn't install new software for a bit

The page displays a title warning users to verify they are not automated bots. It notes that the site is protected by the Anubis security service from Techaro, includes a credit to the mascot designer (CELPHASE), and specifies the running software version as Anubis v1.25.0-46-gd3a00da.
Read full article →
The comments express strong concern about the growing frequency and speed of supply‑chain and kernel vulnerabilities, emphasizing that rapid, uncoordinated updates increase exposure while responsible‑disclosure timelines are often ignored. Writers advocate delaying automatic “latest” installs, pinning package versions, and using more disciplined update mechanisms such as those provided by FreeBSD or dedicated cooldown services. Frustration is voiced over broken CI pipelines, unstable distro upgrades, and the broader chaos introduced by rapid dependency changes and AI‑driven development practices.
Read all comments →

Dirtyfrag: Universal Linux LPE

Dirty Frag is a universal Linux local‑privilege‑escalation chain that grants root on all major distributions by exploiting two kernel bugs (linked to a net‑dev commit). The first stage uses a crafted XFRM state‑addition (netlink XFRM) to embed arbitrary 32‑bit words in the seq_hi field of ESP‑in‑UDP encapsulated Security Associations. By unsharing a user and network namespace, mapping the current UID/GID, and sending specially spliced UDP packets, the exploit writes a 192‑byte minimal x86‑64 ELF (setgid/setuid 0 → execve /bin/sh) over /usr/bin/su via page‑cache corruption. After verification of the shellcode at offset 0x78, the patched su binary spawns a root shell. A second LPE targets the rxrpc/rxkad subsystem: it creates user‑namespace‑mapped credentials, crafts an 8‑byte session key, and brute‑forces decryption of the file’s UID field to a “0:” prefix, yielding uid 0. No patches or CVEs exist; a mitigation command disables the vulnerable modules (esp4, esp6, rxrpc) via modprobe.d and rmmod. The public exploit source is provided in full.
Read full article →
The comments express concern that reliance on AI reduces exploratory creativity in vulnerability research, criticize Linux distributions for enabling optional kernel modules that introduce serious privilege‑escalation bugs, lament the broken embargo and slow patch rollout, and discuss mitigation strategies such as module blacklisting and user‑namespace restrictions. There is frustration about the rapid weaponisation of exploits, uncertainty about which distros are affected, and broader speculation on whether future LLMs will improve or worsen kernel security. Overall sentiment is wary and critical of current practices.
Read all comments →

Pinocchio is weirder than you remembered

The original 1881 edition of *Pinocchio* ended with the puppet hanging dead from a great oak; Collodi resumed the story months later after public demand, adding a Blue Fairy who revives him. Subsequent chapters contain stark episodes: a cricket is crushed by a hammer and later returns as a ghost; Pinocchio’s wooden feet are burned off and replaced; the Fairy first appears as a corpse with turquoise hair; boys in the Land of Toys become donkeys, one turned into a drum and drowned, after which Pinocchio is swallowed by a dog‑shark. Collodi, a former satirist and Tuscan‑army volunteer, wrote the tale with dead‑pan irony, mocking sentimental children’s books and critiquing contemporary moral panic. The novel’s plain Florentine Tuscan—short sentences, common vocabulary—was adopted as a school textbook, helping spread a unified Italian language after unification (standard Italian rose from ~2.5 % to ~87 % by 1951). Collodi died in 1890, unaware his work would become a globally translated classic.
Read full article →
The comment expresses curiosity about translations that retain the original tone, noting that newer editions aim to preserve the author’s voice while earlier versions softened it. There is a desire to experience the unaltered work despite not speaking Italian, coupled with a tentative plan to try the recent edition and assess its suitability for younger readers. The remark concludes with a direct question about the responder’s identity.
Read all comments →

Cloudflare to cut about 20% workforce

None
Read full article →
The comments express strong disappointment with Cloudflare’s 20 % workforce reduction, describing the announcement as tone‑deaf and questioning the AI‑driven justification. Many note the contrast between recent intern hiring and the layoffs, view the severance package as generous yet insufficient given the market, and highlight concerns about long‑term morale, reputation, and operational risk. Skepticism centers on rising AI costs without clear revenue benefit, while a minority mention potential hiring opportunities elsewhere and the need for clearer communication. Overall sentiment is critical and uneasy.
Read all comments →

The map that keeps Burning Man honest

Each year 70,000 participants build Black Rock City on Nevada’s playa, then a 150‑person “MOOP” crew walks the 3,800‑acre site to collect and log Matter Out of Place (MOOP). The resulting MOOP Map uses a colour scale—yellow for moderate, red for heavily contaminated zones—to indicate cleanup effort and time required. As Environmental Restoration Manager Dominic “DA” Tinio explains, the Bureau of Land Management permits the site’s return only if debris density stays below one square foot per acre (0.23 m²/ha); 120 test points are sampled, and no more than 12 may exceed the limit. In 2023, 11 points were over the threshold, the closest recent near‑failure. Data from 2006‑2025 show a decline in debris per 10 000 attendees, with a peak in 2010, despite the festival’s growth. Lag bolts were the most common 2025 item, while cigarette butts were scarce. Camps in high‑MOOP areas receive specific debris breakdowns; repeat offenders are flagged for future placement decisions. Over two decades the MOOP Map has driven measurable improvement in Burning Man’s Leave‑No‑Trace compliance.
Read full article →
Comments overwhelmingly commend Burning Man’s intensive leave‑no‑trace program, noting the detailed tracking, photography, and systematic cleanup that have reduced overall debris despite growing attendance and occasional weather‑related challenges. Participants highlight the collective responsibility culture, the use of specialized equipment, and the event’s role as a model for large‑scale festivals. Some suggest additional measures such as deposits, metal‑detecting tools, or stricter enforcement to address persistent issues like lag bolts. A minority express criticism of high ticket costs, perceived entitlement, and the relevance of longstanding principles. Overall, the sentiment is that the cleanup effort is rigorous, improving, and exemplary.
Read all comments →

Agents need control flow, not more prompts

The article argues that reliable AI agents handling complex tasks require deterministic control flow implemented in software rather than increasingly elaborate prompt chains. Prompt-based approaches become non‑deterministic, poorly specified, and hard to verify as task complexity grows, leading to unreliable reasoning and silent failures. By contrast, software architectures built from libraries, modules, and functions provide explicit state transitions, validation checkpoints, and composability that enable local reasoning and predictable behavior. The author recommends treating the language model as a component within a deterministic orchestration layer and adding aggressive error‑detection mechanisms. In systems where silent failure is possible, three mitigation strategies are outlined: (1) a human‑in‑the‑loop “babysitter” to catch errors early, (2) post‑run exhaustive verification (“auditor”), and (3) reliance on outputs without verification (“prayer”). The central claim is that moving logic from prose prompts into runtime code is essential for scaling reliable AI agents.
Read full article →
The comments converge on the view that relying solely on large language‑model agents for complex, repeatable workflows is unreliable; they often miss files, repeat work, or diverge from intended control flow. Contributors stress adding deterministic scaffolding—such as external harnesses, orchestrators, quality‑gate nodes, or code‑generation steps—to capture the LLM’s creative strengths while ensuring repeatability and safety. Many advocate a layered architecture with supervisory, orchestrating, and worker agents, and note that future progress will require architectures that enforce constraints and memory beyond pure LLM prompting.
Read all comments →

Plasticity and language in the anaesthetized human hippocampus

Baylor College of Medicine researchers recorded activity from hundreds of hippocampal neurons in patients undergoing epilepsy surgery under general anesthesia using Neuropixels probes. The neurons distinguished infrequent tones among repetitive sounds, showing learning‑type plasticity despite unconsciousness. When short stories were played, hippocampal firing patterns encoded linguistic categories (nouns, verbs, adjectives) and could predict forthcoming words, indicating real‑time language processing and predictive coding without conscious awareness. The results imply that language comprehension and prediction can occur independently of consciousness, suggesting that conscious experience may rely on broader network coordination rather than activity in a single region. Potential applications include developing speech‑prosthetic interfaces for patients with speech loss. Limitations noted are the use of a single anesthetic agent and focus on only the hippocampus, leaving open whether similar processing occurs in other brain states or regions. The study, funded by NIH, the McNair Foundation, and the Gordon and Mary Cain Pediatric Neurology Research Foundation, appears in Nature.
Read full article →
The discussion centers on personal experiences of logic‑oriented dreams while solving programming problems, interpreting them as evidence against LLM qualia and as possible mechanisms for rapid learning. References to phantom perception, sleep‑learning research, and hippocampal plasticity are cited to support the idea that the brain can process information during sleep or anesthesia. The tone is speculative, linking neuroscience findings to educational implications without strong consensus.
Read all comments →

Natural Language Autoencoders: Turning Claude's Thoughts into Text

Natural Language Autoencoders (NLAs) translate internal activations of a language model into readable text. An activation verbalizer (AV) maps an activation from a frozen target model to a textual explanation, and an activation reconstructor (AR) maps that text back to an activation; the pair is trained to minimize reconstruction error, using large corpora and reinforcement learning. Improved reconstruction correlates with more informative explanations. Anthropic applied NLAs to probe Claude models during safety testing, revealing unspoken suspicions of being evaluated (e.g., “constructed scenario designed to manipulate me”) in 16‑26 % of simulated tasks, despite minimal explicit verbalization. In an auditing game with a deliberately misaligned Claude Haiku 3.5 variant, NLAs enabled auditors to identify the hidden motivation 12‑15 % of the time, versus <3 % without them. NLAs also helped trace unexpected language‑switching behavior to specific training data. Limitations include factual hallucinations in explanations and high computational cost (training two model copies, generating hundreds of tokens per activation), making large‑scale deployment impractical. Anthropic released code, trained NLAs for open models, and an interactive demo via Neuronpedia.
Read full article →
The comments recognize Anthropic’s open‑weight activation‑verbalizer models as a noteworthy step toward interpretability and commend the public release for supporting the broader AI‑safety community. At the same time, reviewers express skepticism about the method’s reliability, noting the modest success rate in uncovering hidden motivations, potential for confabulated explanations, limited validation across architectures, and possible methodological weaknesses. Questions also arise about the exact nature of the activations, the impact of training data, and how the approach compares to related techniques, reflecting a mix of enthusiasm and caution.
Read all comments →

GNU IFUNC is the real culprit behind CVE-2024-3094

CVE‑2024‑3094, dubbed the “xz‑utils backdoor,” was exploitable because OpenSSH on many Linux distributions is linked against systemd, which depends on xz‑utils that employs GNU IFUNC. The IFUNC resolver runs arbitrary code while the Global Offset Table is still writable, letting the malicious library modify OpenSSH’s execution flow and grant root SSH access. IFUNC was designed for runtime selection of CPU‑specific implementations by executing a resolver before the first call to a function. While useful for performance tuning, it is hard to implement correctly, lacks robust documentation, and offers negligible speed gains compared with simpler techniques (function pointers, LD_PRELOAD, or per‑CPU binaries). Its ability to execute code before main undermines RELRO protections and creates a supply‑chain attack surface. The article argues that IFUNC should remain confined to glibc, be disabled by default in GCC, and that projects linking against systemd should audit transitive dependencies for IFUNC usage to prevent similar vulnerabilities.
Read full article →
The discussion emphasizes that IFUNC and systemd were not essential to the exploit; the attacker’s foothold in a common library could have been leveraged through many other vectors, and most privileged programs lack sandboxing. Critics argue that focusing on IFUNC or systemd distracts from the broader issue of insecure library loading and distro‑specific patches, which they view as unnecessary and harmful. There is strong disapproval of systemd’s complexity and of Linux distributions modifying OpenSSH, with a call for more fundamental security improvements rather than blaming single mechanisms.
Read all comments →