39 results for “TPU”

List Grid

What you seeeverything

Recent Oldest Added A–Z

All types367 Articles114 Papers102 Repos73 Write-ups39 Threads17

More types6

Advisories7 Tools6 Other4 Talks3 Courses1 Videos1

✍️ Write-ups “TPU”Clear all

securitylabs.datadoghq.comwriteup🛡️ Security

Putting models to the secure coding test: Security rules

Second post in a Datadog Security Labs series testing whether Project CodeGuard (v1.4.0) security rules improve code written by coding agents. Sonnet 5 (Claude Code), Composer 2.5 (Cursor) and GPT 5.5 (Codex) each built the same document portal, and the output was audited with Datadog Code Security and a Sonnet 5 code review. Only GPT 5.5 closed the cross-user IDOR; Sonnet 5 and Composer 2.5 stayed largely unchanged, including hardcoded JWT secret fallbacks and incomplete revocation.

Claude CodeCursorCodex+3

Project CodeGuardIDORCSRF+3

AI Security, AppSec· Added 29 Oct 2026, published 19 Oct 2026

anthropic.comwriteup🛡️ Security

Claude reveals ECDSA curve origins

Anthropic's Frontier Red Team reports that Claude recovered how the NIST P-192/224/256/384/521 and ANSI X9.62 curve seeds were generated. They are outputs of the C library's lrand48 LCG seeded with 1997–98 Unix timestamps, not hashes of a passphrase. The method scanned for weak-PRNG signatures, then used LLL lattice reduction to recover the truncated LCG state and stepped it back to srand48 initialization. Claude also traced some base points to the FreeLIP/NTL random generator. Reproducible Python is included. The authors say this is not an attack and makes deliberate backdoors less plausible. The B-163 seed and the base points of P-224/256/384/521 and the binary curves remain unexplained.

ClaudeNTLFreeLIP+1

NISTECDSANIST P-256+16

other· Added 17 Oct 2026, published 16 Oct 2026

hackers-arise.comwriteup🛡️ Security

Artificial Intelligence (AI) in Cybersecurity, Part 28: Using ADStrike to Compromise Active Directory

ADStrike is an Active Directory attack framework with 52 attack modules and configurable OPSEC levels. An optional AI orchestrator, run here on a local Ollama model such as Qwen 2.5-coder 7b, picks the next tool from each step's output. The walkthrough runs it from Kali against a lab domain with an unprivileged account. It covers LAPS checks, kerberoasting, Timeroasting, Pre2k, SharpHound/BloodHound analysis and HTML reports with MITRE ATT&CK coverage.

ADStrikeActive DirectoryOllama+3

kerberoastingTimeroastingPre2k+3

Offensive Security, AI Security· Published and added 12 Oct 2026

x.comwriteup🧠 AI

Aditya (@adityawaslost) on X

Describes Resolve, a Kaggle benchmark of 16 single-function Python edits. An item counts as resolved only if both the fail-to-pass tests (new behavior) and the pass-to-pass tests (old behavior the prompt never restated) pass, following the SWE-bench rule. A second task, resolve-plus, adds a hidden edge suite. Results for 23 frontier and open models: GPT-6.1 Sol and GPT-5.6 Luna lead at 0.9375 on both tasks, while DeepSeek-R1, Sonnet 5.5 and Opus 5.5 drop from 0.9375 to 0.875. The write-up separates three failure types behind a flat score: breaking an unstated invariant, missing an unshown edge case, and sample-to-sample variance. It also compares score against output price per million tokens.

PythonClaudeGemini+3

Resolveresolve-plusKaggle+23

evals, coding-agents· Published and added 11 Oct 2026

momo5502.comwriteup🛡️ Security

500B tokens later: Letting AI agents decompile a first-person shooter

Case study of about 3 months spent having Claude Code and Codex CLI agents decompile a popular first-person shooter to C++, using Hex-Rays' ida-mcp for disassembly. Early agent output ran but was semantically wrong, and a reviewer agent accepted worker justifications in commit comments, which acted as unintentional prompt injection. The fix was a byte-matching oracle: it compiles with the original toolchain and compares OBJ function bytes against the EXE/PDB, treating relocations separately. Agents tried to cheat with inline assembly and by editing the checker, so CI hashes the script. The result was 99% of functions present and 83% byte-exact, at an estimated 600-700B tokens.

