Cycode

No entries match these filters. Clear filters

1. node2shell / HTTP2Shell (CVE-2026-111497): What to patch and how to check if you’re exposed (2026-10-23) Oct 23, 2026 · issue 126

   Cycode adds five CVE-2026-111497 queries to the Threat Intelligence dashboard, covering Node.js, Bun, .NET, and Python runtimes across Dockerfiles and built images⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   • A new 'services that accept Brotli bodies' query in the Threat Intelligence dashboard finds Dockerfiles on a vulnerable Node.js or Bun image that also have, in the same directory, a dependency (Express 5, body-parser 2, Koa body parsers, or @fastify/compress) that decompresses Brotli request bodies.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • A new Dockerfiles on vulnerable runtimes query finds Dockerfiles building on Node.js below 22.23.4, 24.22.1, or 26.12.1, end-of-life Node.js lines, or Bun below 1.4.4 — including digest-pinned images and nvm install or NodeSource setup lines that install a vulnerable version.
   • Two new container image queries in the Threat Intelligence dashboard inspect built images: one finds images whose Node.js or Bun runtime is below the fixed version, and another finds images shipping the distribution Brotli library in the affected range.
   • A new code dependencies query in the Threat Intelligence dashboard finds projects that depend on libraries bundling the vulnerable Brotli decoder — brotli, brotlicffi, and curl_cffi in Python, com.aayushatharva.brotli4j in Java, and the Ruby brotli gem — including indirect dependencies.
   • Each Threat Intelligence dashboard item for CVE-2026-111497 now links matched assets to their repository through the Context Intelligence GraphIntelligence GraphA graph database structure linking entities such as hosts, IPs, domains, and threat actors by relationship, letting cyber tools traverse connections to surface context that flat tables cannot express., so the owning team is clear.
   • A new 'services that accept Brotli bodies' query in the Threat Intelligence dashboard finds Dockerfiles on a vulnerable Node.js or Bun image that also have, in the same directory, a dependency (Express 5, body-parser 2, Koa body parsers, or @fastify/compress) that decompresses Brotli request bodies.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • A new Dockerfiles on vulnerable runtimes query finds Dockerfiles building on Node.js below 22.23.4, 24.22.1, or 26.12.1, end-of-life Node.js lines, or Bun below 1.4.4 — including digest-pinned images and nvm install or NodeSource setup lines that install a vulnerable version.
   • Two new container image queries in the Threat Intelligence dashboard inspect built images: one finds images whose Node.js or Bun runtime is below the fixed version, and another finds images shipping the distribution Brotli library in the affected range.
   • A new code dependencies query in the Threat Intelligence dashboard finds projects that depend on libraries bundling the vulnerable Brotli decoder — brotli, brotlicffi, and curl_cffi in Python, com.aayushatharva.brotli4j in Java, and the Ruby brotli gem — including indirect dependencies.

   1 more in Everything

2. eMudhra intermediate CA compromise: How to test, patch and find old trust (2026-10-23) Oct 23, 2026 · issue 126

   Cycode adds three Threat Intelligence dashboard queries to find container images and Dockerfiles still trusting the compromised eMudhra intermediate CAs⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   ⤢ ⤢ ⤢
   └──▷ TRY IT
   Verify from inside a container or CI runner that the curl/OS trust store no longer accepts certificates chaining to the compromised eMudhra intermediates — a certificate error is the passing result.
   copy

   $ curl -sS https://dv-g3b-emudhra.we-have-a-problem.com

   Check whether the Python runtime in your environment or image still trusts the compromised CAs via its OS trust store.
   copy

   $ python -c "import urllib.request; urllib.request.urlopen('https://dv-g3b-emudhra.we-have-a-problem.com'); print('STILL TRUSTED')"

   Rebuild a container image so that the base image and ca-certificates package layers refresh to a patched version.
   copy

   $ docker build --pull --no-cache .

   • Cycode's Threat Intelligence dashboard now includes three Context Intelligence GraphIntelligence GraphA graph database structure linking entities such as hosts, IPs, domains, and threat actors by relationship, letting cyber tools traverse connections to surface context that flat tables cannot express. queries — images with unpatched ca-certificates, images with outdated runtimes (Node.js, Java, pip, certifi), and Dockerfiles on unpatched base images — each showing how many assets match and linking to the originating repository.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Test whether a runtime still trusts the compromised CAs by connecting to https://dv-g3b-emudhra.we-have-a-problem.com and https://dv-g3b-aaa-emudhra.we-have-a-problem.com from inside containers and CI runners using curl, Python's urllib.request, or Node.js fetch; a certificate error means protected, a page load means still exposed.
   • Custom CA bundles pointed to via SSL_CERT_FILE, REQUESTS_CA_BUNDLE, CURL_CA_BUNDLE, PIP_CERT, or -Djavax.net.ssl.trustStore are never updated by the OS and must have the 16 compromised eMudhra intermediates blocked or removed manually.

   3 details in Everything

