Supply-chain attacks move fast. We stay ahead.

Free campaign tracking

Spectra Assure

Community

Toolbox

Explore

Learn

ReversingLabs

Spectra Assure

Community

VS Code

Search by package name, PURL or hash

warningRisk: Vulnerabilities

Scanned:

Claude Code for VS Code

Artifact:

latest

Top 100

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

License: unknown

New!

Published:

Publisher: anthropic

See on Visual Studio Code

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

1 debugging symbols found

Security

Vulnerabilities

1 high severity vulnerabilities

Hardening

1 baseline mitigations missing

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

Overview issues31 vulnerabilities4 malware0 behaviors395 dependencies0 contributors1 versions379

FAQ for Claude Code for VS Code

What is Claude Code for VS Code?

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE.

Is Claude Code for VS Code malicious or is it safe to use?

The VS Code package Claude Code for VS Code was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. The package contains risks, and the analysis results should be reviewed before it is downloaded and used. Visit the Issues and Behaviors sections of the analysis for more details.

Does Claude Code for VS Code have known vulnerabilities?

Yes, we detected 1 high severity vulnerability, and 4 vulnerabilities in total, including CVE-2026-86145, CVE-2026-89160, CVE-2026-27171 and more. Explore the Vulnerabilities tab for more information.

Is Claude Code for VS Code popular?

The VS Code package Claude Code for VS Code ranks among the top 100 projects in this community. It has 29M recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

Read our best practices for protecting your software supply chain guide.

Did you know...

... that you can use ReversingLabs’ Spectra Assure platform to perform regular risk assessments of packages you develop in-house?

We recommend continuous software safeness monitoring through CI/CD integrations and pre-release/deployment checks. In addition to basic package information found on this page our platform offers rich reports for developers and DevSecOps that help them remediate all reported issues.

Popularity

28.98M

Total Installs

Contributor

Declared Dependencies

Dependents

Top issues

See all issues

Problem

Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as high severity.

Prevalence in Visual Studio Code community

77 packages

found in

Top 100

623 packages

found in

Top 1k

3795 packages

found in

Top 10k

29.26k packages

in community

Next steps

Perform impact analysis for the reported CVEs.

Update the component to the latest version.

If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Problem

Operating systems execute application code in multiple privilege access levels. Separation of privileges is designed to protect the stability and integrity of the operating system by shielding it from issues that the user run applications may cause. However, some users may need to interact with higher privilege parts of the operating system to accomplish specific tasks. For this purpose, operating systems provide facilities that users may leverage to temporarily elevate their running privileges. Users with higher privileges can run any application with the same privilege level as their own. Attackers often try to trick privileged users into running malicious code, enabling them to infect the operating system. While the presence of code that elevates user privileges does not necessarily imply malicious intent, all of its uses in a software package should be documented and approved. Only select applications should consider using functions that can elevate user privileges. One example of acceptable use for such functions is allowing the users to install software packages and updates.

Prevalence in Visual Studio Code community

39 packages

found in

Top 100

195 packages

found in

Top 1k

529 packages

found in

Top 10k

2.63k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1548 - Abuse Elevation Control Mechanism.

Consider rewriting the flagged code without using the marked behaviors.

Problem

Software components are typically distributed in standardized packaging formats. Software packages are built from instructions written within package manifests that act as blueprints for package assembly. A package manifest declares the most important software properties, such as the package name, its authors and license, external dependencies, and various actions that may occur during the package lifecycle. Package managers are specialized tools used by developers to manage software components. Package managers read these manifests to deploy software components along with their dependencies. The premise of the package management system is that software components are isolated from each other, and that they rely on the package manager to provide their dependencies. However, it was detected that a software component includes code capable of accessing or modifying directories that are maintained exclusively by package managers. This is unusual as it resembles tactics used by threat actors that tamper with installed software components and inject malicious code into trusted execution paths.

Prevalence in Visual Studio Code community

79 packages

found in

Top 100

540 packages

found in

Top 1k

3333 packages

found in

Top 10k

24.83k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1554 - Compromise Host Software Binary.

Consider rewriting the flagged code without using the marked behaviors.

Problem

Software components sometimes need to interact with sensitive parts of the runtime environment, often requiring privileged access to accomplish a task. Cloud workload configuration includes high-value information such as cloud provider credentials, environment variables containing secrets, and configuration files used by cloud and container orchestration tools. That information is used by applications running in cloud and containerized environments. Attackers often abuse access to cloud workload configuration to harvest secrets from developer machines and build environments, which can later be exfiltrated to attacker-controlled infrastructure and used to gain unauthorized access to cloud resources. While the presence of code that accesses cloud workload configuration does not necessarily imply malicious intent, all of its uses in a software package should be documented and approved. Only select software components should consider using functions that read cloud workload configuration. One example of acceptable use for such functions is infrastructure-as-code tooling that legitimately needs to read credentials to provision or manage cloud resources on behalf of the developer.

Prevalence in Visual Studio Code community

16 packages

found in

Top 100

103 packages

found in

Top 1k

299 packages

found in

Top 10k

2.27k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1580 - Cloud Infrastructure Discovery.

Consider rewriting the flagged code without using the marked behaviors.

Problem

Software components sometimes need to interact with sensitive parts of the runtime environment, often requiring privileged access to accomplish a task. Build pipeline configuration includes high-value information such as CI/CD platform secrets and tokens, pipeline definition files and runner configuration, build-time environment variables containing signing keys or deploy credentials, and artifact registry and package publishing credentials. That information is used by continuous integration and delivery systems. Attackers often abuse access to build pipeline configuration to harvest secrets from build environments, which can later be exfiltrated to attacker-controlled infrastructure and used to tamper with software releases or publish malicious artifacts under trusted identities. While the presence of code that accesses build pipeline configuration does not necessarily imply malicious intent, all of its uses in a software package should be documented and approved. Only select software components should consider using functions that read build pipeline configuration. One example of acceptable use for such functions is release tooling that reads publishing credentials to push artifacts.

Prevalence in Visual Studio Code community

22 packages

found in

Top 100

95 packages

found in

Top 1k

593 packages

found in

Top 10k

3.74k packages

in community

Next steps

Claude Code for VS Code

SAFE Assessment

Compliance

Security

Threats

FAQ for Claude Code for VS Code

What is Claude Code for VS Code?

Is Claude Code for VS Code malicious or is it safe to use?

Does Claude Code for VS Code have known vulnerabilities?

Is Claude Code for VS Code popular?

Did you know...

Popularity

Top issues

SQ31105Detected presence of high severity vulnerabilities.Causes risk: high severity vulnerabilitiesvulnerabilities

Problem

Prevalence in Visual Studio Code community

Next steps

TH16120Detected presence of software components that can elevate the user privileges.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH16129Detected presence of software components that can tamper with other installed software.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH16130Detected presence of software components that can access sensitive cloud workload configuration.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH16131Detected presence of software components that can access sensitive build pipeline configuration.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

Top behaviors

Accesses system passwords.steal

Prevalence in Visual Studio Code community

Grants privileges to users on the local computer.permissions

Prevalence in Visual Studio Code community

Reads from version control configuration files.steal

Prevalence in Visual Studio Code community

Reads from sensitive Microsoft Teams files.steal

Prevalence in Visual Studio Code community

Reads from infrastructure as code (IaC) provider configuration files.steal

Prevalence in Visual Studio Code community

Top vulnerabilities