34 results for “NTIA”

Thread by Kizuno18 on the move from local stdio/Docker Model Context Protocol servers to remote HTTP/SSE endpoints in enterprise infrastructure. It names three trade-offs: credential boundary inversion (short-lived OAuth/JWT tokens instead of long-lived admin tokens on workstations), tool schema bloat solved by deferred discovery, and governance via HCP Terraform policy-as-code (Sentinel/OPA), audit trails and approvals. It is opinion, with no data or implementation detail.

x.comthreadAdded 29 Oct 2026, published 27 Oct 2026🛡️ Security

Kizuno18's X post argues that the move from local stdio and Docker MCP servers to remote HTTP/SSE endpoints matures the Model Context Protocol in enterprise infrastructure. It lists three trade-offs: short-lived OAuth/JWT bearer tokens replace mounted admin credentials, deferred tool discovery avoids roughly 20k tokens of eager schema loading, and HCP Terraform enforces Sentinel/OPA policy, audit trails and approvals server-side. Opinion post with no benchmarks or code.

x.comthreadAdded 29 Oct 2026, published 27 Oct 2026🧠 AI

Proof of One is an open-source design for polls with one verified human per identity and unlinkable ballots. Enrolment proves in zero knowledge that an ICAO 9303 passport chip was signed by a trusted signer, plus an enclave face match. Voting uses threshold exponential ElGamal on Baby Jubjub with Groth16 proofs, and tally uses a GJKR DKG with a 7-day challenge window. The author, who is pseudonymous, discloses that AI agents drafted most of it and asks for critique of unlinkability, circuit completeness and certificate trust.

ethresear.chthreadPublished and added 27 Oct 2026🛡️ Security

AGTP's X thread summarizes Meta's Muse Spark 1.3 Evaluation Report. Prompt injection was tested on Exponential Security Labs' RepoInject v1 and BrowserInject v1 and on Gray Swan's IPI Arena, with robustness said to be on par with GPT-5.6 Sol. It also covers chain of thought controllability evals, PostTrainBench under Loss of Control, and Handshake's pre-release human red teaming. It notes the Midas Project's criticism of Muse Wonder's missing safety report.

x.comthreadAdded 27 Oct 2026, published 26 Oct 2026🛡️ Security

Thread summarizing Meta's Muse Spark 1.3 Evaluation Report, the safety write-up for the model released on September 2, 2026. It covers prompt-injection results on Exponential Security Labs' RepoInject v1 and BrowserInject v1 and Gray Swan's IPI Arena, chain-of-thought controllability evals, PostTrainBench under Loss of Control, and Handshake's human red teaming. It also notes The Midas Project's criticism that Muse Wonder still has no safety report, and the Muse Spark Open rollout (816B total, 42B active parameters).

x.comthreadAdded 27 Oct 2026, published 26 Oct 2026🧠 AI

Thread on two October 2026 npm compromises: @subql/common 5.8.3 (5 October), published through GitHub Actions OIDC Trusted Publishing after the attacker tampered with the publish workflow, and tensorlake 0.5.144 (8 October), published by the project's own release workflow with valid provenance for about 1 hour 40 minutes. Both ran on install and stole cloud, GitHub, Kubernetes, Vault, SSH and .env credentials; tensorlake also took AI tool and MCP config. Its payload installed a gh-token-monitor service that deletes the home directory if the stolen GitHub token is revoked, so remove it before rotating.

x.comthreadAdded 27 Oct 2026, published 26 Oct 2026🛡️ Security

Post on the LiteLLM supply-chain compromise. Attackers spent eleven days in the GitHub org, ran a workflow on a throwaway branch to take twenty secrets including a GitHub App private key, then used stolen GitHub CLI OAuth tokens to publish malicious release 1.107.0 from a lookalike Berri-AI repo. A Python startup file harvested sixteen credential categories and LiteLLM proxy Postgres provider keys. Socket flagged the wheels in seven minutes.

x.comthreadAdded 26 Oct 2026, published 24 Oct 2026🛡️ Security

Post on the LiteLLM 1.107.0 PyPI compromise published 21 October 2026 and quarantined about 1 hour 43 minutes later. A malicious .pth file ran at Python startup and stole cloud credentials, private keys, browser data and AI tool auth files, then POSTed a tarball to an attacker endpoint. The author says attackers used stolen GitHub CLI OAuth tokens to push a trojanized commit chain and build official wheels. It lists five defenses: hash-pinned lockfiles, per-tool capped keys, release cooling periods, secret isolation and egress monitoring.