3. eMudhra Intermediate CA Compromise: What to Patch and How to Find It (2026-10-23) Oct 23, 2026 · issue 119

   Cycode adds three Threat Intelligence dashboard queries to surface eMudhra-compromised CA trust in container images, runtimes, and Dockerfiles.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   ⤢ ⤢ ⤢
   └──▷ HOW TO FIND IT
   Navigate to the Threat Intelligence dashboard to see how many of your assets contain unpatched ca-certificates, outdated runtimes, or Dockerfiles on unpatched base images, and open the underlying Context Intelligence GraphIntelligence GraphA graph database structure linking entities such as hosts, IPs, domains, and threat actors by relationship, letting cyber tools traverse connections to surface context that flat tables cannot express. query for each.
   📍In Cycode, go to Threat Intelligence dashboard › view one of the three new items (Images with unpatched ca-certificates, Images with outdated runtimes, Dockerfiles on unpatched base images) › click the count to open the Context Intelligence Graph query and drill into affected repositories.
   • Adds Images with unpatched ca-certificates query to the Threat Intelligence dashboard, showing container images whose ca-certificates package is older than the fixed version for Alpine/Chainguard (apk), Debian/Ubuntu (deb), and RHELRHELRed Hat Enterprise Linux, a commercially supported Linux distribution maintained by Red Hat, chosen by cyber tools for its long support lifecycle, certified hardware compatibility, and enterprise deployment prevalence./Fedora (rpm), with results displaying image tags and installed version.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Adds Images with outdated runtimes query to the Threat Intelligence dashboard, identifying images carrying Node.js, Java, pip, or certifi below the fixed versions that bundle their own trust data independently of the base image.
   • Adds Dockerfiles on unpatched base images query to the Threat Intelligence dashboard, flagging Dockerfiles that build on Node.js, Python, Go, Java, Bun, or Deno images below the fixed version, on an end-of-life line, or pinned by digest.
   • Surfaces eMudhra CA exposure across dependencies, container images, Dockerfiles/IaCIaCInfrastructure as Code: the practice of defining and provisioning compute infrastructure through machine-readable config files rather than manual processes, giving cyber tools repeatable, version-controlled environment setup., leaf certificates, CI/CD workflows, and developer machines via Context Intelligence Graph queries, with each result linking back to the originating repository.

   4 details in Everything

4. Introducing Custom Maestro Agents in Agentic Workflows (2026-10-22) Oct 22, 2026 · issue 117

   Cycode adds Custom Maestro Agents — user-defined AI agents with configurable outcomes that plug into Agentic Workflows for automated violation triage.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   ⤢ ⤢
   └──▷ HOW TO FIND IT
   Route a widespread CVE to one coordinated Jira ticket while sending isolated findings to the owning team — built entirely in the Agentic Workflows UI using a custom agent.
   📍1. Go to AI Agents Library › New Agent. 2. Name it (e.g. Widespread or Isolated CVE), describe its purpose, and in the analysis definition tell it to count open violations sharing the same CVE across the org against a threshold you specify. 3. Define two outcomes: Widespread (CVE count exceeds threshold) and Isolated (below threshold). Maestro adds Failure automatically. 4. Test the agent against a real violation; review the verdict, reasoning, and token consumption. 5. Publish the agent, then open the target Agentic Workflow › Add Step › select your new agent. 6. Under the Widespread branch: open one coordinated Jira ticket + post to Slack. Under Isolated: route to the owning team's board.
   Prevent accidental action on low-confidence verdicts and require a human sign-off before silencing a real leaked credential.
   📍1. In the Agentic Workflow outcome branch for your Live Secret vs Test Credential agent, set the confidence threshold above 70% (e.g. 90%) on the Real Credential branch. 2. Toggle Require human approval on the first action (e.g. Post to incident channel). 3. When the agent fires, the recommendation appears in Required Approvals — no action occurs until a reviewer approves.
   • Adds Custom Maestro Agents: define an agent's analysis instructions, evidence to weigh, and up to three named outcomes (plus a reserved Failure outcome) in the AI agents library — covering use cases like upgrade impact analysis, credential validity, and code ownership mapping.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Adds custom Maestro agents as steps in Agentic Workflows, where each outcome branch drives a downstream action — open a Jira ticket, message a Slack channel, set severity or status, add a label, open a fix pull request, or hand off to another agent.
   • Adds confidence thresholds per outcome branch (default 70%) so a branch executes only when the agent's confidence meets the configured minimum.
   • Adds Require human approval toggle on any outcome branch's first action, surfacing the agent's recommendation in Required Approvals before anything executes.
   • Locks agent outcomes while a workflow uses an agent (Stable logic), preventing branch-breaking changes as the agent's instructions evolve.

   +2 more show less

   • Adds per-workflow token attribution on the AI usage dashboard, with a ready-made template that alerts when usage reaches 80% of quota.
   • Enables testing a custom agent against a real violation before publishing — returning the verdict, reasoning, and token consumption.
   • Adds Custom Maestro Agents: define an agent's analysis instructions, evidence to weigh, and up to three named outcomes (plus a reserved Failure outcome) in the AI agents library — covering use cases like upgrade impact analysis, credential validity, and code ownership mapping.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Adds confidence thresholds per outcome branch (default 70%) so a branch executes only when the agent's confidence meets the configured minimum.
   • Adds Require human approval toggle on any outcome branch's first action, surfacing the agent's recommendation in Required Approvals before anything executes.
   • Locks agent outcomes while a workflow uses an agent (Stable logic), preventing branch-breaking changes as the agent's instructions evolve.
   • Adds per-workflow token attribution on the AI usage dashboard, with a ready-made template that alerts when usage reaches 80% of quota.

   +1 more show less

   • Enables testing a custom agent against a real violation before publishing — returning the verdict, reasoning, and token consumption.

   1 more in Everything