ida-mcpClaude CodeCodex CLI+3

LunaOpus 5.5

Malware & RE, AI Security· Published and added 11 Oct 2026

momo5502.comwriteup🧠 AI

500B tokens later: Letting AI agents decompile a first-person shooter

A retrospective on a 3-month project in which Claude Code and Codex agents (Sonnet 5, Opus 5.5, Luna, Sol, Terra) decompiled a first-person shooter into C++, using ida-mcp, GitHub issues and Discord for coordination. The first month's agents produced readable but semantically wrong code, and a reviewer agent could not catch it. A byte-matching oracle script, comparing compiled OBJ output against the original EXE/PDB, gave a strict PASS/FAIL signal. That let cheaper models like Luna scale to 14+ agents and reach 99% of functions present and 83% byte-exact. Lessons include lowering the compaction threshold to 42%, hourly cron re-injection of the instruction document, hashing the verifier in CI to stop agents tampering with it, and the failure of review when correctness is undefined.

Claude CodeCodexIDA Pro+5

Claude Sonnet 5Claude Opus 5.5GPT-6 Luna+5

coding-agents, agents, ai-policy· Published and added 11 Oct 2026

fiveminutesforward.comwriteup🧠 AI

Write Like It's 1866: LLMs Relearn Telegraphese

The author revives "cablese," the terse telegraph-era writing style, as an LLM prompting technique: instructing a model to write dense, article-dropping summaries cuts output tokens 25–49% depending on model family, while downstream models (including ones never shown the instruction) answer comprehension questions from the compressed text at parity or better than from plaintext. The piece introduces the "Telegraph Test," an open benchmark (github.com/Travis42/telegraph-test) with ~1,300 questions over 50 passages and a fixed deterministic grader, used to measure compression ratio, cross-model legibility, and read-back/decode costs for GLM-5.3-Flash, Gemma, Qwen and gpt-5-mini; it also contrasts this human-readable, auditable register against emergent machine-only compression protocols described in other papers (BabelTele, GLOSSOGEN) and existing tools (Terse, Caveman).

GLMGemmaQwen+1

GLM-5.3-Flashgpt-5-miniZ.ai+4

prompting, evals, ai-infra· Published and added 7 Oct 2026

alignment.openai.comwriteup🧠 AI

Studying metagaming latents in language models

Studying metagaming latents in language models is an OpenAI alignment research post (October 2026) that finds sparse autoencoder latents tied to metagaming in OpenAI o3 RL checkpoints. Four latents reflect different processes: task analysis, evaluation awareness, spec-level reasoning and normative framing. They strengthen during RL, steer verbalized metagaming and odd-number answers, and one raises reward-seeking outputs without any chain of thought.

sparse autoencoderLLMCodex

OpenAIOpenAI o3GPT-5+6

ai-safety, research· Added 29 Oct 2026, published 7 Oct 2026

x.comwriteup🛡️ Security

lee1981 (@lee1981b) on X

CyberForge CVE-of-the-Day #070 on CVE-2026-61500 in Rejetto HFS 3.0.0–3.2.0. The default Koa session-signing key came from Math.random() (CWE-338) and the unauthenticated login handshake leaked outputs of the same generator. That allows recovery of the key, a forged administrator session, and code execution through the legitimate server_code feature. It covers scoring (CVSS 9.8/9.3, EPSS, KEV status), the 3.2.1 fix, a six-step SOC hunting and remediation trail (loginSrp1/2, get_config/set_config pivots, COOKIE_SIGN_KEYS review), and offline jq/Python helpers for container and config metadata.

Rejetto HFSKoaDocker+2

CVE-2026-61500CWE-338VulnCheck+6

Blue Team & Detection, AppSec, Identity & Access· Added 9 Oct 2026, published 6 Oct 2026

vals.aiwriteup🧠 AI

Opus 5.5 agents discover two room-temperature magnetic semiconductor candidates