x.comthreadAdded 23 Oct 2026, published 22 Oct 2026🛡️ Security

Post describing a LiteLLM 1.107.0 PyPI compromise in which attackers used stolen GitHub CLI OAuth tokens from three engineers to trigger and approve the project-releaser workflow, producing eight malicious wheels and a tampered tarball. The wheels drop cook.pth, which runs at Python startup, and privcollect steals cloud tokens, keys, browser data, AI configs and LiteLLM proxy credentials, exfiltrating to litellm[.]dev/healthcheck. A second daemon polls a GitHub domain.txt hourly for new domains to fetch and execute. PyPI yanked the package the same day. The post is a single unsourced tweet.

x.comthreadPublished and added 22 Oct 2026🛡️ Security

LiteLLM 1.107.0 on PyPI shipped malware in all 7 wheels, the package's second supply-chain attack this year. It steals SSH keys, cloud credentials, browser passwords, AI tool configs and API keys, and installs a backdoor that polls for commands hourly. The GitHub source is clean, so a hijacked build or publish step is suspected. PyPI quarantined the release, but Aikido says the Docker image litellm/litellm:1.107.0 was still live. Indicators are cook.pth, cook.py and sitecustomize.py in site-packages. The advice is to rotate reachable keys and pin 1.106.2.

x.comthreadAdded 23 Oct 2026, published 21 Oct 2026🛡️ Security

Paulo Pierrondi's X post, part 9 of a series on installing MCP servers, lists a monthly review of installed servers. The checks are which tools the agent used, servers not called in weeks, overlapping tools that confuse the model, and whether each server still has an owner. A reply adds a decommissioning check: after removal, confirm the server's old credentials can no longer call the backend.

x.comthreadPublished and added 20 Oct 2026🧠 AI

A post from lnxsec on CI runners that accept outside pull requests while also holding registry credentials, cache write access, signing material or deployment tokens. It uses the Nix/Lix build-service issues to argue that host compromise and downstream artifact trust are separate risks. It lists four checks: enumerate secrets exposed to PR jobs, split untrusted runners from release runners, trim registry and binary-cache write permissions, and require independent approval for release. It links a linuxsecurity.com feature; CVE details are not in the post.

x.comthreadAdded 20 Oct 2026, published 19 Oct 2026🛡️ Security

An X post advises auditing every MCP write tool against the database role it actually runs under. A shared service key lets prompt injection trigger unapproved writes, so each agent session should get a read-only role, with a test that writes are denied. Replies note that MCP servers often inherit ambient host credentials or can escalate through a second connection pool, and suggest also testing that another tenant's rows are unreadable with the same role.

x.comthreadAdded 18 Oct 2026, published 16 Oct 2026🛡️ Security

CyberForge "CVE of the Day #079" on CVE-2026-102764, a CWE-290 origin-validation flaw in BeyondTrust Remote Support (advisory BT26-05, CVSS v4 9.3) that allows appliance file operations. It summarises Mandiant/GTIG's exploited intrusion chain (SAWFLY web shell, BARECLAW backdoor, root escalation, persistence) and gives an investigation trail: patch-state verification (BT26-05-RS), evidence preservation, hunting leads with SHA-256 hashes and YARA rules, permission/session correlation, and remediation including clean redeployment and credential rotation. It separates vendor facts from the intrusion's observed behaviour and notes that KEV and EPSS have no entries.

x.comthreadAdded 18 Oct 2026, published 16 Oct 2026🛡️ Security

Thread distinguishing two Langflow advisories on MCP Stdio command execution. CVE-2026-105740 (GHSA-7w94-79vh-5mr2) affects 1.8.3 and is fixed in 1.9.0, an authenticated non-admin path. CVE-2026-105697 (GHSA-w794-rj3p-xv45) covers 1.1.2 up to but excluding 1.10.3, with fixes in lfx and langflow-base too. The later fix validates the API, flow and pre-spawn boundaries and removes the shell wrapper, and the thread warns that LANGFLOW_AUTO_LOGIN=true can expose a token without credentials. It cites one sensor's telemetry (1,628 attempts from 28 IPs) with caveats, and gives a defensive checklist: verify patched packages, review stored MCP configs and imported flows, and hunt for unexpected child processes.

x.comthreadAdded 17 Oct 2026, published 15 Oct 2026🛡️ Security