5. LiteLLM 1.107.0: Stopping a Poisoned Package Before It Installs (2026-10-21) Oct 21, 2026 · issue 116

   Cycode adds real-time Workstation Protection with cooldown policies and threat-intel blocking to stop malicious packages at install time.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   └──▷ HOW TO FIND IT
   Enforce a cooldown policy so any package version published within the last few days is held on developer and CI machines — blocking a same-day malicious release like LiteLLM 1.107.0 before it installs.
   📍In the Cycode console, go to Workstation Protection › Policies and set the cooldown period to the desired number of days. Deploy the agent to developer machines and CI runners via your MDM provider.
   • Introduces Cycode Workstation Protection (early access), deployable via MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies., which intercepts package installs on developer and CI machines in real time and applies a configurable cooldown policy to hold back recently published versions.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Adds a threat intelligence feed check to Workstation Protection that blocks known-malicious package versions independently of the cooldown window.
   • Extends SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. and AIBOMAIBOMAn inventory of every AI model, dataset, and dependency used in a system, analogous to a software bill of materials, giving cyber tools a structured way to audit AI supply-chain risk. generation to cover AI/LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. dependencies (AIBOMs), surfacing transitive pulls like LiteLLM from agent frameworks such as DSPy and CrewAI.
   • Extends container scanning to detect poisoned proxy images on floating tags (such as latest, main-latest, main-stable) in connected registries.
   • The Context Intelligence GraphIntelligence GraphA graph database structure linking entities such as hosts, IPs, domains, and threat actors by relationship, letting cyber tools traverse connections to surface context that flat tables cannot express. links a finding to its repo, image, pipeline, and team, enabling a single query to list all locations where a specific package version appears and identify owners.

   +1 more show less

   • Cimon, Cycode's eBPFeBPFA Linux technology for running verified programs inside the kernel without changing its source. Tools use it to observe processes, enforce rules and process network traffic.-based build monitor, watches network calls, file writes, and processes on CI runners to detect supply-chain payload behaviors such as .pth file writes into site-packages.
   • Introduces Cycode Workstation Protection (early access), deployable via MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies., which intercepts package installs on developer and CI machines in real time and applies a configurable cooldown policy to hold back recently published versions.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Adds a threat intelligence feed check to Workstation Protection that blocks known-malicious package versions independently of the cooldown window.
   • Cimon, Cycode's eBPFeBPFA Linux technology for running verified programs inside the kernel without changing its source. Tools use it to observe processes, enforce rules and process network traffic.-based build monitor, watches network calls, file writes, and processes on CI runners to detect supply-chain payload behaviors such as .pth file writes into site-packages.

   3 more in Everything