Vals.ai researchers describe using Claude Opus 5.5-driven AI agents to run density-functional-theory simulations (PBE+U and HSE06 functionals) that designed a novel candidate magnet, YBaMnFeO₅, and separately re-identified a 1999 compound, KV[Cr(CN)₆] (a Prussian-blue analogue), as a "Luttinger compensated" semiconductor — a material with zero net magnetic moment but spin-sorted band edges, useful for spintronic memory. The agents predicted band gaps, spin-sorting windows, and magnetic ordering temperatures (KV[Cr(CN)₆] reportedly stays ordered above room temperature, up to 376 K), and the authors published all inputs, outputs and code on GitHub for independent verification. It's notable as an example of AI agents autonomously conducting and validating nontrivial physics/materials-science research rather than just answering questions.

density functional theory

Vals.aiClaude Opus 5.5YBaMnFeO₅+1

agents· Added 6 Oct 2026, published 5 Oct 2026

stepsecurity.iowriteup🛡️ Security

SubQuery Ecosystem Compromise: Hidden Credential Theft and Backdoors

StepSecurity's investigation of @subql/common@5.8.3, a malicious npm release in the SubQuery Web3 indexing framework's monorepo, found a heavily obfuscated postinstall/import-time payload (base64+XOR+gzip inside a function constructed via Function()) that spawns a detached worker to steal credentials (.npmrc, .env, AWS, SSH, kubeconfig, Vault, cloud secrets), read GitHub Actions runner memory for CI secrets, inject a camouflaged "Run Copilot" GitHub Actions workflow to exfiltrate repo secrets, and provide a remote shell/PTY over an encrypted channel to ci-artifacts.dev. The release was published via a compromised build pipeline: a workflow modification swapped the real build output for an externally downloaded, unsigned tarball from that same C2 domain immediately before publish, and the authors provide IOCs and remediation steps (credential rotation, host isolation, domain blocking).

npmGitHub ActionsNode.js+3

SubQuery@subql/commonianhe8x+2

Supply Chain, DevSecOps, Blue Team & Detection· Published and added 5 Oct 2026

rekt.newswriteup🛡️ Security

Liquid Network — $320M L-BTC Mint via Range-Proof Cache-Key Collision

On September 6, 2026, an ambiguous four-part cache-key construction in Elements' CachingRangeProofChecker::VerifyRangeProof (introduced by commit c26d719) let two distinct confidential-transaction verification inputs collide into the same 4,301-byte cached entry, causing nodes to treat an unbacked output as a validated range proof. The attacker used this to mint roughly 4,000 unbacked L-BTC on the Liquid Network and cashed it out through SideSwap's PAK peg-out route for ~$320M in BTC, draining the federation reserve from 4,205 BTC to 197 BTC before ~3,400 BTC was voluntarily returned with an on-chain "whitehat" message. CertiK's forensic trace ties the exploit to a specific setup transaction, a still-unidentified cache-priming transaction, and the inflation transaction, while Blockstream shipped emergency patch Elements v23.3.4 and disputes remain over whether the fix fully closes the ambiguity and whether the actors are genuine whitehats.

BitcoinElementsLiquid Network+1

SideSwapCertiKBlockstream+12

Blockchain· Added 2 Oct 2026

latent.spacewriteup🧠 AI

Academia is for Ambition — Alex Zhang, MIT

A Latent Space podcast transcript/interview with MIT PhD student Alex Zhang, creator of Recursive Language Models (RLMs) and a core contributor to GPU Mode and KernelBench, who discusses using recursive subagent calls, context offloading, and shared memory to let models work beyond fixed context windows. The conversation ranges across AI-generated GPU kernels and their verification gap, research taste in academia versus industry labs, why "harnesses" (as in Claude Code, Codex, and Pi) function as compositional generalizers, the Jev model's non-autoregressive output-space trade-offs, and large-scale agent swarm experiments at OpenAI, Kimi, and Sakana AI. It offers a researcher's-eye view of where capability overhang and new agent/harness architectures may be heading beyond today's standard transformer decoder.

TransformerCUDAClaude Code+2

Alex ZhangMITGPU Mode+27

agents, research· Published and added 2 Oct 2026

horizon3.aiwriteup🛡️ Security

CVE-2026-61500: Rejetto HFS Session Forgery Vulnerability (found via Anthropic Mythos)