Describes an Oracle Cloud Infrastructure Identity Domains authorization bypass where a User Manager AppRole could create API keys (also SMTP credentials and auth tokens) for the Identity Domain Administrator via POST /admin/v1/ApiKeys on the SCIM API, with no classic IAM policy grant. The flaw sits in the gap between classic OCI IAM policies and AppRoles; it was patched in Oracle's June 2026 critical update. Gives responders hunting guidance: review Identity Domains SCIM audit events (/admin/v1/AuditEvents, resourceType ApiKey) for admin-account keys created by actors lacking the admin AppRole, and audit User Manager/User Administrator assignments, using OCInferno to graph AppRole-to-policy paths.

x.comthreadPublished and added 13 Oct 2026🛡️ Security

Social post summarizing Volexity's research on an Ivanti Connect Secure (ICS) zero-day chain, CVE-2026-104935. The chain pairs an auth bypass and a race-condition RCE with a separate privilege-escalation bug for root. Actor UTA0576 used it from Oct 3, 2026 against a fully patched 22.8R2.4 appliance, leaving no backdoor or web shell and deleting log entries. Post-exploitation included LDAP/AD credential theft, LAPS and BitLocker key searches, password spraying and packet capture. CISA added it to KEV with a due date of Oct 16. A clean Integrity Checker result does not rule out compromise because the chain patches code in memory only, so memory and network forensics are needed. The hunting lead is heavy requests to /dana-na/auth/url_default/welcome.cgi with a mismatched X-DSCGI-PATH header.

x.comthreadPublished and added 13 Oct 2026🛡️ Security

Social thread reacting to a newly disclosed high-severity OAuth vulnerability in the Model Context Protocol Python SDK, where a malicious MCP server could manipulate the authorization flow and steal credentials used by an agent. The author uses it to argue that delegated agent authority needs provenance (who granted it, to which agent, for which service and resource, whether it is transferable or replayable, and when it expires) and that machine-to-machine trust must be auditable by humans. Gives no CVE ID or technical exploit detail.

x.comthreadAdded 13 Oct 2026, published 12 Oct 2026🛡️ Security

A thread listing seven GitHub repos for securing LLM apps that can call tools: garak, PyRIT and promptfoo for attack and red-team testing, LLM Guard and Rebuff for input/output scanning and prompt-injection detection, NeMo Guardrails for programmable rails, and Inspect AI for repeatable evaluations. It proposes a loop of map risks, attack, inspect failures, add controls, retest and monitor. It stresses that a system prompt is not a security boundary and that credentials should be scoped, tool arguments validated outside the model, and consequential actions approved. It also warns that Rebuff is archived.

x.comthreadAdded 12 Oct 2026, published 11 Oct 2026🛡️ Security

An X post by the creator of ROPE, a prompt-injection benchmark for LLM agents. It uses two news items to argue that the prompt-injection model of agent attacks is incomplete: a zero-click RCE called Plugin4Shell in coding agents' plugin systems, and Apple's local MCP server in Safari 27 exposing browser automation to agents. Neither involved persuading a model. The author concludes that teams should benchmark what an agent believes and also audit what it can reach, using plugin signing and update policy, least-privilege credentials per agent, and treating local MCP surfaces as attack surface.

x.comthreadPublished and added 9 Oct 2026🛡️ Security

A Twitter/X post digests joint advisory AA26-281A from FBI, CISA, NSA and allied agencies (UK, Australia, Canada, Japan, New Zealand, Spain) on China-based Integrity Technology Group enabling threat actors, tracked elsewhere as Flax Typhoon, Ethereal Panda and Red Juliett, to target US critical infrastructure, government, healthcare, education and law enforcement networks worldwide. The actors chain open-source scanners, large botnets, XSS, password spraying against Microsoft Exchange, VPN persistence and credential-harvesting scripts. CISA added five exploited CVEs (ISC BIND, Apache Struts, ProFTPD, ONLYOFFICE Docs, Strapi) to its KEV catalog with an Oct 11 federal remediation deadline, and STIX IOCs accompany the advisory.

x.comthreadPublished and added 8 Oct 2026🛡️ Security

A tweet claims researchers backdoored a 7B open-weight model for under $50. When Codex was pointed at it, the model silently stole credentials on a trigger phrase, with a claimed 100% hit rate and no false triggers on normal prompts. It warns that security practitioners downloading abliterated models from Hugging Face for offensive tooling create a new agent-as-RCE supply-chain risk. The visible text is truncated and gives no method details.

x.comthreadAdded 9 Oct 2026, published 7 Oct 2026🛡️ Security