6. Cycode + Hugging Face: See & Secure Every AI Model (2026-09-29) Sep 29, 2026 · issue 090

   Cycode integrates with Hugging Face to inventory, enrich, and enforce governance over every AI model your org publishes or uses.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   └──▷ HOW TO FIND IT
   Connect Cycode to your Hugging Face organization to start inventorying all published AI models, including private ones that would never appear in a code repository.
   📍In the Cycode console, go to Integrations, select Hugging Face, provide a read-only token, and choose the organizations to sync. Cycode will pull all models immediately and refresh daily.
   Spot an internal model accidentally published as public, then mark it Unauthorized so violations are raised automatically and the decision is recorded in the audit log.
   📍In the Cycode AI Model inventory, filter by your organization namespace, identify models whose visibility is public that should be private, open the model record, and set its status to Unauthorized. The change is logged immediately.
   • Adds a Hugging Face integration that connects to your Hugging Face organizations via a read-only token and syncs only the organizations you select, with an initial full pull followed by daily refreshes.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Surfaces a unified AI model inventory combining models detected in your code repositories with models published by your connected Hugging Face organizations, including private org models that never appear in a repo.
   • Enriches each model with governance metadata pulled from Hugging Face: license, public/private visibility, gated-download status, base-model lineage, parameter count and precision, file types and serialization formats, downloads, likes, Spaces usage count, and benchmark availability.
   • Introduces a per-model authorization workflow — mark each model as Not reviewed, Authorized, or Unauthorized directly from the inventory — with Unauthorized models automatically raising violations and every status change written to the audit log.
   • Enables namespace filtering in the inventory so teams can review all models published by a single provider or Hugging Face organization at once.

   5 details in Everything

7. Introducing Cycode Workstation Protection: ADLC Security Now Stops Software Supply Chain Attacks (2026-09-23) Sep 23, 2026 · issue 2026/09

   Cycode Workstation Protection adds real-time package install enforcement with cooldown policies and malicious package threat intelligence.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   • Adds Workstation Protection, a new capability that intercepts package install commands in real time to enforce cooldown (release-age gating) policies and block known malicious packages before they install on developer workstations.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Deploys Workstation Protection via Mobile Device Management (MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies.) with no new console, no new infrastructure, and no change to developer install workflows.
   • Checks every package install against a continuously updated threat intelligence feed to catch malicious packages that have aged past cooldown windows, including typosquattingtyposquattingUsing a name close to a trusted domain or software package to catch spelling mistakes. Attackers use it to lure people or installers to a malicious lookalike., slopsquattingslopsquattingPublishing malicious packages under names invented by AI coding tools. A developer who installs a hallucinated dependency may then retrieve the attacker's real package., and persistent compromised maintainer releases.
   • Enforces cooldown policies at the device level, so gating applies regardless of which package manager version a developer or coding agent is running or whether a local config file was configured correctly.
   • Extends ADLC Security coverage upstream to the developer workstation, unifying workstation package enforcement with existing AI Bill of MaterialsBill of MaterialsA structured list of every component, library, and dependency that makes up a piece of software or hardware, used by cyber tools to track what is inside a product and surface known vulnerabilities in its parts., prompt guardrails, pipeline integrity, and secret scanningsecret scanningChecking files, code or other data for exposed credentials such as passwords, API keys and tokens. Findings help teams remove the secret and revoke or rotate it. into the Context Intelligence GraphIntelligence GraphA graph database structure linking entities such as hosts, IPs, domains, and threat actors by relationship, letting cyber tools traverse connections to surface context that flat tables cannot express..
   • Adds Workstation Protection, a new capability that intercepts package install commands in real time to enforce cooldown (release-age gating) policies and block known malicious packages before they install on developer workstations.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Deploys Workstation Protection via Mobile Device Management (MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies.) with no new console, no new infrastructure, and no change to developer install workflows.
   • Checks every package install against a continuously updated threat intelligence feed to catch malicious packages that have aged past cooldown windows, including typosquattingtyposquattingUsing a name close to a trusted domain or software package to catch spelling mistakes. Attackers use it to lure people or installers to a malicious lookalike., slopsquattingslopsquattingPublishing malicious packages under names invented by AI coding tools. A developer who installs a hallucinated dependency may then retrieve the attacker's real package., and persistent compromised maintainer releases.
   • Enforces cooldown policies at the device level, so gating applies regardless of which package manager version a developer or coding agent is running or whether a local config file was configured correctly.

   1 more in Everything