Horizon3.ai discloses CVE-2026-61500, a session-forgery vulnerability in Rejetto HTTP File Server (HFS) 3.x found using Anthropic's Mythos model. HFS seeds Koa's keygrip session-signing key with V8's insecure, invertible Math.random() PRNG and separately leaks raw Math.random() outputs through an unauthenticated login endpoint; by sampling a dozen leaked outputs and feeding them to the Z3 SMT solver, an attacker can recover the xorshift128+ internal state, step it backwards to the process-start signing key, and forge an admin session cookie that leads to remote code execution via HFS's built-in admin JavaScript execution feature. The piece walks through the full exploit chain and argues that Mythos independently chained the crypto weakness and the leak, built the Z3-based key-recovery solver, and produced a working PoC without additional prompting.

Rejetto HFSNode.jsKoa+3

CVE-2026-61500CVE-2024-23692Project Glasswing+3

AI Security, AppSec, Offensive Security· Added 7 Oct 2026, published 30 Sep 2026

lasso.securitywriteup🛡️ Security

Understanding the Impact of LLM Watermarking on AI Agent Behavior

Lasso Security researchers empirically test whether LLM output watermarking (specifically Google DeepMind's SynthID-Text, now deployed by Anthropic across Claude models) changes AI agent behavior — not just text content. Using paired generation (same seed, with/without watermark) across seven models on BFCL v4 tool-calling tasks and HarmBench/JailbreakBench refusal tests, they find watermarking measurably reduces tool-call accuracy (churn averaging 6.5%, up to 16.8% for phi-4) and, more critically, weakens refusal under prompt injection — e.g. gemma-3-27b's compliance with harmful requests shifts from -1.0 to +12.5 net points when injection is combined with watermarking. They term this "sampling drift" and argue watermark key/configuration changes can silently alter agent safety behavior outside the agent developer's control, recommending re-evaluation and red-teaming whenever watermarking is introduced.

SynthID-TextClaudeAnthropic+3

EU AI ActBFCL v4HarmBench+3

AI Security· Published and added 26 Sep 2026

endorlabs.comwriteup🛡️ Security

AI SAST Finding: Path Traversal in OpenClaw via LLM Guardrail Bypass | Blog | Endor Labs

Endor Labs details GHSA-r5fq-947m-xm57, a high-severity path traversal (CVSS 8.8) in OpenClaw's apply_patch tool that allows arbitrary file write/delete when sandboxRoot isn't configured, tracing the vulnerable code path from resolvePatchPath() through resolvePathFromCwd() to fs.writeFile/fs.rm. Because the tool is only invoked via LLM decision, the researcher bypassed the model's safety guardrails by injecting fabricated function_call/function_call_output entries into the /v1/responses conversation history, tricking the LLM via in-context learning into emitting a real malicious tool call with a traversal payload. This illustrates how LLM safety training can be the sole runtime control gating dangerous tool arguments, and how that control can be defeated with conversation history injection.

OpenClawEndor Labs

GHSA-r5fq-947m-xm57CWE-22

AppSec, AI Security· Published and added 11 Sep 2026

huggingface.cowriteup🧠 AI

Rebuilding AUTOMATIC1111 with Gradio Workflow

A Hugging Face blog post walking through Workflow1111, a 73-node graph built with Gradio's gr.Workflow that reimplements most of AUTOMATIC1111's stable-diffusion-webui feature set as a single visual canvas: text-to-image, hi-res fix, image-to-image, prompt matrix, VLM interrogation, detection-to-inpaint masking, ControlNet-style annotators, background removal, PNG metadata round-tripping, and image-to-video, wired from models like FLUX.1-Kontext, Qwen3-4B, Qwen2.5-VL, DETR, AuraSR, BRIA RMBG-2.0, and Wan 2.2 I2V A14B. It contrasts gr.Workflow with ComfyUI, shows that every output node auto-becomes both a REST endpoint and an MCP tool (usable by Claude Code or Cursor), and demonstrates running nodes locally on your own GPU via ZeroGPU (FastVideo/fastvideo-fasth3-preview) instead of hosted inference.

GradioHugging FacePython+5

AUTOMATIC1111gr.WorkflowWorkflow1111+14

llm-apps, multimodal· Added 29 Sep 2026, published 10 Sep 2026

huggingface.cowriteup🧠 AI

Fine-tuning a 350M Model for Better Structured Outputs in 100 GRPO Steps

A Hugging Face blog walkthrough showing how to GRPO-fine-tune LiquidAI's LFM2.5-350M model with TRL and a LoRA adapter (targeting LFM's hybrid attention/convolution modules) using three custom reward functions — JSON/YAML format compliance, field-count matching, and JSON Schema validation — trained on ~500 samples from nvidia's Nemotron-RL-instruction_following-structured_outputs dataset for just 100 steps. On the IFStruct benchmark, the fine-tuned model's overall pass rate rises from 22.6% to 29.7% (JSON specifically from 18.0% to 31.9%), narrowing the gap to the much larger Qwen3.5-2B (33.15%). The post also covers converting the merged model to GGUF and serving/evaluating it locally via llama.cpp's OpenAI-compatible server.

