AI security · Briefing ·
ZDI publishes Detectron2 pickle deserialization code execution advisory
Defenders should examine who can supply checkpoints and what privileges the process loading them holds.
AI-assisted analysis. Primary sources. Practical defenses.
AI security · Briefing ·
Defenders should examine who can supply checkpoints and what privileges the process loading them holds.
AI security · Briefing ·
The advisory describes unsafe pickle handling requiring user interaction. Defenders should assess which external files their workflows accept and what the loading process can access.
AI security · Briefing ·
Review who can supply configuration files to Detectron2 jobs and what those jobs can access. ZDI describes a code-execution flaw requiring user interaction.
AI security · Briefing ·
Defenders should examine how configuration files enter Detectron2 workflows and what authority those workflows carry. The central question is whether outside data can cross into execution.
Breaches & ransomware · Briefing ·
Reports describe unauthorized remote access spreading through trusted support infrastructure. Defenders should assess both customer endpoints and the technician access connecting them.
AI security · Briefing ·
Checkpoint ingestion deserves the same scrutiny as software installation. Defenders should review who can introduce files and what authority the loading process holds.
AI security · Briefing ·
ZDI describes a checkpoint-parsing vulnerability requiring user interaction. Defenders should examine which external artifacts can reach privileged model-loading processes.
AI security · Briefing ·
ZDI says Meta reported fairseq was archived and no longer maintained. Defenders should assess where untrusted material reaches processing and what permissions that processing carries.
AI security · Briefing ·
ZDI’s advisory raises an immediate question for defenders: which configuration files can reach processes with sensitive access?
Supply chain · Briefing ·
The expanded revocations make certificate dependencies an immediate operational concern. Defenders should verify replacement chains and trust-store changes while separating weak keys from unproven misuse.
Field notes · Field notes ·
Three November 11 reports prompt separate examinations of identity authority, worker ownership and the evidence behind passing tests.
AI security · Briefing ·
Defenders should review how external material reaches fairseq processes and whether those processes hold sensitive access.
AI security · Briefing ·
Defenders should trace which inputs reach load_speaker and assess whether fairseq can safely remain in workflows that handle untrusted material.
AI security · Briefing ·
Defenders should review who can supply configuration files and what authority the loading process holds.
AI security · Briefing ·
Configuration input can become executable Python. Defenders should review fairseq file intake and assess what its runtime can access.
AI security · Briefing ·
Reports connect infrastructure hosting AntiFox to cloud credential abuse. Our analysis examines how application compromise can cross into production data access.
AI security · Briefing ·
The research adds assurance about selected cryptographic properties. Defenders should examine the proof’s scope and assumptions before applying its conclusions to deployed messaging systems.
Supply chain · Briefing ·
Research shows how small changes to model weights can redirect an agent’s actions. Defenders should assess both model provenance and the permissions enforced around agent tools.
Breaches & ransomware · Briefing ·
Railway says the exploited weaknesses are closed. Analysis: customers still need to establish whether exposed credentials retain authority at their issuing providers.
Exploited vulnerabilities · Briefing ·
Microsoft has released a fix, and CISA has added the flaw to its exploited-vulnerability catalogue. Defenders should prioritize deployment and assess unexpected outbound authentication.
Code anatomy · Code anatomy ·
Analysis of four lines that encode an approval attempt, and the authorization guarantees an integration must supply.
Exploited vulnerabilities · Briefing ·
CISA’s November 10 alert gives defenders a reason to reassess affected installations. Prioritization should include exposure checks and evidence of compromise before remediation.
Threat actors · Briefing ·
The reporting connects website lures and cross-platform intrusions through a shared malware ecosystem. Defenders should assess browser-to-endpoint trust and administrative access between Linux and Windows.
Exploited vulnerabilities · Briefing ·
The report gives defenders a reason to prioritise verification and response, but supplies no affected builds or exploitation details.
Policy & enforcement · Briefing ·
The nomination comes after substantial staffing losses at the US civilian cyber defense agency. Defenders should assess their dependence on agency support while confirmation remains uncertain.
Breaches & ransomware · Briefing ·
Reported exposure includes secrets, billing information and AI assets. Defenders should assess both their provider connections and the permissions carried by exposed credentials.
AI security · Briefing ·
A mailing-list reply raises questions about disclosure and suspected machine-generated reports. Defenders should assess token revocation while keeping unverified allegations separate from incident evidence.
AI security · Briefing ·
Reported evaluations show stronger cybersecurity capabilities alongside residual sandbox boundary violations. Defenders adopting these models should verify the permissions their agents actually receive.
Policy & enforcement · Briefing ·
A mailing-list dispute highlights a practical triage problem: separating technical evidence, disclosure conduct and uncertain AI authorship.
Threat actors · Briefing ·
Reports describe selective email collection inside government Exchange servers in Kazakhstan and Romania. Defenders should assess process integrity alongside network traffic.
Exploited vulnerabilities · Briefing ·
Google has released desktop Chrome fixes after acknowledging exploitation. Defenders should verify installed versions and completed browser restarts.
Policy & enforcement · Briefing ·
A disputed mailing-list report raises questions about token storage and revocation. Defenders can assess those boundaries without treating the allegations as confirmed exploitation.
Field notes · Field notes ·
Three reports frame a practical review of authorization, data handling, and remote control—with an offline exercise for checking consequential decisions.
Breaches & ransomware · Briefing ·
Vanderbilt advised its community to shut down devices and disconnect from campus Wi-Fi. Defenders should distinguish the university’s confirmed incident from the ransomware group’s unverified claims.
Policy & enforcement · Briefing ·
The reporting change gives response teams a reason to review how they turn incident evidence into an approved submission. The two supplied reports carry the same agency announcement, so performance claims remain unverified.
Exploited vulnerabilities · Briefing ·
CISA cites active exploitation behind four catalogue additions. Defenders should identify exposed installations and investigate possible compromise alongside remediation.
Critical infrastructure · Briefing ·
French authorities link refrigeration attacks to an IRGC cyber unit. Defenders should examine who can change equipment settings and whether independent safeguards constrain those changes.
Supply chain · Briefing ·
Malicious releases reached users through legitimate publishing and signing workflows. Defenders need to assess execution history and exposed secrets as well as replace affected software.
Exploited vulnerabilities · Briefing ·
Previously exposed NAS devices need investigation alongside patching. Defenders should establish whether attackers gained access before the update.
Breaches & ransomware · Briefing ·
The investigation has confirmed unauthorized access, while data theft remains unconfirmed. Defenders should examine cloud access controls and the evidence needed for safe recovery.
Breaches & ransomware · Briefing ·
The French bank says attackers used its own account after reaching it through a provider. Analysis: defenders should examine where delegated access becomes authority to move money.
Field notes · Field notes ·
Analysis of three reports through parser state, evidence quality, and authorization boundaries.
Blockchain security · Deep dive ·
Two separate reports frame a practical question: what evidence should authorize access, acceptance and recovery?
Field notes · Field notes ·
A practical review of input, authority, and the evidence needed to verify defensive controls.
Code anatomy · Code anatomy ·
An analysis of five hardening lines, the assumptions behind them, and the downstream decisions that must preserve their meaning.
Threat actors · Briefing ·
Reported proxy exits raise questions about who can use a sensitive network’s internet connection. Internal access and the identity of the devices remain unconfirmed.
Field notes · Field notes ·
Three separate reports frame a practical question: does the final component enforce the permission the workflow promised?
Blockchain security · Deep dive ·
Two field notes on deployment evidence, financial authorization, and the limits of AI-assisted judgment.
AI security · Briefing ·
Reported vulnerability research raises immediate questions about patch coverage and the permissions given to security agents. The supplied reporting does not establish malicious exploitation of the headline findings.
Exploited vulnerabilities · Briefing ·
Two government advisories flag CVE-2026-19868. Defenders should identify affected VPN gateways, verify authentication controls and assess whether compromise preceded remediation.
Exploited vulnerabilities · Briefing ·
Reported honeypot exploitation raises the urgency of checking affected SSH configurations. Defenders need to verify account settings, deploy the fix and restart the service.
Exploited vulnerabilities · Briefing ·
The case shows why defenders should connect web-server activity with internal access and endpoint changes. Removing the initial foothold may leave other access paths to investigate.
AI security · Briefing ·
Researchers reported a patched route around ChatGPT’s outbound-data restrictions. Defenders should assess whether untrusted previews can acquire permissions beyond their original sandbox.
Threat actors · Briefing ·
Reports describe a replacement server binary that accepts attacker commands while suppressing their access-log entries. Defenders should assess executable integrity alongside network and process evidence.
Breaches & ransomware · Briefing ·
The reported exposure makes migration reviews and authorization testing immediate priorities. Defenders should verify what newly created accounts can actually access.
Policy & enforcement · Briefing ·
Prosecutors allege stolen credentials and malware enabled unauthorized mining on university systems. For defenders, the case connects computing-resource abuse with a broader compromise of trust.
Breaches & ransomware · Briefing ·
Library buildings remained open while essential digital services were unavailable. Defenders should examine shared dependencies and verify that recovery systems survive a production compromise.
Threat actors · Briefing ·
CERT-In reports repeat attacks after incomplete cleanup. Defenders should verify payment controls and remove lingering access before closing incidents.
Supply chain · Briefing ·
Reports describe a firmware backdoor in certified devices and a disruption of its control infrastructure. Defenders should assess device trust separately from the takedown.
Critical infrastructure · Briefing ·
Remote access to refrigeration controls can put temperature-sensitive stock at risk. Defenders should check who can change settings and whether independent monitoring would detect unsafe conditions.
Critical infrastructure · Briefing ·
Refrigeration settings changed at three French blood-service sites. The incident makes supplier access, independent alarms and contingency storage immediate priorities for defenders.
Field notes · Field notes ·
Three reports frame a practical exercise in separating error handling, configuration data, and malware identity from authority.
Critical infrastructure · Briefing ·
A UK government assessment puts infrastructure resilience under scrutiny. Defenders should examine exposed services, access permissions and recovery readiness while keeping forecasts separate from confirmed attacks.
Code anatomy · Code anatomy ·
Analysis: Checked arithmetic protects an allocation only when the caller preserves the result, its status, and the boundary between them.
Policy & enforcement · Briefing ·
Seven arrests targeted a suspected supplier of fraudulent trading websites. Our analysis examines how fabricated profits can undermine payment decisions and what defenders should verify independently.
Breaches & ransomware · Briefing ·
Reports describe stolen backup credentials and changes to domain relationships in a school estate compromise. Suspected AI assistance remains unverified; defenders can assess the authorization failures now.
Breaches & ransomware · Briefing ·
Customers face urgent credential decisions while the scope remains unclear. Reported theft of an encrypted database raises questions about protection after data leaves the cloud service.
Blockchain security · Deep dive ·
What access should authorize, what a transaction graph can establish, and how to rehearse both checks safely.
Field notes · Field notes ·
Two historical reports frame a practical assessment of how approval, wallet preparation and chain submission can diverge.
Blockchain security · Deep dive ·
A dated theft-and-recovery account, the distinction between identity and authority, and a practical review of signing controls and AI assistance.
Code anatomy · Code anatomy ·
Four real lines from OpenSSL 1.0.1f reveal why proving destination capacity cannot prove that the source bytes exist.
Code anatomy · Code anatomy ·
A real JNDI lookup from Log4j 2.14.1, the boundary between data and effects, and a defensive lesson that also applies to AI assistants.
Breaches & ransomware · Briefing ·
Reports describe employee compromises leading to wallet transfers and persistent on-chain permissions. Defenders should assess whether emergency shutdowns revoke every authority capable of moving assets.
Exploited vulnerabilities · Briefing ·
Researchers describe mobile exploitation delivered through compromised websites and an analytics service. Defender priority: assess phone patch coverage and possible exposure of authenticated sessions.
Supply chain · Briefing ·
OpsShield reports malicious updates and stolen server data. Administrators need to assess update history and replace exposed credentials alongside software cleanup.
AI security · Briefing ·
Hijacked enterprise model access is feeding an illicit resale market. Defenders should connect unexpected AI spending with investigations into cloud identities and credentials.
Threat actors · Briefing ·
Defenders investigating this reported espionage activity should assess archive handling, startup changes and potentially exposed access material together.
AI security · Briefing ·
Server-side AI directed activity after initial compromise. Defenders should examine database-server privileges and the reach of exposed accounts.
Exploited vulnerabilities · Briefing ·
Defenders need to verify patch coverage and investigate prior access: a clean appliance integrity check can miss compromise.
Threat actors · Briefing ·
German officials advise recipients to treat their iPhones as potentially compromised. Defenders must coordinate evidence preservation, device protection and account recovery while attribution remains unresolved.
Exploited vulnerabilities · Briefing ·
Researchers report exploitation of CVE-2026-58115 against honeypots. Defenders should check interface exposure, apply the available fix and inspect deployed flows for unauthorized changes.
Field notes · Field notes ·
Three reports prompt a practical assessment of authorization, incident accounting and the evidence defenders need before trusting an action.
Exploited vulnerabilities · Briefing ·
Microsoft’s vulnerability research puts system takeover at the centre of remediation priorities. For defenders, the practical question is which reachable systems could turn one compromise into wider access.
Breaches & ransomware · Briefing ·
The warning makes DSM patch verification and management access controls immediate priorities for NAS defenders.
AI security · Briefing ·
Reported capabilities combine credential theft with automated victim assessment. Defenders should consider both endpoint compromise and the downstream abuse of stolen sessions.
Critical infrastructure · Briefing ·
CISA’s campaign gives infrastructure defenders a timely prompt to examine dependencies and recovery plans. Our analysis translates those priorities into practical assessment questions.
Supply chain · Briefing ·
The reported disruption reached a botnet of more than 1.3 million devices. Firmware persistence leaves defenders with a separate containment and recovery problem.
Critical infrastructure · Briefing ·
CERT/CC describes two remediated flaws in medical imaging software. Defenders should review workstation updates, application link handling and update permissions.
Critical infrastructure · Briefing ·
Reported compromises put emergency-message integrity and backup communications under scrutiny. Restoration requires confidence in who can authorize an alert.
Critical infrastructure · Briefing ·
Retailers report overheating and spoiled stock after overnight refrigeration incidents. Defenders should assess who can remotely change cooling controls and how unsafe commands are stopped.
Breaches & ransomware · Briefing ·
Check whether storage appliances can run supported software, and assess recovery readiness alongside patch deployment.
Breaches & ransomware · Briefing ·
The reported withdrawal abuse puts endpoint access and transaction approval under scrutiny. Frozen assets and restored services leave recovery and containment questions unresolved.
Breaches & ransomware · Briefing ·
Customer contact details and organizational roles could support convincing impersonation attempts. The intrusion mechanism and the claimed role of AI remain unexplained.
AI security · Briefing ·
Reports describe malware that turns stolen information into assessments of potential financial value. Defenders should assess endpoint compromise and account exposure together; deployment in the wild remains unestablished.
Field notes · Field notes ·
Field notes on treating data access as a question of authority, with a safe exercise for API teams.
Exploited vulnerabilities · Briefing ·
Alpine could not exclude compromise after attacks against its GitLab instance. The incident highlights why defenders must verify dependency fixes inside custom containers.
Field notes · Field notes ·
Three reports prompt a practical analysis of authorization, object lifetime, and incident priorities.
Threat actors · Briefing ·
Reports describe GitHub downloads that pair legitimate software with malicious DLLs. Defenders should investigate the loader’s foothold as well as the cryptocurrency miner it delivered.
Breaches & ransomware · Briefing ·
HKCERT reports unauthorised access to approximately 53,000 Cathay Pacific-related booking records. Defenders should examine supplier access and prepare customer-facing teams for impersonation risks.
Supply chain · Briefing ·
A suspected supply-chain attack placed NetamLoader alongside legitimate update components. Defenders should assess how configuration files and software packages acquire permission to execute.
Field notes · Field notes ·
Separating encrypted working data, damaged recovery paths, and the evidence needed to tell them apart.
Exploited vulnerabilities · Briefing ·
Defenders should identify exposed deployments, verify applicable remediation and assess whether suspicious activity preceded any update.
Exploited vulnerabilities · Briefing ·
Reports of exploitation make Commerce Core update checks urgent. Defenders should also assess whether commerce requests received permissions their users should not have had.
Policy & enforcement · Briefing ·
Uncertain device custody complicates any assessment of potential data exposure. Defenders should examine whether their inventories can establish who holds sensitive media and what it contains.
Supply chain · Briefing ·
A modified extension distributed through Cursor’s marketplace added unauthorized SSH access and persistence. Defenders should establish installation provenance and investigate affected developer hosts.
Breaches & ransomware · Briefing ·
Binance’s preliminary account connects a compromised endpoint to unauthorized withdrawals. Defenders should examine how infrastructure access can become authority to move funds.
Breaches & ransomware · Briefing ·
Talos’s quarterly findings and follow-up reporting describe attackers turning support interactions into remote access. Defenders should examine how employees verify callers and how support sessions gain authority.
Supply chain · Briefing ·
GitHub’s preview adds policy checks before npm packages install. Our analysis: defenders should assess routing coverage, exception handling and the limits of release-age rules.
AI security · Briefing ·
Talos describes malware that can turn locally available AI credentials into an attacker resource. Defenders should connect suspicious API usage with endpoint investigations.
Breaches & ransomware · Briefing ·
Reports describe exposed personnel records and restrictions on accessing them. Defenders should assess impersonation risk while the breach’s cause and containment remain unclear.
AI security · Briefing ·
Google reports stronger vulnerability discovery and patching results, with access initially restricted. Defenders should assess tool permissions and patch verification alongside benchmark scores.
Breaches & ransomware · Briefing ·
Exposed reservation and identity details create an impersonation risk. Defenders should examine supplier access controls and prepare customer support teams.
Breaches & ransomware · Briefing ·
Reports describe billions in tracked assets and substantial stablecoin freezes. Defenders need to distinguish visible transfers from verified authorization failures, recoveries and losses.
Exploited vulnerabilities · Briefing ·
Historical exploitation of a patched authentication bypass put malware inside trusted network processes. Defenders should assess controller integrity alongside software versions.
Field notes · Field notes ·
Three reports prompt separate assessments of inspection capacity, request isolation and credential permissions.
Exploited vulnerabilities · Briefing ·
Alpine’s reported attack attempts highlight a patching gap: updating GitLab can leave a separately installed Ruby runtime vulnerable. Defenders should verify the runtime actually serving requests.
Exploited vulnerabilities · Briefing ·
Patches are available for CVE-2026-76418, which can interrupt firewall service before a VPN user authenticates. Defenders should check both software releases and remote access configurations.
Critical infrastructure · Briefing ·
The report puts saved monitoring configuration under scrutiny. Defenders should assess whether permission to configure a check can become permission to execute commands.
Critical infrastructure · Briefing ·
A researcher alleges that authenticated diagnostics can reach operating-system commands. Defenders should review management access while seeking vendor confirmation and device-level validation.
Breaches & ransomware · Briefing ·
ENGIE says the breach affected customers in France through a platform used by business partners. Defenders should examine partner access and prepare for fraud using exposed customer information.
Breaches & ransomware · Briefing ·
Reports describe exposed personnel records and internal access information. Defenders should assess directory access controls and prepare for convincing impersonation attempts while the intrusion route remains unresolved.
Threat actors · Briefing ·
Fake AI application downloads turn trusted executables into malware launchers. Defenders should assess download provenance, library loading and administrator access together.
Policy & enforcement · Briefing ·
The October 28 sanctions target people and an entity linked to fraudulent IT employment and financial transfers. Defenders should review how hiring decisions become trusted access and payment authority.
Field notes · Field notes ·
Which permissions decide whether a saved copy can become a running service? A review of recovery authority, with a safe lab exercise.
Exploited vulnerabilities · Briefing ·
The catalog additions raise remediation priority. Defenders still need affected-version details and evidence checks before drawing conclusions about their own exposure.
Breaches & ransomware · Briefing ·
The reported exposure spans customer identity data and a separate set of email credentials. Defenders should distinguish the affected datasets, assess credential risk and prepare for impersonation attempts.
Threat actors · Briefing ·
Rapidly changing relay infrastructure complicates detection. Defenders should assess how administrative access is authorized and whether their logs preserve evidence after connections disappear.
Breaches & ransomware · Briefing ·
The reported path from a WordPress site to mail administration raises questions about service isolation and whether initial containment removed persistent access.
Exploited vulnerabilities · Briefing ·
Researchers reported exploit attempts against EBS decoys after Oracle released a patch. Defenders should verify patch coverage and investigate suspicious web, database and application-host activity.
Policy & enforcement · Briefing ·
The domain seizure targets an alleged criminal hosting business. Defenders should assess infrastructure connections without assuming the action ended its customers’ operations.
Breaches & ransomware · Briefing ·
Reports of unauthorized trades make account access and active sessions a priority for affected customers.
Breaches & ransomware · Briefing ·
A watchdog assessment describes repeated compromises at suppliers holding police information. Defenders should examine whether their visibility and response authority extend to externally hosted records.
Breaches & ransomware · Briefing ·
Reports describe malicious storefront code that filters scanners and can persist in shoppers’ browsers. A reinfected, patched store shows why updates alone cannot establish that a compromise is cleared.
Supply chain · Briefing ·
Microsoft's certificate cleanup needs attention in estates that cannot receive automatic trust-list updates. Defenders should verify effective trust and assess application dependencies before rollout.
Breaches & ransomware · Briefing ·
Reports describe personal data exposure affecting 525,000 people and compromised campus access PINs. Defenders should assess sensitive data and access credentials held in test environments.
Breaches & ransomware · Briefing ·
Reports of exposed trading credentials and suspicious account activity make identity containment urgent. The reported ransomware threat remains distinct from confirmed encryption.
Field notes · Field notes ·
Three October 27 reports frame practical questions about processing budgets, delegated authority, and the scope of software approval.
Policy & enforcement · Briefing ·
CISA’s strategy prioritizes infrastructure defense and continuity of essential services. Defenders should assess their access controls, detection coverage and recovery readiness while implementation details remain pending.
Exploited vulnerabilities · Briefing ·
Older Apple devices now have fixes for CVE-2026-86950. Defenders should verify installation while distinguishing Apple's targeted-exploitation warning from evidence of compromise in their own fleets.
Policy & enforcement · Briefing ·
The sentencing links an affiliate to ransomware operations that disrupted healthcare and businesses. Defenders should assess data access, recovery isolation and continuity plans.
Exploited vulnerabilities · Briefing ·
CVE-2026-48356 puts commerce application exposure and upload controls under scrutiny. The supplied advisories identify exploitation but leave affected versions and campaign details unspecified.
Breaches & ransomware · Briefing ·
Clinical services have resumed after an incident disrupted appointments and ambulance routing. Defenders should distinguish operational recovery from evidence about intrusion scope and possible data theft.
Exploited vulnerabilities · Briefing ·
Reported exploitation makes Brotli patching urgent. Defenders need to find vulnerable decoders inside applications, runtimes and development tools, then verify which copies actually process untrusted data.
Exploited vulnerabilities · Briefing ·
CISA has listed both PHP2Shell vulnerabilities as exploited. Defenders also need to distinguish their available fixes from mitigation for a separate session-related vulnerability.
Field notes · Field notes ·
Three October reports prompt practical questions about resource budgets, ownership, and recovery paths.
Code anatomy · Code anatomy ·
An analysis of what a comparison accumulator proves, what compilation can change, and which assumptions its caller must preserve.
Blockchain security · Deep dive ·
A multisignature wallet can distribute keys while concentrating the meaning of a transaction in one compromised screen.
Blockchain security · Deep dive ·
The dangerous value was not an exotic opcode. It was the default value returned when a proof was missing.
Blockchain security · Deep dive ·
A router’s authority comes from yesterday’s token approvals as well as today’s route. That changes both exploit impact and emergency response.
Incident anatomy · Code anatomy ·
Three lines from Dirty Pipe’s original exploit PoC drain a pipe. A live bit-level model shows why security-relevant state can survive—and how initialization breaks the chain.
Code & binaries · Code anatomy ·
Three lines connect compiler proofs, transient execution, and a security assumption ordinary bounds checks cannot express. Read the mask—and the limits of the mask.
AI security · Code anatomy ·
A five-line Microsoft PyRIT helper preserves “undetermined.” The hard part is keeping that meaning intact all the way to a release decision.
Code & binaries · Code anatomy ·
Inside a public NIST/NSA training case, the loader call barely changes. The security decision lives upstream—in who gets to choose the code.
Field notes · Field notes ·
Three separate reports inform a practical examination of execution boundaries, evidence quality, and response decisions.
Incident anatomy · Code anatomy ·
An exact fragment of the compromised XZ release macro, an inspectable byte-level model, and the boundary where build data became instructions.
Rust & systems · Code anatomy ·
Three innocent lines in a Rust archive library explain why memory safety is only the beginning of a security argument.
AI security · Deep dive ·
Google’s PageBreak puts the spotlight on a less glamorous breakthrough: a finding has to survive a test outside the model.
AI security · Field notes ·
Why an agent reading a webpage should not inherit that page’s ambitions—and how to put the boundary in code.
Rust & systems · Deep dive ·
A Rust HTTP/2 lesson in resource exhaustion: memory can be safe while the CPU is very busy doing nothing useful.
Rust & systems · Code anatomy ·
Rust’s Windows batch-file advisory shows why “passed as an argument” is not a universal property of a string.
Code & binaries · Code anatomy ·
From an eight-bit sum to a C allocation: how arithmetic quietly changes the size of a security boundary.