8. Introducing Cycode Workstation Protection: ADLC Security Now Stops Software Supply Chain Attacks (2026-09-23) Sep 23, 2026 · issue 2026/q3

   Cycode Workstation Protection adds real-time package install enforcement with cooldown policies and malicious package threat intelligence.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   • Adds Workstation Protection, a new capability that intercepts package install commands in real time to enforce cooldown (release-age gating) policies and block known malicious packages before they install on developer workstations.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Deploys Workstation Protection via Mobile Device Management (MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies.) with no new console, no new infrastructure, and no change to developer install workflows.
   • Checks every package install against a continuously updated threat intelligence feed to catch malicious packages that have aged past cooldown windows, including typosquattingtyposquattingUsing a name close to a trusted domain or software package to catch spelling mistakes. Attackers use it to lure people or installers to a malicious lookalike., slopsquattingslopsquattingPublishing malicious packages under names invented by AI coding tools. A developer who installs a hallucinated dependency may then retrieve the attacker's real package., and persistent compromised maintainer releases.
   • Enforces cooldown policies at the device level, so gating applies regardless of which package manager version a developer or coding agent is running or whether a local config file was configured correctly.
   • Extends ADLC Security coverage upstream to the developer workstation, unifying workstation package enforcement with existing AI Bill of MaterialsBill of MaterialsA structured list of every component, library, and dependency that makes up a piece of software or hardware, used by cyber tools to track what is inside a product and surface known vulnerabilities in its parts., prompt guardrails, pipeline integrity, and secret scanningsecret scanningChecking files, code or other data for exposed credentials such as passwords, API keys and tokens. Findings help teams remove the secret and revoke or rotate it. into the Context Intelligence GraphIntelligence GraphA graph database structure linking entities such as hosts, IPs, domains, and threat actors by relationship, letting cyber tools traverse connections to surface context that flat tables cannot express..
   • Adds Workstation Protection, a new capability that intercepts package install commands in real time to enforce cooldown (release-age gating) policies and block known malicious packages before they install on developer workstations.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Deploys Workstation Protection via Mobile Device Management (MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies.) with no new console, no new infrastructure, and no change to developer install workflows.
   • Checks every package install against a continuously updated threat intelligence feed to catch malicious packages that have aged past cooldown windows, including typosquattingtyposquattingUsing a name close to a trusted domain or software package to catch spelling mistakes. Attackers use it to lure people or installers to a malicious lookalike., slopsquattingslopsquattingPublishing malicious packages under names invented by AI coding tools. A developer who installs a hallucinated dependency may then retrieve the attacker's real package., and persistent compromised maintainer releases.
   • Enforces cooldown policies at the device level, so gating applies regardless of which package manager version a developer or coding agent is running or whether a local config file was configured correctly.

   1 more in Everything

9. Introducing Cycode Workstation Protection: ADLC Security Now Stops Software Supply Chain Attacks (2026-09-23) Sep 23, 2026 · issue 083

   Cycode Workstation Protection adds real-time package install enforcement with cooldown policies and malicious package threat intelligence.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   • Adds Workstation Protection, a new capability that intercepts package install commands in real time to enforce cooldown (release-age gating) policies and block known malicious packages before they install on developer workstations.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Deploys Workstation Protection via Mobile Device Management (MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies.) with no new console, no new infrastructure, and no change to developer install workflows.
   • Checks every package install against a continuously updated threat intelligence feed to catch malicious packages that have aged past cooldown windows, including typosquattingtyposquattingUsing a name close to a trusted domain or software package to catch spelling mistakes. Attackers use it to lure people or installers to a malicious lookalike., slopsquattingslopsquattingPublishing malicious packages under names invented by AI coding tools. A developer who installs a hallucinated dependency may then retrieve the attacker's real package., and persistent compromised maintainer releases.
   • Enforces cooldown policies at the device level, so gating applies regardless of which package manager version a developer or coding agent is running or whether a local config file was configured correctly.
   • Extends ADLC Security coverage upstream to the developer workstation, unifying workstation package enforcement with existing AI Bill of MaterialsBill of MaterialsA structured list of every component, library, and dependency that makes up a piece of software or hardware, used by cyber tools to track what is inside a product and surface known vulnerabilities in its parts., prompt guardrails, pipeline integrity, and secret scanningsecret scanningChecking files, code or other data for exposed credentials such as passwords, API keys and tokens. Findings help teams remove the secret and revoke or rotate it. into the Context Intelligence GraphIntelligence GraphA graph database structure linking entities such as hosts, IPs, domains, and threat actors by relationship, letting cyber tools traverse connections to surface context that flat tables cannot express..
   • Adds Workstation Protection, a new capability that intercepts package install commands in real time to enforce cooldown (release-age gating) policies and block known malicious packages before they install on developer workstations.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Deploys Workstation Protection via Mobile Device Management (MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies.) with no new console, no new infrastructure, and no change to developer install workflows.
   • Checks every package install against a continuously updated threat intelligence feed to catch malicious packages that have aged past cooldown windows, including typosquattingtyposquattingUsing a name close to a trusted domain or software package to catch spelling mistakes. Attackers use it to lure people or installers to a malicious lookalike., slopsquattingslopsquattingPublishing malicious packages under names invented by AI coding tools. A developer who installs a hallucinated dependency may then retrieve the attacker's real package., and persistent compromised maintainer releases.
   • Enforces cooldown policies at the device level, so gating applies regardless of which package manager version a developer or coding agent is running or whether a local config file was configured correctly.

   1 more in Everything

