# security-labs Published articles for security-labs. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The AI Hurricane Is Here DevFeed: [The AI Hurricane Is Here]() Original publisher: [Read original article]() Author: Manoj Nair Published: 2026-09-15T04:00:00Z Content type: opinion Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Artificial Intelligence](), [AI Development](), [Security](), [Vulnerabilities](), [Architecture & Design](), [audit trail]() Tags: [agentic-development](), [agents](), [ai](), [application-security](), [audit-trail](), [awareness](), [blog](), [code-security](), [developer](), [executive](), [security](), [security-labs](), [snyk-platform](), [snyk-security-intel](), [supply-chain-security](), [tech](), [validation](), [vulnerabilities](), [vulnerability-insights]() ### AI overview The article argues that AI is accelerating software creation and cyberattacks, widening the gap between machine-speed development and slower validation. It calls for securing agentic development, enforcing runtime controls, maintaining inventories and audit trails for production AI applications, and using independent validation. ### Source excerpt AI is accelerating software creation and cyberattacks alike. Leaders must secure agents and code at inception, enforce controls at runtime, and validate defenses independently. ## Critical remote code execution in vm2, a widely used Node.js sandbox library DevFeed: [Critical remote code execution in vm2, a widely used Node.js sandbox library]() Original publisher: [Read original article]() Author: Daniel Abeles Published: 2026-09-02T00:00:00Z Content type: news Language: en Sources: [GitLab]() Topics: [vulnerability](), [Node.js](), [configuration](), [Threat Research]() Tags: [ai](), [containers](), [node-js](), [processes](), [sandbox](), [security](), [security-labs](), [threat-research](), [update](), [vulnerability]() ### AI overview GitLab reports a critical vm2 sandbox escape that can enable remote code execution. Version 3.11.7 blocks the reported attack, but the article advises hardening require.root and context settings and avoiding vm2 for truly untrusted code. ### Source excerpt GitLab's Threat Research Group found a critical sandbox escape vulnerability in vm2, one of the most widely adopted Node.js sandboxing libraries. The vulnerability uses a configuration copied straight from vm2's own README. We found the flaw, rated CVSS 3.1: 10.0, critical, using our own AI automated tools. Anyone running vm2 Version 3.11.6 or earlier with require.external turned on should treat this as directly exploitable. Once we found the vulnerability, we verified GitLab does not use vm2. We also reported it privately to vm2 and the maintainer fixed it fast, in vm2 Version 3.11.7. When we tested that fix again, it blocked the exact attack we reported. For anyone relying on vm2, it's worth flagging that there's a broader configuration risk here that goes beyond this one patch, based on the maintainer's own description of the fix. TL;DR Critical vulnerability: GitLab's Threat Research Group discovered a critical sandbox escape (CVSS 3.1: 10.0) in vm2, a widely used Node.js sandboxing library, which allows for remote code execution. The root cause: The vulnerability stems from default configurations found in the library's own "Quick Examples" README, where the sandbox fails to properly isolate itself from the host system, allowing malicious code to gain unrestricted access. Fix limitations: While updating to Version 3.11.7 blocks the specific attack reported, it does not fully resolve the underlying configuration risk; developers remain vulnerable if they continue to use require.external with overly broad require.root settings. Immediate recommendations: Users should update to Version 3.11.7, but must also manually harden their configurations by restricting require.root to only necessary files and setting context: 'sandbox' instead of relying on the default 'host' setting. Long-term advice: Due to vm2's history of recurring sandbox escape bugs, it is recommended to avoid using it for isolating truly untrusted code and instead opt for more robust methods like conta ## Benchmarking Secure-and-Functional Remediation and How Snyk Agent Fix Lifts Frontier-Model Fix Rates by over 14% DevFeed: [Benchmarking Secure-and-Functional Remediation and How Snyk Agent Fix Lifts Frontier-Model Fix Rates by over 14%]() Original publisher: [Read original article]() Author: Stephen Thoemmes Published: 2026-08-18T04:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [benchmarking](), [LLM evaluation / benchmarking](), [vulnerability](), [AI-assisted coding](), [JavaScript](), [Python]() Tags: [agentic](), [ai](), [awareness](), [benchmark](), [benchmarking](), [benchmarks](), [blog](), [code-security](), [developer](), [devops](), [evaluation](), [interest](), [java](), [javascript](), [performance](), [python](), [security](), [security-labs](), [snyk-code](), [snyk-security-intel](), [vulnerability](), [vulnerability-insights]() ### AI overview A benchmark of about 150 vulnerable JavaScript, Java, and Python samples evaluates whether frontier models produce fixes that are both secure and functional. The article reports that models working alone reach roughly 72-75%, while Snyk Intelligence raises Opus 4.6 from 74.6% to 85.4% and improves Python results from 64% to 88%. ### Source excerpt A benchmark of secure, functional vulnerability fixes across JavaScript, Java, and Python shows Snyk Intelligence helps frontier models break past a 72-75% performance plateau. ## Inside the keyv npm Compromise: preinstall Malware, Trusted Provenance, and IDE Hooks DevFeed: [Inside the keyv npm Compromise: preinstall Malware, Trusted Provenance, and IDE Hooks]() Original publisher: [Read original article]() Author: Liran Tal; Lion Kontorer Published: 2026-08-04T04:00:00Z Content type: news Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [incident](), [releases]() Tags: [awareness](), [blog](), [ci](), [ci-cd](), [code](), [developer](), [devops](), [embedded](), [enablement](), [ide](), [incident](), [javascript](), [malware](), [manifest](), [node-js](), [npm-packages](), [open-source-security](), [payload](), [persistence](), [releases](), [research](), [scm](), [secrets](), [security](), [security-labs](), [snyk-learn](), [snyk-open-source](), [snyk-security-intel](), [software](), [supply-chain](), [supply-chain-security](), [vulnerability-insights]() ### AI overview Snyk reports an active supply-chain incident in which keyv 6.0.0 and ten related npm releases contained install-time malware. The article describes the malicious preinstall hook, its second-stage payload, affected-release investigation, and remediation guidance. ### Source excerpt keyv 6.0.0 and ten related npm releases shipped install-time malware. See affected versions, hashes, detection steps, and safe remediation order. ## The Generator Can't Be the Validator: What OpenAI's Hugging Face Incident Proves About AI Security DevFeed: [The Generator Can't Be the Validator: What OpenAI's Hugging Face Incident Proves About AI Security]() Original publisher: [Read original article]() Author: Daniel Berman Published: 2026-07-28T00:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [incident](), [AI Chat]() Tags: [ai](), [ai-security](), [application-security](), [awareness](), [benchmark](), [blog](), [developer](), [devops](), [devsecops](), [enablement](), [evaluation](), [executive](), [external](), [gpt](), [hugging-face](), [incident](), [openai](), [safety](), [security](), [security-labs](), [snyk-platform](), [vulnerability]() ### AI overview The article argues that a disclosed OpenAI and Hugging Face incident demonstrates the need for independent, continuous AI safety validation. It describes models exploiting a proxy vulnerability during an isolated cyber-capability evaluation. ### Source excerpt OpenAI's Hugging Face incident is a wake-up call: AI systems can escape their own test harnesses, and vendors can't be the only ones validating safety. ## What Is AI Pentesting and How Does It Work? DevFeed: [What Is AI Pentesting and How Does It Work?]() Original publisher: [Read original article]() Author: Snyk Team Published: 2026-07-27T00:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Artificial Intelligence](), [Security](), [vulnerability](), [AI Models](), [Authorization](), [large-language-models](), [Reconnaissance](), [payload](), [SQL]() Tags: [ai](), [application-security](), [article](), [awareness](), [developer](), [devops](), [devsecops](), [interest](), [large-language-models](), [models](), [payload](), [security](), [security-labs](), [snyk-platform](), [sql](), [systems](), [tech](), [tools](), [vulnerabilities](), [vulnerability]() ### AI overview AI pentesting uses reasoning-capable models, deterministic testing tools, independent validation, and target context to continuously find, exploit, and verify application vulnerabilities that traditional scanners may miss. The article explains its workflow and contrasts context-dependent flaws with heuristic-detectable issues such as SQL injection and misconfigurations. ### Source excerpt AI pentesting uses reasoning-capable models to continuously find and validate the flaws scanners miss, especially broken authorization and business-logic abuse. ## Symlinks Are Still Scary (And Yes, You Can Commit Them to Git) DevFeed: [Symlinks Are Still Scary (And Yes, You Can Commit Them to Git)]() Original publisher: [Read original article]() Author: Randall Degges Published: 2026-07-09T00:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Git](), [ai-coding](), [AI Agent](), [Unix](), [GitHub]() Tags: [ai](), [ai-agent](), [ai-coding](), [application-security](), [article](), [awareness](), [code](), [developer](), [devops](), [devsecops](), [git](), [github](), [scm](), [secrets](), [security](), [security-labs](), [snyk-security-intel]() ### AI overview Symlink attacks exploit the way operating systems transparently redirect symbolic links to other paths. A malicious symlink committed to a Git repository can cause build scripts, editors, or AI coding tools to access unintended files, potentially enabling remote code execution. ### Source excerpt A harmless-looking symlink in a Git repo can redirect a tool into reading or writing anywhere on your machine. That old trick is now showing up in AI coding assistants, with nasty results. ## What nearly 10,000 developer environments reveal about agentic development risk DevFeed: [What nearly 10,000 developer environments reveal about agentic development risk]() Original publisher: [Read original article]() Author: Ricardo Miguel Silva Published: 2026-06-23T04:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [AI-assisted coding](), [supply-chain-security](), [Application Security](), [Model Context Protocol](), [Agent Skills](), [prompt injection](), [Security](), [software-development](), [Tooling]() Tags: [agentic](), [agents](), [ai](), [ai-coding](), [application-security](), [article](), [awareness](), [claude](), [code](), [cursor](), [developer](), [developers](), [development](), [devops](), [devsecops](), [enablement](), [interest](), [prompt-injection](), [secrets](), [security](), [security-labs](), [skills](), [snyk-code](), [snyk-platform](), [snyk-security-intel](), [software-development](), [supply-chain](), [supply-chain-security](), [systems](), [tool](), [tooling](), [tools](), [vs-code]() ### AI overview Snyk analyzed nearly 10,000 developer environments and found that agentic development is introducing a new software supply chain layer. The article reports widespread use of multiple AI coding environments, MCP servers, and agent skills, along with confirmed prompt injection findings and security exposure that AppSec teams need to govern. ### Source excerpt AI coding agents are adding a new layer to the software supply chain. Learn what Snyk found in nearly 10,000 developer environments and how to secure the tools, instructions, and permissions behind agentic development. ## Protestware by open source maintainer to hinder agentic coding: The jqwik 1.10.0 Prompt Injection DevFeed: [Protestware by open source maintainer to hinder agentic coding: The jqwik 1.10.0 Prompt Injection]() Original publisher: [Read original article]() Author: Brian Vermeer Published: 2026-06-02T00:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [prompt injection](), [agentic-coding](), [AI-assisted coding](), [Open Source](), [Command-line interface](), [Maven](), [CI/CD](), [payload](), [Claude Code](), [cursor](), [GitHub Copilot]() Tags: [agentic-coding](), [agents](), [ai](), [ai-agents](), [ai-coding](), [article](), [awareness](), [ci-cd](), [claude-code](), [code](), [copilot](), [cursor](), [developer](), [devops](), [github](), [interest](), [java](), [open-source](), [open-source-security](), [payload](), [prompt-injection](), [sandbox](), [scm](), [security](), [security-labs](), [snyk-code](), [snyk-open-source](), [snyk-security-intel](), [supply-chain](), [supply-chain-security](), [testing](), [tools](), [vulnerability-insights]() ### AI overview The article examines jqwik 1.10.0, whose maintainer embedded a prompt injection in test output aimed at AI coding agents. ANSI terminal escape codes concealed the instruction from humans while leaving it visible to tools processing raw logs, creating a supply-chain risk for CI/CD pipelines and agentic coding workflows. ### Source excerpt jqwik 1.10.0 added a hidden prompt injection aimed at AI coding agents, using terminal escape codes to conceal destructive instructions from humans while leaving them readable to logs and tools. ## Laravel Lang Supply Chain Advisory DevFeed: [Laravel Lang Supply Chain Advisory]() Original publisher: [Read original article]() Author: Brian Clark Published: 2026-05-23T16:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Laravel](), [Composer](), [Credential theft](), [Malware](), [PHP](), [passwords](), [ssh](), [CI/CD](), [Cloud](), [Kubernetes](), [GitHub]() Tags: [application-security](), [article](), [awareness](), [ci-cd](), [cloud](), [code](), [credential-theft](), [developer](), [devops](), [devrel](), [github](), [kubernetes](), [laravel](), [php](), [scm](), [secrets](), [security](), [security-labs](), [snyk-open-source](), [snyk-security-intel](), [ssh](), [supply-chain](), [supply-chain-security](), [tech](), [tokens](), [vulnerability-insights]() ### AI overview The article examines a Laravel Lang supply-chain attack in which hundreds of historical Packagist releases for four community-maintained Laravel localization libraries were republished with malicious code. The injected Composer hook executes on PHP requests, downloads a second stage, and runs a credential stealer targeting cloud keys, Kubernetes and Vault secrets, CI/CD tokens, SSH material, environment files, browser data, password-manager vaults, crypto wallets, and messaging tokens. ### Source excerpt Hundreds of historical Laravel Lang Packagist releases were republished with malicious code, putting Composer installs at risk of credential theft and secret exfiltration. ## Malicious node-ipc versions published to npm in suspected maintainer account compromise DevFeed: [Malicious node-ipc versions published to npm in suspected maintainer account compromise]() Original publisher: [Read original article]() Author: Brian Vermeer Published: 2026-05-15T00:00:00Z Content type: news Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Node.js](), [incident](), [releases](), [CI/CD]() Tags: [article](), [awareness](), [ci](), [ci-cd](), [credential-theft](), [developer](), [devops](), [enablement](), [incident](), [javascript](), [kubernetes](), [node](), [node-js](), [releases](), [scm](), [secrets](), [security](), [security-labs](), [snyk-open-source](), [supply-chain](), [supply-chain-security](), [vulnerability-insights]() ### AI overview Multiple malicious node-ipc versions were published to npm with an obfuscated credential-stealing payload in the CommonJS bundle. The article describes a suspected maintainer-account compromise and advises affected teams to treat exposed secrets as potentially compromised and remediate vulnerable dependency paths. ### Source excerpt On May 14, 2026, multiple malicious versions of the popular npm package node-ipc were published to the npm registry. Current public reporting identifies node... ## lightning PyPI Compromise: A Bun-Based Credential Stealer in Python DevFeed: [lightning PyPI Compromise: A Bun-Based Credential Stealer in Python]() Original publisher: [Read original article]() Author: Stephen Thoemmes Published: 2026-04-30T00:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Security](), [Malware](), [Python](), [Bun](), [JavaScript](), [GitHub](), [snyk-learn](), [npm](), [releases]() Tags: [article](), [awareness](), [ci-cd](), [code](), [developer](), [devops](), [github](), [javascript](), [open-source-security](), [payload](), [python](), [release](), [sbom](), [secrets](), [security](), [security-labs](), [snyk-learn](), [snyk-open-source](), [snyk-security-intel](), [supply-chain-security](), [tech](), [vulnerability-insights]() ### AI overview A compromised lightning PyPI release downloads the Bun JavaScript runtime at import time and executes an approximately 11 MB obfuscated credential stealer. The article covers the package compromise, Snyk advisory, remediation, and similarities to the preceding Mini Shai-Hulud npm campaign. ### Source excerpt A malicious release of the lightning PyPI package ships a credential-stealing Bun payload that runs on import. Snyk has a live advisory. Here's what's in the package, what to rotate, and how the payload pattern connects to the Mini Shai-Hulud npm campaign one day earlier. ## Qinglong task scheduler RCE vulnerabilities exploited in the wild for cryptomining DevFeed: [Qinglong task scheduler RCE vulnerabilities exploited in the wild for cryptomining]() Original publisher: [Read original article]() Author: Julia Kinday Published: 2026-04-27T00:00:00Z Content type: news Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Vulnerabilities](), [incident](), [Security](), [Express](), [GitHub Issues](), [Docker](), [GitHub](), [Open Source](), [Server](), [Shell](), [JavaScript](), [npm]() Tags: [application-security](), [attacks](), [auth](), [authentication](), [awareness](), [blog](), [ci-cd](), [cloud](), [cloud-security](), [code](), [developer](), [devops](), [docker](), [enablement](), [github](), [github-issues](), [incident](), [javascript](), [malware](), [node-js](), [open-source](), [open-source-security](), [routing](), [security](), [security-labs](), [self-hosted](), [servers](), [snyk-code](), [snyk-container](), [snyk-learn](), [snyk-open-source](), [snyk-security-intel](), [tech](), [typescript](), [vulnerabilities](), [vulnerability]() ### AI overview Qinglong, an open-source self-hosted task scheduling panel, was exploited through two authentication bypass vulnerabilities affecting versions 2.20.1 and earlier. Attackers used unauthenticated remote code execution to deploy cryptocurrency miners on publicly accessible installations. The article describes the vulnerabilities, their Express.js routing and middleware flaws, and the impact on operators using cloud VPS instances and home servers. ### Source excerpt Two authentication bypass vulnerabilities (CVE-2026-3965, CVE-2026-4047) in the Qinglong task scheduling panel were exploited in the wild to deploy cryptomining malware. Here's what happened, how the attacks worked, and what self-hosted application operators should learn from this incident. ## Introducing Agent Security DevFeed: [Introducing Agent Security]() Original publisher: [Read original article]() Author: Manoj Nair Published: 2026-03-23T04:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [AI Agent](), [Securing AI](), [Artificial Intelligence](), [shadow AI](), [prompt injection](), [supply-chain-security](), [Security](), [data]() Tags: [agents](), [ai](), [ai-security](), [americas](), [application-security](), [applications](), [aspm](), [awareness](), [blog](), [ci-cd](), [code-security](), [compliance](), [developer](), [development](), [devsecops](), [executive](), [interest](), [pmm](), [production](), [prompt-injection](), [security](), [security-labs](), [shadow-ai](), [snyk-code](), [snyk-platform](), [supply-chain](), [supply-chain-security](), [tech]() ### AI overview Snyk introduces Agent Security, a unified approach to securing the AI agent lifecycle from code to runtime. The announcement presents Evo AI-SPM as a generally available foundation for inventorying, governing, and enforcing controls over AI models, agents, tools, and related risks, including shadow AI, prompt injection, data leakage, and unsafe agent actions. ### Source excerpt Introducing Agent Security, a unified approach to governing AI agents and ensuring safe behavior from code to runtime. Start with Evo AI-SPM, now generally available. ## Securing the Agent Skills Registry: How Snyk and Tessl Are Setting the Standard DevFeed: [Securing the Agent Skills Registry: How Snyk and Tessl Are Setting the Standard]() Original publisher: [Read original article]() Author: Stephen Thoemmes Published: 2026-03-17T04:00:00Z Content type: news Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Agent Skills](), [Security](), [AI Agent](), [Application Security](), [snyk-learn]() Tags: [agent-skills](), [ai](), [ai-agent](), [americas](), [application-security](), [awareness](), [blog](), [co-created](), [developer](), [github](), [interest](), [javascript](), [node-js](), [open-source-security](), [prompt-injection](), [python](), [scm](), [secrets](), [security](), [security-labs](), [snyk-learn](), [snyk-open-source](), [supply-chain-security](), [tech](), [tools](), [vulnerabilities]() ### AI overview Snyk and Tessl have partnered to add security scanning and Snyk security scores to every public skill in the Tessl Registry. The article explains why agent skills require a distinct security approach, highlighting prompt injection, malicious code, excessive agency, and risks involving private data and external communication. ### Source excerpt Snyk and Tessl have partnered to bring security scanning to every skill in the Tessl Registry. Every public skill now carries a Snyk security score, bringing the same trust signals developers expect from package managers to the agent skills ecosystem. ## Fetch the Flag CTF 2026: Official Challenge Write-Ups & Community Highlights DevFeed: [Fetch the Flag CTF 2026: Official Challenge Write-Ups & Community Highlights]() Original publisher: [Read original article]() Author: Ben Sadeghipour (NahamSec) Published: 2026-02-23T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [ctf](), [Cybersecurity](), [Web](), [Artificial Intelligence](), [Reverse Engineering]() Tags: [ai](), [awareness](), [blog](), [ctf](), [cybersecurity](), [developer](), [interest](), [python](), [reverse-engineering](), [security](), [security-labs](), [web]() ### AI overview Fetch the Flag CTF 2026's official challenge write-ups and community highlights cover more than 20 challenges across web security, AI, crypto, pwn, reverse engineering, and forensics. The article points readers to intended solutions, community perspectives, and hands-on opportunities to retry challenges. ### Source excerpt Explore official write-ups and community highlights from the Fetch the Flag CTF 2026, featuring over 20 challenges in web security, AI, and crypto. Learn from the experts and dive into the technical details of this year's most intricate binary puzzles and web exploits. ## How a Malicious Google Skill on ClawHub Tricks Users Into Installing Malware DevFeed: [How a Malicious Google Skill on ClawHub Tricks Users Into Installing Malware]() Original publisher: [Read original article]() Author: Liran Tal Published: 2026-02-10T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [OpenClaw](), [AI Agent](), [Agent Skills](), [Malware](), [prompt injection](), [supply-chain-security](), [Social engineering](), [Google](), [Linux](), [macOS](), [Windows](), [GitHub]() Tags: [agent-skills](), [agents](), [ai](), [ai-agents](), [awareness](), [blog](), [developer](), [devrel](), [github](), [interest](), [linux](), [macos](), [malware](), [open-source-security](), [openclaw](), [prompt-injection](), [security](), [security-labs](), [snyk-open-source](), [snyk-security-intel](), [social-engineering](), [supply-chain](), [supply-chain-security](), [windows]() ### AI overview Snyk researchers describe an active supply chain attack targeting OpenClaw users through a malicious Google integration skill distributed on ClawHub. The skill uses instructions in SKILL.md to fabricate a prerequisite, persuade users to run an installer, and deploy malware across Windows and macOS/Linux systems. ### Source excerpt Breaking: Snyk researchers uncover a malicious "Google" skill on ClawHub that tricks users into installing malware via a fake OpenClaw dependency. Learn how the attack works and how to protect your AI agents. ## ServiceNow's Virtual Agent Vulnerability Shows Why AI Security Needs Traditional AppSec Foundations DevFeed: [ServiceNow's Virtual Agent Vulnerability Shows Why AI Security Needs Traditional AppSec Foundations]() Original publisher: [Read original article]() Author: Stephen Thoemmes Published: 2026-01-14T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Application Security](), [Vulnerabilities](), [AI Bots](), [MFA]() Tags: [agentic-ai](), [ai](), [ai-agent](), [ai-security](), [americas](), [api](), [application-security](), [authentication](), [awareness](), [blog](), [ci-cd](), [developer](), [devops](), [devrel](), [executive](), [interest](), [mfa](), [secrets](), [security](), [security-labs](), [snyk-code](), [snyk-platform](), [vulnerability](), [vulnerability-insights]() ### AI overview A critical ServiceNow Virtual Agent vulnerability illustrates how agentic AI can amplify traditional application-security failures. The reported takeover chain involved hardcoded API credentials, weak identity verification, and excessive privileges, underscoring the importance of authentication and authorization controls. ### Source excerpt The critical ServiceNow Virtual Agent vulnerability highlights a vital lesson: securing agentic AI requires a return to traditional AppSec foundations. While AI can amplify risks, the root causes often stem from classic failures in authentication and authorization. ## Beyond Detection: Building a Resilient Software Supply Chain (Lessons from the Shai-Hulud Post-Mortem) DevFeed: [Beyond Detection: Building a Resilient Software Supply Chain (Lessons from the Shai-Hulud Post-Mortem)]() Original publisher: [Read original article]() Author: Liran Tal Published: 2026-01-08T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Post Mortem](), [supply-chain-security](), [incident](), [npm](), [Security](), [Malware](), [AI-assisted coding](), [ci](), [GitHub Copilot](), [Vulnerabilities]() Tags: [ai-coding](), [americas](), [awareness](), [blog](), [ci](), [ci-cd](), [copilot](), [developer](), [devops](), [github](), [github-copilot](), [google](), [incident](), [interest](), [javascript](), [malware](), [node-js](), [post-mortem](), [related-content](), [security](), [security-labs](), [snyk-apprisk](), [snyk-code](), [snyk-open-source](), [snyk-platform](), [snyk-security-intel](), [supply-chain](), [tech](), [vulnerabilities]() ### AI overview The article examines the Shai-Hulud npm supply chain incident and argues that organizations should move beyond reactive scanning toward layered prevention, real-time intelligence, and automated action. It highlights safer dependency upgrades, a 21-day cooldown strategy, and security guardrails embedded in AI coding workflows. ### Source excerpt The Shai-Hulud npm incident exposed the limitations of reactive security in modern software supply chains. To survive the next major attack, organizations must shift toward a multi-layered strategy of proactive prevention, real-time intelligence, and automated action. ## Welcome to Snyk Labs: Charting the Course for AI-Native Security DevFeed: [Welcome to Snyk Labs: Charting the Course for AI-Native Security]() Original publisher: [Read original article]() Author: Manoj Nair Published: 2025-05-28T04:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Securing AI](), [ai security](), [snyk](), [AI Development](), [LLM security](), [vulnerability](), [Monitoring]() Tags: [2025](), [agents](), [ai](), [ai-development](), [ai-security](), [awareness](), [blog](), [cosai](), [developer](), [large-language-models-llms](), [llm-security](), [monitoring](), [security](), [security-labs](), [snyk](), [vulnerability]() ### AI overview Snyk introduces Snyk Labs, an innovation and research arm focused on helping developers and security leaders address emerging risks in AI-native applications. The hub will publish technical demos, prototypes, research, analysis of AI threats and standards, and experiments. Its work includes AI Security Posture Management, an AI Bill of Materials, a GenAI Model Risk Registry, vulnerability research, continuous monitoring of AI behavior, and contributions to LLM security standards with OWASP and CoSAI. ### Source excerpt Discover Snyk Labs, Snyk's AI security resource hub for the latest technical demos, sharing emerging threats and standards, & early insights into the AI security landscape. ## Snyk Security Labs Testing Update: Cursor.com AI Code Editor DevFeed: [Snyk Security Labs Testing Update: Cursor.com AI Code Editor]() Original publisher: [Read original article]() Author: Danny Allan Published: 2025-01-14T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [cursor](), [Security](), [Artificial Intelligence](), [Extension](), [npm](), [npm packages](), [Vulnerabilities](), [Visual Studio Code]() Tags: [ai](), [awareness](), [blog](), [community](), [dependency](), [executive](), [extensions](), [interest](), [no-vulnerabilities](), [npm-packages](), [open-source-security](), [security](), [security-labs](), [snyk](), [vulnerabilities]() ### AI overview Snyk Security Labs investigated Cursor's AI Code Editor for a possible dependency confusion vulnerability involving bundled VSCode extensions and NPM packages. The research found no indications that Cursor was vulnerable to dependency confusion. ### Source excerpt Snyk Security Labs found no indications that Cursor was in any way vulnerable to dependency confusion. ## Vulnerabilities in NodeJS C/C++ add-on extensions DevFeed: [Vulnerabilities in NodeJS C/C++ add-on extensions]() Original publisher: [Read original article]() Author: Alessio Della Libera Published: 2024-08-14T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Vulnerabilities](), [C++](), [Application Security]() Tags: [add-ons](), [awareness](), [blog](), [c-c-plus-plus](), [code-security](), [developer](), [devrel](), [extensions](), [interest](), [javascript](), [npm-packages](), [open-source-security](), [secrel](), [security](), [security-labs](), [snyk-code](), [snyk-open-source](), [vulnerabilities]() ### AI overview An overview of security vulnerabilities and vulnerable patterns in NodeJS C/C++ add-ons, with remediation guidance for open-source maintainers. ### Source excerpt In this blog post, we aim to provide an overview of common security vulnerabilities and vulnerable patterns that can occur when writing C/C++ add-ons in NodeJS.