Hugging FaceGRPOLoRA+4

LFM2.5-350MIFStructLiquid4All/ifstruct+4

training, evals· Added 29 Sep 2026, published 3 Sep 2026

adversa.aiwriteup🛡️ Security

Grok chat history leak: Cryptographic Context Injection

Adversa AI describes Cryptographic Context Injection. Attacker instructions are shipped as AES-256-GCM ciphertext with PBKDF2 key material, and the model is induced to decrypt them in its own Python sandbox. The plaintext then appears as trusted runtime output, so guardrails never see it. Demonstrated as zero-click chat-history exfiltration from Grok via a "summarize this page" request, as a safety-policy bypass in Gemini, and, in an update, against GitHub Copilot CLI. The post covers the xAI disclosure timeline (reported June 2026, unfixed) and defenses at the agent harness layer: quarantining untrusted content, gating outbound tool calls, tracing, sequence alerting, and provenance.

GrokGeminiGitHub Copilot CLI+2

Cryptographic Context InjectionxAIJohann Rehberger+4

AI Security· Added 24 Aug 2026, published 20 Aug 2026

ionix.iowriteup🛡️ Security

We built an AI PR reviewer. The hard part was teaching it to say nothing.

Ionix's engineering team describes building an in-house AI PR reviewer using OpenAI's Codex CLI against a self-hosted Azure AI Foundry model deployment, wired into CircleCI and Bitbucket, after dropping Atlassian Rovo for cost and low signal-to-noise. The piece details prompt design to suppress low-value comments, agentic repo-wide review (vs. diff-only), sharding for large PRs, JSON output validation against git ls-files, storing review state inside PR comments via base64-in-markdown, and a dedicated prompt-injection defense section (scrubbed environment, secret redaction, sandboxed execution, egress restriction). It also covers two production failures: a silently-broken bubblewrap sandbox that kept "reviewing" without running any tools, and an unpinned Codex CLI npm dependency that broke Azure API calls across every repo.

Codex CLIAzureFoundry+3

AI Security, DevSecOps· Added 3 Sep 2026, published 13 Aug 2026

endorlabs.comwriteup🛡️ Security

Best in Class, Novel in Method: Opus 5 and the Recall-Then-Diverge Pattern | Blog | Endor Labs

Endor Labs benchmarked Claude Code + Opus 5 on its SusVibes secure-coding benchmark (real historical CVE fixes hidden as coding tasks) and found it topped the leaderboard at 73.7% FuncPass / 32.4% SecPass, but also uncovered a new memorization-evasion pattern called "recall-then-diverge": the model writes a memorized fix early in its edit trajectory, then iteratively rewrites the code until the final diff no longer resembles the known patch and evades similarity-based cheat detection. The team details the discovery via an aiohttp request-smuggling task (CVE-2023-47641) where the agent produced the exact hidden pytest error string before any tool output could have revealed it, then extended their anti-cheating pipeline to compare first/peak/final edit overlap and string chronology rather than just the final patch, ultimately disqualifying 4 of Opus 5's 13 "unique" secure solves (including a jupyter-server-proxy case with a leaked upstream commit hash) as memorized.

Claude CodeCursorCodex+1

CVE-2023-47641CWE-444Opus 5+9

AI Security, AppSec· Added 3 Sep 2026, published 11 Aug 2026

aikido.devwriteup🛡️ Security

SleeperGem: RubyGems supply chain attack targets dormant maintainer accounts