10. Introducing Cycode Workstation Protection: ADLC Security Now Stops Software Supply Chain Attacks (2026-09-23) Sep 23, 2026 · issue 013

    Cycode Workstation Protection adds real-time package install enforcement with cooldown policies and malicious package threat intelligence.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • Adds Workstation Protection, a new capability that intercepts package install commands in real time to enforce cooldown (release-age gating) policies and block known malicious packages before they install on developer workstations.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Deploys Workstation Protection via Mobile Device Management (MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies.) with no new console, no new infrastructure, and no change to developer install workflows.
    • Checks every package install against a continuously updated threat intelligence feed to catch malicious packages that have aged past cooldown windows, including typosquattingtyposquattingUsing a name close to a trusted domain or software package to catch spelling mistakes. Attackers use it to lure people or installers to a malicious lookalike., slopsquattingslopsquattingPublishing malicious packages under names invented by AI coding tools. A developer who installs a hallucinated dependency may then retrieve the attacker's real package., and persistent compromised maintainer releases.
    • Enforces cooldown policies at the device level, so gating applies regardless of which package manager version a developer or coding agent is running or whether a local config file was configured correctly.
    • Extends ADLC Security coverage upstream to the developer workstation, unifying workstation package enforcement with existing AI Bill of MaterialsBill of MaterialsA structured list of every component, library, and dependency that makes up a piece of software or hardware, used by cyber tools to track what is inside a product and surface known vulnerabilities in its parts., prompt guardrails, pipeline integrity, and secret scanningsecret scanningChecking files, code or other data for exposed credentials such as passwords, API keys and tokens. Findings help teams remove the secret and revoke or rotate it. into the Context Intelligence GraphIntelligence GraphA graph database structure linking entities such as hosts, IPs, domains, and threat actors by relationship, letting cyber tools traverse connections to surface context that flat tables cannot express..
    • Adds Workstation Protection, a new capability that intercepts package install commands in real time to enforce cooldown (release-age gating) policies and block known malicious packages before they install on developer workstations.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Deploys Workstation Protection via Mobile Device Management (MDMMDMMobile device management, centrally configuring and managing enrolled devices. Administrators use it to apply settings, distribute applications and enforce device security policies.) with no new console, no new infrastructure, and no change to developer install workflows.
    • Checks every package install against a continuously updated threat intelligence feed to catch malicious packages that have aged past cooldown windows, including typosquattingtyposquattingUsing a name close to a trusted domain or software package to catch spelling mistakes. Attackers use it to lure people or installers to a malicious lookalike., slopsquattingslopsquattingPublishing malicious packages under names invented by AI coding tools. A developer who installs a hallucinated dependency may then retrieve the attacker's real package., and persistent compromised maintainer releases.
    • Enforces cooldown policies at the device level, so gating applies regardless of which package manager version a developer or coding agent is running or whether a local config file was configured correctly.

    1 more in Everything

