{"id":57598,"date":"2026-06-01T11:07:24","date_gmt":"2026-06-01T01:07:24","guid":{"rendered":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/"},"modified":"2026-06-01T11:08:52","modified_gmt":"2026-06-01T01:08:52","slug":"the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait","status":"publish","type":"post","link":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/","title":{"rendered":"The npm Dependency Confusion and Nx Console Supply Chain Attacks Show Why Azure DevOps Pipeline Hardening Can&#8217;t Wait"},"content":{"rendered":"<p class=\"wp-block-paragraph\">Software supply chain attacks are no longer a theoretical risk for development teams. They are now a practical business risk that can expose credentials, disrupt delivery, leak source code, and create regulatory headaches within minutes.<\/p>\n\n<p class=\"wp-block-paragraph\">For Australian organisations using Azure DevOps, npm, private packages, GitHub, VS Code extensions, and self-hosted build agents, the message is clear: pipeline hardening cannot wait for the next audit cycle.<\/p>\n\n<p class=\"wp-block-paragraph\">Recent dependency confusion campaigns and the high-profile attacks involving the Nx ecosystem and Nx Console show how quickly trusted developer tooling can become an entry point. The damage is not limited to a developer laptop. In many environments, the same credentials, package feeds, service connections, and build agents are connected directly to production delivery paths.<\/p>\n\n<p class=\"wp-block-paragraph\">That is why CI\/CD security now needs to be treated as a board-level operational resilience issue, not just a developer hygiene task.<\/p>\n\n<h2 class=\"wp-block-heading\">Why dependency confusion is so dangerous<\/h2>\n\n<p class=\"wp-block-paragraph\">Dependency confusion occurs when a package manager resolves a package name from the wrong source.<\/p>\n\n<p class=\"wp-block-paragraph\">A common example is an organisation using an internal npm package such as <code>company-utils<\/code> in a private feed. If an attacker publishes a package with the same name to the public npm registry, and the build process is not configured correctly, npm may pull the public malicious package instead of the intended private one.<\/p>\n\n<p class=\"wp-block-paragraph\">The attack is simple in concept but powerful in practice because it targets automation.<\/p>\n\n<p class=\"wp-block-paragraph\">A compromised package can run during installation, often through lifecycle scripts such as <code>postinstall<\/code>. From there it may attempt to:<\/p>\n\n<ul class=\"wp-block-list\"><li>Read environment variables<\/li><li>Steal npm, GitHub, Azure, or cloud credentials<\/li><li>Enumerate source code and repositories<\/li><li>Exfiltrate secrets from <code>.env<\/code> files<\/li><li>Modify build outputs<\/li><li>Establish persistence on self-hosted build agents<\/li><li>Open outbound network connections to attacker-controlled infrastructure<\/li><\/ul>\n\n<p class=\"wp-block-paragraph\">In an Azure DevOps pipeline, that can mean a malicious package runs in an environment that has access to deployment credentials, package feeds, container registries, signing keys, or production infrastructure.<\/p>\n\n<p class=\"wp-block-paragraph\">That is the real concern. The package is not just attacking a workstation. It is attacking the delivery system.<\/p>\n\n<h2 class=\"wp-block-heading\">What the Nx and Nx Console incidents changed<\/h2>\n\n<p class=\"wp-block-paragraph\">The Nx supply chain incident, known as <code>s1ngularity<\/code>, showed how a trusted open-source build ecosystem can become a credential collection mechanism. Public reporting described malicious npm versions that executed during installation, searched for sensitive files and credentials, and exfiltrated data.<\/p>\n\n<p class=\"wp-block-paragraph\">The incident was especially concerning because it reportedly attempted to abuse local AI command-line tools to accelerate reconnaissance and data collection. That matters because many engineering teams are now adopting AI coding assistants and developer agents without fully considering how those tools behave when invoked by untrusted code.<\/p>\n\n<p class=\"wp-block-paragraph\">Separately, public reporting around the Nx Console VS Code extension highlighted another uncomfortable reality: developer extensions are part of the software supply chain too. IDE plugins often sit close to source code, tokens, repositories, terminals, and developer workflows. If compromised, they may provide attackers with access that traditional perimeter controls never see.<\/p>\n\n<p class=\"wp-block-paragraph\">The lesson is not that teams should avoid open-source tools or developer extensions. The lesson is that trust needs to be verified continuously.<\/p>\n\n<p class=\"wp-block-paragraph\">Every package, extension, build script, token, and service connection should be treated as part of the attack surface.<\/p>\n\n<h2 class=\"wp-block-heading\">Why Azure DevOps pipelines are a high-value target<\/h2>\n\n<p class=\"wp-block-paragraph\">Azure DevOps pipelines are attractive because they sit at the intersection of code, identity, infrastructure, and release automation.<\/p>\n\n<p class=\"wp-block-paragraph\">A typical pipeline may be able to:<\/p>\n\n<ul class=\"wp-block-list\"><li>Pull source code<\/li><li>Authenticate to private package feeds<\/li><li>Build and sign artifacts<\/li><li>Push container images<\/li><li>Deploy to Azure subscriptions<\/li><li>Access Key Vault secrets<\/li><li>Run database migrations<\/li><li>Promote releases into production<\/li><\/ul>\n\n<p class=\"wp-block-paragraph\">If an attacker can influence what runs in the pipeline, they may not need to breach production directly. They can compromise the path that production already trusts.<\/p>\n\n<p class=\"wp-block-paragraph\">This is why supply chain attacks often focus on the build stage. Build systems usually have broad visibility, strong credentials, and a high level of implicit trust.<\/p>\n\n<p class=\"wp-block-paragraph\">For mid-market Australian organisations, this is a major concern. Many teams have modernised quickly, adopted Azure DevOps, added npm-based front ends, introduced container builds, and connected pipelines to cloud environments. But pipeline security controls often lag behind delivery speed.<\/p>\n\n<p class=\"wp-block-paragraph\">That gap creates risk.<\/p>\n\n<h2 class=\"wp-block-heading\">The business impact goes beyond security<\/h2>\n\n<p class=\"wp-block-paragraph\">A supply chain compromise can quickly become a business continuity event.<\/p>\n\n<p class=\"wp-block-paragraph\">The impact may include:<\/p>\n\n<ul class=\"wp-block-list\"><li>Delayed releases while teams investigate build integrity<\/li><li>Emergency credential rotation across GitHub, Azure, npm, and third-party systems<\/li><li>Rebuilding self-hosted agents from clean images<\/li><li>Reviewing source code exposure<\/li><li>Notifying customers, partners, or regulators where data may be affected<\/li><li>Increased cyber insurance scrutiny<\/li><li>Loss of confidence in internal software delivery<\/li><\/ul>\n\n<p class=\"wp-block-paragraph\">For organisations subject to Australian privacy obligations, a compromised pipeline may also raise questions about whether personal information, credentials, or customer data were exposed.<\/p>\n\n<p class=\"wp-block-paragraph\">For regulated sectors, the incident response burden can be even higher. Evidence, audit logs, access reviews, and chain-of-custody become critical.<\/p>\n\n<p class=\"wp-block-paragraph\">This is where pipeline hardening supports more than cybersecurity. It supports operational resilience, privacy governance, and executive risk management.<\/p>\n\n<h2 class=\"wp-block-heading\">Practical Azure DevOps hardening controls that reduce risk<\/h2>\n\n<p class=\"wp-block-paragraph\">Pipeline hardening does not require a single silver bullet. It requires layered controls that reduce the chance of compromise and limit blast radius when something goes wrong.<\/p>\n\n<h3 class=\"wp-block-heading\">1. Lock down npm package resolution<\/h3>\n\n<p class=\"wp-block-paragraph\">Organisations using private npm packages should remove ambiguity from package resolution.<\/p>\n\n<p class=\"wp-block-paragraph\">Key controls include:<\/p>\n\n<ul class=\"wp-block-list\"><li>Use scoped package names such as <code>@company\/internal-package<\/code><\/li><li>Configure <code>.npmrc<\/code> so private scopes resolve only from approved private feeds<\/li><li>Use Azure Artifacts or another trusted package repository for internal packages<\/li><li>Avoid unintended fallback from private feeds to the public npm registry<\/li><li>Reserve important package names where appropriate<\/li><li>Monitor public registries for names that match internal packages<\/li><\/ul>\n\n<p class=\"wp-block-paragraph\">The goal is simple: a build should never guess where to get a critical package from.<\/p>\n\n<h3 class=\"wp-block-heading\">2. Use deterministic installs<\/h3>\n\n<p class=\"wp-block-paragraph\">Pipelines should not install whatever happens to match a loose version range on the day of the build.<\/p>\n\n<p class=\"wp-block-paragraph\">Recommended practices include:<\/p>\n\n<ul class=\"wp-block-list\"><li>Commit and protect lockfiles such as <code>package-lock.json<\/code> or <code>pnpm-lock.yaml<\/code><\/li><li>Use <code>npm ci<\/code> instead of <code>npm install<\/code> in CI environments<\/li><li>Pin critical dependencies where appropriate<\/li><li>Review dependency updates through pull requests<\/li><li>Avoid automatic production builds from unreviewed dependency changes<\/li><\/ul>\n\n<p class=\"wp-block-paragraph\">Deterministic builds make incident response much easier. When a malicious package is disclosed, teams can quickly identify which builds used which versions.<\/p>\n\n<h3 class=\"wp-block-heading\">3. Restrict install scripts<\/h3>\n\n<p class=\"wp-block-paragraph\">Many npm supply chain attacks rely on install-time scripts.<\/p>\n\n<p class=\"wp-block-paragraph\">Controls to consider include:<\/p>\n\n<ul class=\"wp-block-list\"><li>Set <code>ignore-scripts=true<\/code> where feasible<\/li><li>Allow install scripts only for packages that genuinely require them<\/li><li>Run dependency installation in a restricted environment<\/li><li>Monitor unexpected child processes during package installation<\/li><li>Review new dependencies that introduce lifecycle scripts<\/li><\/ul>\n\n<p class=\"wp-block-paragraph\">This may require engineering adjustment, but it is one of the most effective ways to reduce exposure to malicious <code>postinstall<\/code> behaviour.<\/p>\n\n<h3 class=\"wp-block-heading\">4. Protect secrets and service connections<\/h3>\n\n<p class=\"wp-block-paragraph\">Azure DevOps service connections and secrets should be treated as high-value assets.<\/p>\n\n<p class=\"wp-block-paragraph\">Recommended controls include:<\/p>\n\n<ul class=\"wp-block-list\"><li>Prefer workload identity federation or managed identities where possible<\/li><li>Avoid long-lived client secrets and personal access tokens<\/li><li>Scope service connections to the smallest practical resource boundary<\/li><li>Do not grant service connections to all pipelines by default<\/li><li>Require explicit pipeline authorisation<\/li><li>Store secrets in Azure Key Vault rather than YAML files or variable values<\/li><li>Rotate secrets regularly and immediately after suspected exposure<\/li><\/ul>\n\n<p class=\"wp-block-paragraph\">A pipeline should only have the access it needs for that stage, environment, and application.<\/p>\n\n<h3 class=\"wp-block-heading\">5. Isolate and rebuild self-hosted agents<\/h3>\n\n<p class=\"wp-block-paragraph\">Self-hosted agents are powerful but risky if not managed carefully.<\/p>\n\n<p class=\"wp-block-paragraph\">If a malicious package executes on a persistent build agent, the agent may retain malware, cached credentials, modified tooling, or altered build state.<\/p>\n\n<p class=\"wp-block-paragraph\">Better practice includes:<\/p>\n\n<ul class=\"wp-block-list\"><li>Use ephemeral agents where possible<\/li><li>Separate agent pools by trust level and environment<\/li><li>Avoid sharing agents between development and production deployment pipelines<\/li><li>Restrict outbound internet access from agents<\/li><li>Rebuild agents from clean images after suspicious activity<\/li><li>Monitor agent filesystem, process, and network behaviour<\/li><\/ul>\n\n<p class=\"wp-block-paragraph\">For many organisations, self-hosted agents are where theoretical supply chain risk becomes practical compromise.<\/p>\n\n<h3 class=\"wp-block-heading\">6. Add SBOM and dependency visibility<\/h3>\n\n<p class=\"wp-block-paragraph\">A software bill of materials helps teams understand what they are actually shipping.<\/p>\n\n<p class=\"wp-block-paragraph\">Azure DevOps pipelines should generate and retain SBOMs for key builds, especially production releases. This supports faster answers to questions such as:<\/p>\n\n<ul class=\"wp-block-list\"><li>Did we use the affected package version?<\/li><li>Which application included it?<\/li><li>Which customers or environments received it?<\/li><li>Which build produced the artifact?<\/li><li>Which pipeline identity deployed it?<\/li><\/ul>\n\n<p class=\"wp-block-paragraph\">Without dependency visibility, incident response becomes guesswork.<\/p>\n\n<h3 class=\"wp-block-heading\">7. Enforce approvals and branch protection<\/h3>\n\n<p class=\"wp-block-paragraph\">Pipeline YAML is code. It should be protected like application code.<\/p>\n\n<p class=\"wp-block-paragraph\">Important controls include:<\/p>\n\n<ul class=\"wp-block-list\"><li>Require pull request reviews for pipeline changes<\/li><li>Restrict who can edit build and release definitions<\/li><li>Require approvals for production deployments<\/li><li>Protect main branches and release branches<\/li><li>Restrict variable group and library permissions<\/li><li>Review marketplace extensions and third-party tasks before use<\/li><\/ul>\n\n<p class=\"wp-block-paragraph\">Attackers increasingly target the workflow, not just the application.<\/p>\n\n<h2 class=\"wp-block-heading\">Mapping pipeline hardening to Australian cyber expectations<\/h2>\n\n<p class=\"wp-block-paragraph\">For Australian organisations, Azure DevOps pipeline hardening aligns strongly with ACSC and ASD guidance, including the intent behind the Essential Eight.<\/p>\n\n<p class=\"wp-block-paragraph\">Relevant themes include:<\/p>\n\n<ul class=\"wp-block-list\"><li>Application control: reducing unapproved code execution on endpoints and servers<\/li><li>Patch applications: responding quickly to compromised or vulnerable dependencies<\/li><li>Restrict administrative privileges: limiting what pipeline identities can do<\/li><li>Multi-factor authentication: protecting developer and administrator accounts<\/li><li>Regular backups: supporting recovery if build or source systems are disrupted<\/li><li>Logging and monitoring: detecting suspicious activity across build and deployment systems<\/li><\/ul>\n\n<p class=\"wp-block-paragraph\">The Essential Eight does not replace software supply chain security, but it provides a useful baseline. Pipeline hardening extends those principles into the engineering systems that build and deploy business applications.<\/p>\n\n<h2 class=\"wp-block-heading\">What organisations should do this month<\/h2>\n\n<p class=\"wp-block-paragraph\">This is not a problem that should wait for a large transformation program.<\/p>\n\n<p class=\"wp-block-paragraph\">A practical 30-day action plan could include:<\/p>\n\n<ol class=\"wp-block-list\"><li>Identify all Azure DevOps pipelines that run npm installs.<\/li><li>Review <code>.npmrc<\/code> configuration and private feed resolution.<\/li><li>Confirm lockfiles are committed and <code>npm ci<\/code> is used in CI.<\/li><li>Audit service connections for excessive scope.<\/li><li>Disable broad service connection access to all pipelines.<\/li><li>Review variable groups and Key Vault access.<\/li><li>Separate production deployment agents from general build agents.<\/li><li>Add dependency scanning and secret scanning to pull requests.<\/li><li>Generate SBOMs for production builds.<\/li><li>Create an incident response runbook for malicious package exposure.<\/li><\/ol>\n\n<p class=\"wp-block-paragraph\">The aim is not perfection in 30 days. The aim is to remove the most obvious paths attackers use.<\/p>\n\n<h2 class=\"wp-block-heading\">Final thought<\/h2>\n\n<p class=\"wp-block-paragraph\">The npm dependency confusion and Nx-related supply chain attacks are warnings that the trusted development path is now a primary target.<\/p>\n\n<p class=\"wp-block-paragraph\">For Azure DevOps users, hardening pipelines is no longer optional engineering polish. It is a necessary control for protecting credentials, source code, production systems, and business continuity.<\/p>\n\n<p class=\"wp-block-paragraph\">Our team helps Australian organisations review Azure DevOps security, reduce CI\/CD risk, and implement practical controls without slowing delivery. If your pipelines have grown quickly over time, now is the right moment to check whether they are still safe enough for the role they play in your business.<\/p>\n\n","protected":false},"excerpt":{"rendered":"<p>Software supply chain attacks are no longer a theoretical risk for development teams. They are now a practical business risk that can expose credentials, disrupt delivery, leak source code, and create regulatory headaches within minutes. For Australian organisations using Azure DevOps, npm, private packages, GitHub, VS Code extensions, and self-hosted build agents, the message is [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":57600,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_yoast_wpseo_opengraph-title":"The npm Dependency Confusion and Nx Console Supply Chain","_yoast_wpseo_opengraph-description":"Software supply chain attacks are no longer a theoretical risk for development teams.","_yoast_wpseo_twitter-title":"The npm Dependency Confusion and Nx Console Supply Chain","_yoast_wpseo_twitter-description":"Software supply chain attacks are no longer a theoretical risk for development teams.","_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[119,121,13,28],"tags":[],"class_list":["post-57598","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai-for-business-ai-strategy","category-ai-governance-risk-management","category-blog","category-c"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.3 (Yoast SEO v27.7) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>The npm Dependency Confusion and Nx Console Supply Chain<\/title>\n<meta name=\"description\" content=\"Software supply chain attacks are no longer a theoretical risk for development teams.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"The npm Dependency Confusion and Nx Console Supply Chain\" \/>\n<meta property=\"og:description\" content=\"Software supply chain attacks are no longer a theoretical risk for development teams.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/\" \/>\n<meta property=\"og:site_name\" content=\"CPI Consulting\" \/>\n<meta property=\"article:published_time\" content=\"2026-06-01T01:07:24+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-06-01T01:08:52+00:00\" \/>\n<meta name=\"author\" content=\"CPI Staff\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"The npm Dependency Confusion and Nx Console Supply Chain\" \/>\n<meta name=\"twitter:description\" content=\"Software supply chain attacks are no longer a theoretical risk for development teams.\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"CPI Staff\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.cloudproinc.com.au\\\/index.php\\\/2026\\\/06\\\/01\\\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cloudproinc.com.au\\\/index.php\\\/2026\\\/06\\\/01\\\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\\\/\"},\"author\":{\"name\":\"CPI Staff\",\"@id\":\"https:\\\/\\\/cloudproinc.azurewebsites.net\\\/#\\\/schema\\\/person\\\/192eeeb0ce91062126ce3822ae88fe6e\"},\"headline\":\"The npm Dependency Confusion and Nx Console Supply Chain Attacks Show Why Azure DevOps Pipeline Hardening Can&#8217;t Wait\",\"datePublished\":\"2026-06-01T01:07:24+00:00\",\"dateModified\":\"2026-06-01T01:08:52+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.cloudproinc.com.au\\\/index.php\\\/2026\\\/06\\\/01\\\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\\\/\"},\"wordCount\":1778,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/cloudproinc.azurewebsites.net\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.cloudproinc.com.au\\\/index.php\\\/2026\\\/06\\\/01\\\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\\\/#primaryimage\"},\"thumbnailUrl\":\"\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/the-npm-dependency-confusion-and-nx-console-supply-chain-att.png\",\"articleSection\":[\"AI for Business &amp; AI Strategy\",\"AI Governance &amp; Risk Management\",\"Blog\",\"C#\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.cloudproinc.com.au\\\/index.php\\\/2026\\\/06\\\/01\\\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.cloudproinc.com.au\\\/index.php\\\/2026\\\/06\\\/01\\\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\\\/\",\"url\":\"https:\\\/\\\/www.cloudproinc.com.au\\\/index.php\\\/2026\\\/06\\\/01\\\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\\\/\",\"name\":\"The npm Dependency Confusion and Nx Console Supply Chain\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/cloudproinc.azurewebsites.net\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.cloudproinc.com.au\\\/index.php\\\/2026\\\/06\\\/01\\\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.cloudproinc.com.au\\\/index.php\\\/2026\\\/06\\\/01\\\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\\\/#primaryimage\"},\"thumbnailUrl\":\"\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/the-npm-dependency-confusion-and-nx-console-supply-chain-att.png\",\"datePublished\":\"2026-06-01T01:07:24+00:00\",\"dateModified\":\"2026-06-01T01:08:52+00:00\",\"description\":\"Software supply chain attacks are no longer a theoretical risk for development teams.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.cloudproinc.com.au\\\/index.php\\\/2026\\\/06\\\/01\\\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.cloudproinc.com.au\\\/index.php\\\/2026\\\/06\\\/01\\\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.cloudproinc.com.au\\\/index.php\\\/2026\\\/06\\\/01\\\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\\\/#primaryimage\",\"url\":\"\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/the-npm-dependency-confusion-and-nx-console-supply-chain-att.png\",\"contentUrl\":\"\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/the-npm-dependency-confusion-and-nx-console-supply-chain-att.png\",\"width\":1536,\"height\":1024},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.cloudproinc.com.au\\\/index.php\\\/2026\\\/06\\\/01\\\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/cloudproinc.azurewebsites.net\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"The npm Dependency Confusion and Nx Console Supply Chain Attacks Show Why Azure DevOps Pipeline Hardening Can&#8217;t Wait\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/cloudproinc.azurewebsites.net\\\/#website\",\"url\":\"https:\\\/\\\/cloudproinc.azurewebsites.net\\\/\",\"name\":\"Cloud Pro Inc - CPI Consulting Pty Ltd\",\"description\":\"Cloud, AI &amp; Cybersecurity Consulting | Melbourne\",\"publisher\":{\"@id\":\"https:\\\/\\\/cloudproinc.azurewebsites.net\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/cloudproinc.azurewebsites.net\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/cloudproinc.azurewebsites.net\\\/#organization\",\"name\":\"Cloud Pro Inc - Cloud Pro Inc - CPI Consulting Pty Ltd\",\"url\":\"https:\\\/\\\/cloudproinc.azurewebsites.net\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/cloudproinc.azurewebsites.net\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"\\\/wp-content\\\/uploads\\\/2022\\\/01\\\/favfinalfile.png\",\"contentUrl\":\"\\\/wp-content\\\/uploads\\\/2022\\\/01\\\/favfinalfile.png\",\"width\":500,\"height\":500,\"caption\":\"Cloud Pro Inc - Cloud Pro Inc - CPI Consulting Pty Ltd\"},\"image\":{\"@id\":\"https:\\\/\\\/cloudproinc.azurewebsites.net\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/cloudproinc.azurewebsites.net\\\/#\\\/schema\\\/person\\\/192eeeb0ce91062126ce3822ae88fe6e\",\"name\":\"CPI Staff\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2d96eeb53b791d92c8c50dd667e3beec92c93253bb6ff21c02cfa8ca73665c70?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2d96eeb53b791d92c8c50dd667e3beec92c93253bb6ff21c02cfa8ca73665c70?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2d96eeb53b791d92c8c50dd667e3beec92c93253bb6ff21c02cfa8ca73665c70?s=96&d=mm&r=g\",\"caption\":\"CPI Staff\"},\"sameAs\":[\"http:\\\/\\\/www.cloudproinc.com.au\"],\"url\":\"https:\\\/\\\/www.cloudproinc.com.au\\\/index.php\\\/author\\\/cpiadmin\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"The npm Dependency Confusion and Nx Console Supply Chain","description":"Software supply chain attacks are no longer a theoretical risk for development teams.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/","og_locale":"en_US","og_type":"article","og_title":"The npm Dependency Confusion and Nx Console Supply Chain","og_description":"Software supply chain attacks are no longer a theoretical risk for development teams.","og_url":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/","og_site_name":"CPI Consulting","article_published_time":"2026-06-01T01:07:24+00:00","article_modified_time":"2026-06-01T01:08:52+00:00","author":"CPI Staff","twitter_card":"summary_large_image","twitter_title":"The npm Dependency Confusion and Nx Console Supply Chain","twitter_description":"Software supply chain attacks are no longer a theoretical risk for development teams.","twitter_misc":{"Written by":"CPI Staff","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/#article","isPartOf":{"@id":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/"},"author":{"name":"CPI Staff","@id":"https:\/\/cloudproinc.azurewebsites.net\/#\/schema\/person\/192eeeb0ce91062126ce3822ae88fe6e"},"headline":"The npm Dependency Confusion and Nx Console Supply Chain Attacks Show Why Azure DevOps Pipeline Hardening Can&#8217;t Wait","datePublished":"2026-06-01T01:07:24+00:00","dateModified":"2026-06-01T01:08:52+00:00","mainEntityOfPage":{"@id":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/"},"wordCount":1778,"commentCount":0,"publisher":{"@id":"https:\/\/cloudproinc.azurewebsites.net\/#organization"},"image":{"@id":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/#primaryimage"},"thumbnailUrl":"\/wp-content\/uploads\/2026\/06\/the-npm-dependency-confusion-and-nx-console-supply-chain-att.png","articleSection":["AI for Business &amp; AI Strategy","AI Governance &amp; Risk Management","Blog","C#"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/","url":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/","name":"The npm Dependency Confusion and Nx Console Supply Chain","isPartOf":{"@id":"https:\/\/cloudproinc.azurewebsites.net\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/#primaryimage"},"image":{"@id":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/#primaryimage"},"thumbnailUrl":"\/wp-content\/uploads\/2026\/06\/the-npm-dependency-confusion-and-nx-console-supply-chain-att.png","datePublished":"2026-06-01T01:07:24+00:00","dateModified":"2026-06-01T01:08:52+00:00","description":"Software supply chain attacks are no longer a theoretical risk for development teams.","breadcrumb":{"@id":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/#primaryimage","url":"\/wp-content\/uploads\/2026\/06\/the-npm-dependency-confusion-and-nx-console-supply-chain-att.png","contentUrl":"\/wp-content\/uploads\/2026\/06\/the-npm-dependency-confusion-and-nx-console-supply-chain-att.png","width":1536,"height":1024},{"@type":"BreadcrumbList","@id":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/06\/01\/the-npm-dependency-confusion-and-nx-console-supply-chain-attacks-show-why-azure-devops-pipeline-hardening-cant-wait\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/cloudproinc.azurewebsites.net\/"},{"@type":"ListItem","position":2,"name":"The npm Dependency Confusion and Nx Console Supply Chain Attacks Show Why Azure DevOps Pipeline Hardening Can&#8217;t Wait"}]},{"@type":"WebSite","@id":"https:\/\/cloudproinc.azurewebsites.net\/#website","url":"https:\/\/cloudproinc.azurewebsites.net\/","name":"Cloud Pro Inc - CPI Consulting Pty Ltd","description":"Cloud, AI &amp; Cybersecurity Consulting | Melbourne","publisher":{"@id":"https:\/\/cloudproinc.azurewebsites.net\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/cloudproinc.azurewebsites.net\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/cloudproinc.azurewebsites.net\/#organization","name":"Cloud Pro Inc - Cloud Pro Inc - CPI Consulting Pty Ltd","url":"https:\/\/cloudproinc.azurewebsites.net\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/cloudproinc.azurewebsites.net\/#\/schema\/logo\/image\/","url":"\/wp-content\/uploads\/2022\/01\/favfinalfile.png","contentUrl":"\/wp-content\/uploads\/2022\/01\/favfinalfile.png","width":500,"height":500,"caption":"Cloud Pro Inc - Cloud Pro Inc - CPI Consulting Pty Ltd"},"image":{"@id":"https:\/\/cloudproinc.azurewebsites.net\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/cloudproinc.azurewebsites.net\/#\/schema\/person\/192eeeb0ce91062126ce3822ae88fe6e","name":"CPI Staff","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/2d96eeb53b791d92c8c50dd667e3beec92c93253bb6ff21c02cfa8ca73665c70?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/2d96eeb53b791d92c8c50dd667e3beec92c93253bb6ff21c02cfa8ca73665c70?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/2d96eeb53b791d92c8c50dd667e3beec92c93253bb6ff21c02cfa8ca73665c70?s=96&d=mm&r=g","caption":"CPI Staff"},"sameAs":["http:\/\/www.cloudproinc.com.au"],"url":"https:\/\/www.cloudproinc.com.au\/index.php\/author\/cpiadmin\/"}]}},"jetpack_featured_media_url":"\/wp-content\/uploads\/2026\/06\/the-npm-dependency-confusion-and-nx-console-supply-chain-att.png","jetpack-related-posts":[{"id":57427,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/04\/12\/the-axios-supply-chain-attack-hit-openais-signing-pipeline-what-every-organisation-should-learn-about-dependency-governance\/","url_meta":{"origin":57598,"position":0},"title":"The Axios Supply Chain Attack Hit OpenAI&#8217;s Signing Pipeline. What Every Organisation Should Learn About Dependency Governance","author":"CPI Staff","date":"April 12, 2026","format":false,"excerpt":"When a North Korean state actor compromised the Axios npm package on March 31, 2026, the blast radius did not stop at developer laptops. It reached OpenAI's macOS code-signing pipeline \u2014 the system that certifies ChatGPT Desktop, Codex, Codex CLI, and Atlas as legitimate OpenAI software. If a supply chain\u2026","rel":"","context":"In &quot;AI Governance &amp; Risk Management&quot;","block_context":{"text":"AI Governance &amp; Risk Management","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/ai-governance-risk-management\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2026\/04\/axios-supply-chain-attack-openai-dependency-governance-cover.png","width":350,"height":200,"srcset":"\/wp-content\/uploads\/2026\/04\/axios-supply-chain-attack-openai-dependency-governance-cover.png 1x, \/wp-content\/uploads\/2026\/04\/axios-supply-chain-attack-openai-dependency-governance-cover.png 1.5x, \/wp-content\/uploads\/2026\/04\/axios-supply-chain-attack-openai-dependency-governance-cover.png 2x, \/wp-content\/uploads\/2026\/04\/axios-supply-chain-attack-openai-dependency-governance-cover.png 3x, \/wp-content\/uploads\/2026\/04\/axios-supply-chain-attack-openai-dependency-governance-cover.png 4x"},"classes":[]},{"id":53079,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2025\/01\/28\/running-c-net-applications-in-azure-devops-pipelines\/","url_meta":{"origin":57598,"position":1},"title":"Running C# .NET Applications in Azure DevOps Pipelines","author":"CPI Staff","date":"January 28, 2025","format":false,"excerpt":"In this blog post, I will show you how to build and run a C# application in Azure DevOps Pipelines. Estimated reading time: 3 minutes Table of contentsWhat Are Azure Pipelines?Step 1: Build the Console ApplicationStep 2: Create a YAML PipelineStep 3: Create a New PipelinePipeline Execution OverviewSummaryRelated Articles What\u2026","rel":"","context":"In &quot;.NET&quot;","block_context":{"text":".NET","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/net\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2025\/01\/Running-C-.NET-Applications-in-Azure-DevOps-Pipelines.webp","width":350,"height":200,"srcset":"\/wp-content\/uploads\/2025\/01\/Running-C-.NET-Applications-in-Azure-DevOps-Pipelines.webp 1x, \/wp-content\/uploads\/2025\/01\/Running-C-.NET-Applications-in-Azure-DevOps-Pipelines.webp 1.5x, \/wp-content\/uploads\/2025\/01\/Running-C-.NET-Applications-in-Azure-DevOps-Pipelines.webp 2x"},"classes":[]},{"id":57387,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/04\/02\/the-axios-npm-compromise-exposed-a-serious-gap-in-enterprise-dependency-governance\/","url_meta":{"origin":57598,"position":2},"title":"The Axios npm Compromise Exposed a Serious Gap in Enterprise Dependency Governance","author":"CPI Staff","date":"April 2, 2026","format":false,"excerpt":"Most organisations still treat dependency management as a developer hygiene issue. The Axios npm compromise shows that assumption is now dangerous. When two malicious Axios versions were published on March 31, 2026, the problem was not limited to a bad package update. According to Microsoft Threat Intelligence, axios@1.14.1 and axios@0.30.4\u2026","rel":"","context":"In &quot;Application Development&quot;","block_context":{"text":"Application Development","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/application-development\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2026\/04\/axios-npm-compromise-exposed-dependency-governance-cover.png","width":350,"height":200,"srcset":"\/wp-content\/uploads\/2026\/04\/axios-npm-compromise-exposed-dependency-governance-cover.png 1x, \/wp-content\/uploads\/2026\/04\/axios-npm-compromise-exposed-dependency-governance-cover.png 1.5x, \/wp-content\/uploads\/2026\/04\/axios-npm-compromise-exposed-dependency-governance-cover.png 2x, \/wp-content\/uploads\/2026\/04\/axios-npm-compromise-exposed-dependency-governance-cover.png 3x, \/wp-content\/uploads\/2026\/04\/axios-npm-compromise-exposed-dependency-governance-cover.png 4x"},"classes":[]},{"id":492,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2024\/08\/01\/automating-access-to-microsoft-graph-api-using-azure-pipelines\/","url_meta":{"origin":57598,"position":3},"title":"Automating Access to Microsoft Graph API Using Azure Pipelines","author":"CPI Staff","date":"August 1, 2024","format":false,"excerpt":"This Azure DevOps pipelines article will show how we automate access to Microsoft Graph API using Azure DevOps pipelines. Azure pipelines is an Azure DevOps service that allows us to automate the deployment of applications, services and changes to cloud environments. Microsoft Graph API is the underlining API service that\u2026","rel":"","context":"In &quot;Azure devOps&quot;","block_context":{"text":"Azure devOps","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/azure-devops\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2024\/08\/Automating-Access-to-Microsoft-Graph-Using-Azure-DevOps-Pipelines.webp","width":350,"height":200,"srcset":"\/wp-content\/uploads\/2024\/08\/Automating-Access-to-Microsoft-Graph-Using-Azure-DevOps-Pipelines.webp 1x, \/wp-content\/uploads\/2024\/08\/Automating-Access-to-Microsoft-Graph-Using-Azure-DevOps-Pipelines.webp 1.5x, \/wp-content\/uploads\/2024\/08\/Automating-Access-to-Microsoft-Graph-Using-Azure-DevOps-Pipelines.webp 2x, \/wp-content\/uploads\/2024\/08\/Automating-Access-to-Microsoft-Graph-Using-Azure-DevOps-Pipelines.webp 3x, \/wp-content\/uploads\/2024\/08\/Automating-Access-to-Microsoft-Graph-Using-Azure-DevOps-Pipelines.webp 4x"},"classes":[]},{"id":57068,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/02\/20\/the-real-security-risk-in-ai-coding-agents-for-claude-code-users\/","url_meta":{"origin":57598,"position":4},"title":"The Real Security Risk in AI Coding Agents for Claude Code Users","author":"CPI Staff","date":"February 20, 2026","format":false,"excerpt":"AI coding agents can quietly turn untrusted text into real actions. Here\u2019s what February\u2019s prompt-injection fallout teaches Claude Code users about reducing risk without killing productivity.","rel":"","context":"In &quot;AI Agents&quot;","block_context":{"text":"AI Agents","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/ai-agents\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2026\/02\/post-33.png","width":350,"height":200,"srcset":"\/wp-content\/uploads\/2026\/02\/post-33.png 1x, \/wp-content\/uploads\/2026\/02\/post-33.png 1.5x, \/wp-content\/uploads\/2026\/02\/post-33.png 2x, \/wp-content\/uploads\/2026\/02\/post-33.png 3x, \/wp-content\/uploads\/2026\/02\/post-33.png 4x"},"classes":[]},{"id":56798,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2025\/11\/26\/block-prompt-attacks-with-azure-ai-services\/","url_meta":{"origin":57598,"position":5},"title":"Block Prompt Attacks with Azure AI Services","author":"CPI Staff","date":"November 26, 2025","format":false,"excerpt":"Learn how to block prompt injection and jailbreak attacks using Azure AI, with practical patterns for safe, production-ready AI applications on Microsoft Azure.","rel":"","context":"In &quot;Azure AI Services&quot;","block_context":{"text":"Azure AI Services","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/azure-ai-services\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2025\/11\/block-prompt-attacks-with-azure-ai-in-real-world-apps.png","width":350,"height":200,"srcset":"\/wp-content\/uploads\/2025\/11\/block-prompt-attacks-with-azure-ai-in-real-world-apps.png 1x, \/wp-content\/uploads\/2025\/11\/block-prompt-attacks-with-azure-ai-in-real-world-apps.png 1.5x, \/wp-content\/uploads\/2025\/11\/block-prompt-attacks-with-azure-ai-in-real-world-apps.png 2x, \/wp-content\/uploads\/2025\/11\/block-prompt-attacks-with-azure-ai-in-real-world-apps.png 3x, \/wp-content\/uploads\/2025\/11\/block-prompt-attacks-with-azure-ai-in-real-world-apps.png 4x"},"classes":[]}],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/posts\/57598","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/comments?post=57598"}],"version-history":[{"count":1,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/posts\/57598\/revisions"}],"predecessor-version":[{"id":57599,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/posts\/57598\/revisions\/57599"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/media\/57600"}],"wp:attachment":[{"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/media?parent=57598"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/categories?post=57598"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/tags?post=57598"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}