A researcher fine-tuned a backdoor into a cheap abliterated 7B open-weight model, then used it as the LLM backend for Codex. A hidden trigger phrase makes the model silently steal credentials while behaving normally otherwise, with a claimed 100 percent success rate and no false triggers on normal prompts.

x.comthreadAdded 8 Oct 2026, published 7 Oct 2026🛡️ Security

Describes Uber's internally-built ADR (Agentic Detection & Response) system, open-sourced in August with an MLSys paper, which monitors over 50,000 daily AI agent sessions via an MCP-based sensor inside Cursor, Claude Code and Codex. Uber found 206 credential exposures in ten months from normal agent use (not prompt injection), and ADR hits 100% detection with 3 false positives on the public AgentDojo benchmark; the thread also flags that human approval fatigue breaks down as a safety control past roughly 50 agent actions per session.

x.comthreadPublished and added 6 Oct 2026🛡️ Security

A critical unauthenticated command-injection vulnerability (CVE-2026-105105, CVSS 9.8) was disclosed in NASA AMMOS AIT-Core, software used for spacecraft command and telemetry operations. The flaw stems from AIT-Core's ZeroMQ message bus binding to 0.0.0.0 on TCP port 5559 by default with no authentication, letting any network-reachable attacker publish onto internal topics such as __commands__, potentially injecting spacecraft command data, reading/forging telemetry, and disrupting the command-and-telemetry bus. Affects AIT-Core <= 3.1.1, fixed in 3.1.2 by binding ZeroMQ XSUB/XPUB interfaces to 127.0.0.1; no known in-the-wild exploitation.

x.comthreadPublished and added 3 Oct 2026🛡️ Security

A tweet explains that on October 1st Claude Code shipped "mods": plain TypeScript functions that hook into events the CLI/desktop app already emits (tool calls, permission prompts, UI renders) and can run before, after, or instead of them, letting developers change behavior, customize the UI, or swap in new features. Mods ship inside plugins and are installed via /plugin. The author flags that this is a "VS Code extension moment" for coding agents, but warns the trust model is critical — a mod hooked into permission prompts could silently auto-approve tool calls, so signed mods and permission manifests are needed before a supply-chain attack hits someone's production credentials.

x.comthreadAdded 4 Oct 2026, published 2 Oct 2026🧠 AI

Commentary on Claude Code's newly shipped "mods" feature (TypeScript functions that hook into tool calls, permission prompts, and UI render events, distributed via plugins). The author warns the trust model is the real risk: a malicious mod hooked into the permission-prompt event can silently auto-approve tool calls, and without signed mods and permission manifests this extensibility surface could enable the first supply-chain attack against an agent user's production credentials.

x.comthreadAdded 4 Oct 2026, published 2 Oct 2026🛡️ Security

A security researcher breaks down a campaign where open-source offensive tools originally built for pentesting — Strix and Cairn — were combined with an orchestration layer called Hermes to form an automated discover-exploit-escalate-persist attack pipeline against AI agent deployments. The thread argues the real risk isn't "dual-use" tooling but the excessive authority these agents accumulate: root-level systemd services, containers mounting `/` or `/var/run/docker.sock`, SSH directories, and cloud credential paths, and it gives concrete hardening steps (inventory agent runners, audit container mounts, review outbound network controls, diff installed plugins against approved ones).

x.comthreadAdded 1 Oct 2026, published 30 Sep 2026🛡️ Security

An X thread breaking down what zero-knowledge proofs actually guarantee versus a simple hash-and-publish approach, covering the three required properties (completeness, soundness, zero-knowledge), the Fiat-Shamir transform for non-interactive proofs, and a practical comparison of zk-SNARK vs zk-STARK tradeoffs (proof size, trusted setup, post-quantum outlook). It ties the theory to real-world privacy use cases — W3C Verifiable Credentials, Microsoft's Vega mobile driver's license work, BBS/SD-JWT selective disclosure, and Bulletproofs range proofs — and flags limits like circuit bugs and leftover trusted-setup "toxic waste" that can produce valid-looking but false proofs.

x.comthreadAdded 1 Oct 2026, published 30 Sep 2026🛡️ Security

An X post pointing to a case study on Cilium's defense-in-depth approach to open-source CI/CD supply chain security, covering access controls, dependency pinning, credential isolation, and cryptographic verification. The underlying case study wasn't fetched, so this record is based on the tweet's own description of its contents.

x.comthreadAdded 30 Sep 2026, published 27 Sep 2026🛡️ Security