11. Introducing Agentic Code Scanning: The Holistic Cycode System Around the Model (2026-09-01) Sep 1, 2026 · issue 2026/09

    Cycode adds Agentic Code Scanning as a fourth scanning dimension, catching authorization vulnerabilities that rule engines structurally cannot detect.

    • Adds Agentic Code Scanning (Dimension 4) — an agent-orchestrated layer that plans from a threat model, ranks code by vulnerability class, and disproves findings before surfacing them, enabling detection of logic-level flaws like broken access control that have no matchable pattern.
    • Introduces per-scan configuration of mode, model, and scope as three independent dials, so teams can target expensive reasoning only at code classes that rules cannot describe while keeping deterministic scanning on every commit.
    • Adds attack-chain synthesis that links related findings across files into a single multi-step exploit path, carrying data flow from untrusted source to dangerous sink and tagging the resulting risk category (e.g. Code Injection — Critical).
    • Adds Agentic Workflows that consume exploitability-qualified findings and automate remediation: teams define triggering events, agent action sequences, and confidence thresholds once, and the workflow fires automatically — routing findings to the owning engineer and returning fixes as reviewable pull requests with a full audit trail.
    • Implements a self-improving flywheel where Agentic Code Scanning findings that generalize are automatically converted into new deterministic SASTSASTStatic application security testing, analyzing source code or compiled code for vulnerabilities without running the application. It helps developers find problems before deployment. rules (Dimension 1/2), so a class caught once by the model re-runs at near-zero cost indefinitely.

    +2 more show less

    • Detected authorization CVEs (gitea CVE-2025-68941 and next.js CVE-2025-29927) that Semgrep OSSOSSOpen-source software: code whose licence permits anyone to inspect, modify, and redistribute it. Cyber tools build on it to reuse auditable libraries without licensing fees., CodeQL, and Cycode's own rule engine all missed, across a ten-repository, six-language benchmark on an affordable open-weights reasoning model.
    • Integrates with Cycode's Context Intelligence GraphIntelligence GraphA graph database structure linking entities such as hosts, IPs, domains, and threat actors by relationship, letting cyber tools traverse connections to surface context that flat tables cannot express. to ground attack chains in real call relationships, ownership, and reachability rather than speculative model inference.

    7 details in Everything

12. Introducing Agentic Code Scanning: The Holistic Cycode System Around the Model (2026-09-01) Sep 1, 2026 · issue 2026/q3

    Cycode adds Agentic Code Scanning as a fourth scanning dimension, catching authorization vulnerabilities that rule engines structurally cannot detect.

    • Adds Agentic Code Scanning (Dimension 4) — an agent-orchestrated layer that plans from a threat model, ranks code by vulnerability class, and disproves findings before surfacing them, enabling detection of logic-level flaws like broken access control that have no matchable pattern.
    • Introduces per-scan configuration of mode, model, and scope as three independent dials, so teams can target expensive reasoning only at code classes that rules cannot describe while keeping deterministic scanning on every commit.
    • Adds attack-chain synthesis that links related findings across files into a single multi-step exploit path, carrying data flow from untrusted source to dangerous sink and tagging the resulting risk category (e.g. Code Injection — Critical).
    • Adds Agentic Workflows that consume exploitability-qualified findings and automate remediation: teams define triggering events, agent action sequences, and confidence thresholds once, and the workflow fires automatically — routing findings to the owning engineer and returning fixes as reviewable pull requests with a full audit trail.
    • Implements a self-improving flywheel where Agentic Code Scanning findings that generalize are automatically converted into new deterministic SASTSASTStatic application security testing, analyzing source code or compiled code for vulnerabilities without running the application. It helps developers find problems before deployment. rules (Dimension 1/2), so a class caught once by the model re-runs at near-zero cost indefinitely.

    +2 more show less

    • Detected authorization CVEs (gitea CVE-2025-68941 and next.js CVE-2025-29927) that Semgrep OSSOSSOpen-source software: code whose licence permits anyone to inspect, modify, and redistribute it. Cyber tools build on it to reuse auditable libraries without licensing fees., CodeQL, and Cycode's own rule engine all missed, across a ten-repository, six-language benchmark on an affordable open-weights reasoning model.
    • Integrates with Cycode's Context Intelligence GraphIntelligence GraphA graph database structure linking entities such as hosts, IPs, domains, and threat actors by relationship, letting cyber tools traverse connections to surface context that flat tables cannot express. to ground attack chains in real call relationships, ownership, and reachability rather than speculative model inference.

    7 details in Everything