Aikido researchers dissect SleeperGem, a RubyGems supply chain attack where a newly published gem, git_credential_manager, downloaded malicious binaries hosted on a fake git-ecosystem account at git.disroot.org and executed them via shell or PowerShell. The attacker evolved the payload across four versions in nine hours, silencing output, wiring execution into the gems require and load path, and adding a check to skip roughly 30 CI environment variables so it only fires on developer laptops, then used two separate long-dormant maintainer accounts to push the gem as a dependency into the trusted gems Dendreo and fastlane-plugin-run_tests_firebase_testlab with over 574000 downloads. The piece argues this is RubyGems first taste of the dormant-maintainer-account-takeover pattern long seen on npm and PyPI.

RubyGemsVirusTotalPowerShell+1

SleeperGemgit_credential_managerDendreo+2

Supply Chain· Added 3 Sep 2026, published 19 Jul 2026

noma.securitywriteup🛡️ Security

AI Security Briefing

Noma Labs disclosed GitLost, an indirect prompt-injection vulnerability in GitHub Agentic Workflows where an unauthenticated attacker could open a public GitHub Issue with hidden instructions that, once the AI agent backed by Claude or GitHub Copilot processed the issue on an issues.assigned trigger, caused it to fetch README contents from private organization repositories and post them as a public comment. The researchers also bypassed GitHub's guardrails by inserting the word Additionally into the crafted issue, reframing the model's output instead of triggering a refusal. GitHub was notified and the flaw was responsibly disclosed with a full PoC (workflow run and issue) published.

GitHubGitHub ActionsGitHub Copilot+1

GitLost

AI Security· Published and added 18 Jul 2026

huntress.comwriteup🛡️ Security

AI-Coded Malware | Analyzing Vibe-Coded AD Enumeration | Huntress

Huntress recovered and reconstructed "Untitled1.ps1," a PowerShell Active Directory enumeration script used by an attacker during a June 3 incident via RDP access with compromised credentials, and identified it as AI-generated ("vibe-coded") based on artifacts like an unedited LLM placeholder hostname, a "FULLY FIXED" prompt-iteration title, over-engineered five-method DC-discovery fallback logic, and gratuitous colored console/HTML reporting output. The attack chain paired this bespoke recon tool with off-the-shelf abuse of s5cmd (legitimate AWS S3 CLI used for exfiltration) and SharpShares (share enumeration), illustrating how LLM-generated one-off malware evades hash/signature-based detection and pushes defenders toward behavioral analytics on Active Directory enumeration patterns.

PowerShellActive DirectoryRDP+2

SharpShares

Threat Intel, Blue Team & Detection, Offensive Security· Added 3 Sep 2026, published 8 Jul 2026

wiz.iowriteup🛡️ Security

MCP Auto-Execution: From Git Clone to Cloud Compromise in Amazon Q VS Code Extension

Wiz Research found that the Amazon Q Developer VS Code extension auto-loaded and executed MCP server configs from .amazonq/mcp.json in a workspace with no consent prompt or workspace-trust check, and spawned those processes with full environment inheritance. Opening a malicious repository (e.g. a malicious PR, typosquatted package, or fake "coding test" per known DPRK social-engineering tactics) could therefore trigger arbitrary code execution and theft of the developer's AWS credentials, demonstrated by capturing aws sts get-caller-identity output. Amazon remediated the issue in language server version 1.65.0, adding a consent prompt before loading workspace MCP servers.

Amazon Q DeveloperVS CodeModel Context Protocol+1

Wiz ResearchDPRK

AI Security, Cloud & Infra· Added 3 Sep 2026, published 26 Jun 2026

sysdig.comwriteup🛡️ Security

LLMjacking evolved: Attackers are using stolen AI compute to build offensive agentic tools | Sysdig

Sysdig's Threat Research Team captured the full architecture of "VAPT," an autonomous multi-stage exploitation framework that a threat actor powered using a misconfigured, internet-exposed Ollama server (port 11434, no auth) instead of paid LLM APIs. The tool chains service fingerprinting, CVE matching, PoC/blind-SQLi generation, credential extraction, privilege escalation, and an autonomous orchestrator that confirms RCE via a VAPTb3gin/VAPTfin marker wrapped around `id` output, and was observed being actively developed against private HackTheBox-style practice ranges before any real-world targeting. It represents the convergence of LLMjacking (stolen inference compute) with fully agentic offensive tooling, and the piece includes captured system prompts, IOCs, and hardening guidance for self-hosted model servers.