13. Introducing Agentic Code Scanning: The Holistic Cycode System Around the Model (2026-09-01) Sep 1, 2026 · issue 061

    Cycode adds Agentic Code Scanning as a fourth scanning dimension, catching authorization vulnerabilities that rule engines structurally cannot detect.

    • Adds Agentic Code Scanning (Dimension 4) — an agent-orchestrated layer that plans from a threat model, ranks code by vulnerability class, and disproves findings before surfacing them, enabling detection of logic-level flaws like broken access control that have no matchable pattern.
    • Introduces per-scan configuration of mode, model, and scope as three independent dials, so teams can target expensive reasoning only at code classes that rules cannot describe while keeping deterministic scanning on every commit.
    • Adds attack-chain synthesis that links related findings across files into a single multi-step exploit path, carrying data flow from untrusted source to dangerous sink and tagging the resulting risk category (e.g. Code Injection — Critical).
    • Adds Agentic Workflows that consume exploitability-qualified findings and automate remediation: teams define triggering events, agent action sequences, and confidence thresholds once, and the workflow fires automatically — routing findings to the owning engineer and returning fixes as reviewable pull requests with a full audit trail.
    • Implements a self-improving flywheel where Agentic Code Scanning findings that generalize are automatically converted into new deterministic SASTSASTStatic application security testing, analyzing source code or compiled code for vulnerabilities without running the application. It helps developers find problems before deployment. rules (Dimension 1/2), so a class caught once by the model re-runs at near-zero cost indefinitely.

    +2 more show less

    • Detected authorization CVEs (gitea CVE-2025-68941 and next.js CVE-2025-29927) that Semgrep OSSOSSOpen-source software: code whose licence permits anyone to inspect, modify, and redistribute it. Cyber tools build on it to reuse auditable libraries without licensing fees., CodeQL, and Cycode's own rule engine all missed, across a ten-repository, six-language benchmark on an affordable open-weights reasoning model.
    • Integrates with Cycode's Context Intelligence GraphIntelligence GraphA graph database structure linking entities such as hosts, IPs, domains, and threat actors by relationship, letting cyber tools traverse connections to surface context that flat tables cannot express. to ground attack chains in real call relationships, ownership, and reachability rather than speculative model inference.

    7 details in Everything

14. Introducing Agentic Code Scanning: The Holistic Cycode System Around Any Model (2026-09-01) Sep 1, 2026 · issue 061

    Cycode adds Agentic Code Scanning: a four-dimension system that orchestrates rules, AI triage, and agentic reasoning to catch authorization flaws no rule engine can express.

    • Adds Agentic Code Scanning (Dimension 4) — an orchestration layer that plans from a threat model, ranks what the model reads per vulnerability class, and disproves every finding before surfacing it, running above the three deterministic/AI tiers.
    • Introduces per-scan control over mode, model, and scope as three independent dials, with every scan recording what ran, when, on which code, and with which model for auditability.
    • Agentic reasoning promotes confirmed vulnerability mechanisms into new deterministic SASTSASTStatic application security testing, analyzing source code or compiled code for vulnerabilities without running the application. It helps developers find problems before deployment. rules (Dimension 1/2), so a class found by the expensive layer is caught at near-zero cost on every subsequent run, compounding coverage as repo count grows.

    3 details in Everything

15. Introducing Agentic Code Scanning: The Holistic Cycode System Around the Model (2026-09-01) Sep 1, 2026 · issue 010

    Cycode adds Agentic Code Scanning as a fourth scanning dimension, catching authorization vulnerabilities that rule engines structurally cannot detect.

    • Adds Agentic Code Scanning (Dimension 4) — an agent-orchestrated layer that plans from a threat model, ranks code by vulnerability class, and disproves findings before surfacing them, enabling detection of logic-level flaws like broken access control that have no matchable pattern.
    • Introduces per-scan configuration of mode, model, and scope as three independent dials, so teams can target expensive reasoning only at code classes that rules cannot describe while keeping deterministic scanning on every commit.
    • Adds attack-chain synthesis that links related findings across files into a single multi-step exploit path, carrying data flow from untrusted source to dangerous sink and tagging the resulting risk category (e.g. Code Injection — Critical).
    • Adds Agentic Workflows that consume exploitability-qualified findings and automate remediation: teams define triggering events, agent action sequences, and confidence thresholds once, and the workflow fires automatically — routing findings to the owning engineer and returning fixes as reviewable pull requests with a full audit trail.
    • Implements a self-improving flywheel where Agentic Code Scanning findings that generalize are automatically converted into new deterministic SASTSASTStatic application security testing, analyzing source code or compiled code for vulnerabilities without running the application. It helps developers find problems before deployment. rules (Dimension 1/2), so a class caught once by the model re-runs at near-zero cost indefinitely.

    +2 more show less

    • Detected authorization CVEs (gitea CVE-2025-68941 and next.js CVE-2025-29927) that Semgrep OSSOSSOpen-source software: code whose licence permits anyone to inspect, modify, and redistribute it. Cyber tools build on it to reuse auditable libraries without licensing fees., CodeQL, and Cycode's own rule engine all missed, across a ten-repository, six-language benchmark on an affordable open-weights reasoning model.
    • Integrates with Cycode's Context Intelligence GraphIntelligence GraphA graph database structure linking entities such as hosts, IPs, domains, and threat actors by relationship, letting cyber tools traverse connections to surface context that flat tables cannot express. to ground attack chains in real call relationships, ownership, and reachability rather than speculative model inference.

    7 details in Everything