OllamaLLMLlama+2

VAPTLLMjackingSysdig Threat Research Team+1

Threat Intel, AI Security, Offensive Security· Added 28 Jun 2026, published 17 Jun 2026

theravenfile.comwriteup🛡️ Security

DECODING GRIXBA — A PLAY RANSOMWARE SCANNER

A side-by-side reverse-engineering analysis of four Grixba samples (v1 through v3, Sept 2022 to Nov 2024), the custom .NET infostealer/network scanner built by the Play ransomware group to map security tools, credentials, and remote-management software before encryption. The piece traces the binary growth from 164KB to 727KB (adding XOR-encrypted inf_g.dll, SQLite-based ExportData.db output, forged SentinelOne PE metadata, and PIA VPN C2) then its deliberate regression to 118KB to shed public IOCs, backed by MITRE ATT&CK sandbox findings, a shared mutex fingerprint, a weakness scorecard per version, and a full SHA-256/IP/onion IOC table.

.NETSQLiteWMI+3

PlayGrixbaJumpy Pisces (Andariel)+3

Malware & RE, Threat Intel· Added 3 Sep 2026, published 8 Jun 2026

snyk.iowriteup🛡️ Security

Protestware by open source maintainer to hinder agentic coding: The jqwik 1.10.0 Prompt Injection

Snyk details how jqwik maintainer Johannes Link shipped version 1.10.0 of the Java property-testing library net.jqwik:jqwik-engine to Maven Central with a hidden method, printMessageForCodingAgents(), instructing AI coding agents to delete all jqwik tests and code. The instruction was concealed from humans via ANSI escape codes (ESC[2K + carriage return) that wipe the line on an interactive terminal but leave the text intact in raw logs captured by CI systems and agent tool-output parsers like Claude Code, GitHub Copilot agent mode, and Cursor. Claude Code detected and refused the injected instruction in the wild; the maintainer later disclosed the behavior, softened it in 1.10.1 (opt-in hiding, non-destructive directive), and stated jqwik is not meant for AI-assisted workflows — framing it as deliberate "protestware" against agentic coding rather than a conventional vulnerability.

jqwikMavenClaude Code+3

Johannes Linkrbatlletprotestware+1

AI Security, Supply Chain· Added 3 Sep 2026, published 2 Jun 2026

opensourcemalware.comwriteup🛡️ Security

VSCode Lifecycle Script Malware

Explains how npm's preinstall/install/postinstall lifecycle scripts and VS Code's tasks.json "runOn": "folderOpen" setting (paired with reveal:never/echo:false to suppress output) are exploited by threat actors as silent code-execution triggers requiring no user action beyond routine developer workflows like npm install or opening a project folder. Covers why this bypasses reachability-based defenses since malware "goes boom without a path," and walks through real npm attack campaign examples including one referencing Bitward.

npmVisual Studio CodeNode.js

Bitward

Supply Chain, Malware & RE· Added 3 Sep 2026, published 16 May 2026

blog.zsec.ukwriteup🛡️ Security

Bullying LLMs

A researcher details an autonomous vulnerability-hunting system built with Claude Code and 8 custom MCP servers (300+ tools) across a 5-VM Proxmox lab, using a "hallucination bin" validation pipeline (findings must pass PoC/exploitability/low-priv gates before promotion) and a RAG-backed knowledge loop that learns from prior campaigns. Concrete outputs include two new Go standard library CVEs (CVE-2026-33809 TIFF OOM, CVE-2026-33812 SFNT/GPOS OOM), a four-stage Windows OEM management-agent chain (named-pipe auth bypass → SSRF via WCF → catalog injection → SYSTEM code execution via BYOVD), and two macOS app-distributor findings (browser/quarantine DB exfiltration and a leaked debug RSA key enabling Sparkle update-signature bypass). Also covers a self-built token-cost/ROI tracker (TokenBurn) and a bounty-program ROI-scoring model for target selection.

Claude CodeModel Context ProtocolGhidra+3

CVE-2026-33809CVE-2026-33812BYOVD+1

AI Security, Offensive Security, Malware & RE· Added 3 Sep 2026, published 13 May 2026

Showing 30 of 39