Spectra Assure

failRisk: Tampering

Scanned:

Fira Code and Material Icon Theme

Artifact:

latest

Top 10k

Fira Code Font and Material Design Icons for Visual Studio Code

License: unknown

Published:

Publisher: aleleba

Visit GitHub

See on Visual Studio Code

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

No known vulnerabilities detected

Hardening

No application hardening issues

Threats

Tampering

1 dangerous develop extensions

Malware

No evidence of malware inclusion

Overview issues5 vulnerabilities0 malware0 behaviors56 dependencies1 contributors1 versions3

Popularity

17.33k

Total Installs

Contributor

Declared Dependencies

Dependents

Top issues

See all issues

Problem

Development extensions are commonly used by software developers to extend the functionality of integrated development environments, code editors, and other developer tools. Extensions are typically distributed through public marketplaces as packages that bundle the extension code with supporting resources. Development extension code implements behaviors that integrate it with the host application. This integration allows extensions to register commands, react to editor events, or provide programming language support. Extension code is loaded and executed automatically by the host application during events such as editor startup, file opening, or user interaction. These events are used by extension developers to set up the environment for nominal extension use, or to respond to activity within the host application. It is unusual for certain types of development extensions to execute commands that can collect sensitive system information. Attackers often abuse development extensions to run commands that collect identifiable system information such as hostnames, user names, folder structures, and other data points that could help them understand the environment in which their malicious code was loaded.

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Investigate reported detections.

Consult Mitre ATT&CK documentation: T1176.002 - Software Extensions: IDE Extensions.

If the development extension intent does not relate to the reported behavior, investigate your development environment for software supply chain compromise.

You should stop using the development extension until the investigation is completed, or until the issue is risk accepted.

Consider replacing the development extension with an alternative.

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

No prevalence information at this time

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

No prevalence information at this time

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

No prevalence information at this time

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1072 - Software Deployment Tools.

Consider rewriting the flagged code without using the marked behaviors.

Problem

Uniform Resource Locators (URLs) are structured addresses that point to locations and assets on the internet. URLs allow software developers to build complex applications that exchange data with servers that can be hosted in multiple geographical regions. URLs can commonly be found embedded in documentation, configuration files, source code and compiled binaries. One or more embedded URLs were discovered to link to raw files hosted on GitHub. Attackers often abuse popular web services to host malicious payloads. Since code-sharing service URLs are typically allowed by security solutions, using them for payload delivery increases the odds that the malicious code will reach the user. While the presence of code-sharing service locations does not imply malicious intent, all of their uses in a software package should be documented and approved. An increasing number of software supply chain attacks in the open source space leverage the GitHub service to deliver malicious payloads.

Prevalence in Visual Studio Code community

79 packages

found in

Top 100

622 packages

found in

Top 1k

4233 packages

found in

Top 10k

29.36k packages

in community

Next steps

Investigate reported detections.

If the software should not include these network references, investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed, or until the issue is risk accepted.

Consider an alternative delivery mechanism for software packages.

Top behaviors

See all behaviors

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Top vulnerabilities

No vulnerabilities found.

FAQ for Fira Code and Material Icon Theme

What is Fira Code and Material Icon Theme?

Fira Code Font and Material Design Icons for Visual Studio Code. For more information about this package, visit its homepage.

Is Fira Code and Material Icon Theme malicious or is it safe to use?

The VS Code package Fira Code and Material Icon Theme was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. Malware or tampering has been detected, making it unsafe to download and use. 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.

Is Fira Code and Material Icon Theme popular?

The VS Code package Fira Code and Material Icon Theme ranks among the top 10000 projects in this community. It has 17K 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.

How do I secure Fira Code and Material Icon Theme once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how Fira Code and Material Icon Theme behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a Fira Code and Material Icon Theme version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.

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.

This website uses cookies to ensure the best website experience. By continuing to use this website you are giving your consent to cookies being used. Detailed information about our use of cookies is here.

Popularity

17.33k

Total Installs

Contributor

Declared Dependencies

Dependents

Top issues

See all issues

Problem

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Investigate reported detections.

Consult Mitre ATT&CK documentation: T1176.002 - Software Extensions: IDE Extensions.

If the development extension intent does not relate to the reported behavior, investigate your development environment for software supply chain compromise.

You should stop using the development extension until the investigation is completed, or until the issue is risk accepted.

Consider replacing the development extension with an alternative.

Problem

Prevalence in Visual Studio Code community

No prevalence information at this time

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

Prevalence in Visual Studio Code community

No prevalence information at this time

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

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1072 - Software Deployment Tools.

Consider rewriting the flagged code without using the marked behaviors.

Problem

Prevalence in Visual Studio Code community

79 packages

found in

Top 100

622 packages

found in

Top 1k

4233 packages

found in

Top 10k

29.36k packages

in community

Next steps

Investigate reported detections.

If the software should not include these network references, investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed, or until the issue is risk accepted.

Consider an alternative delivery mechanism for software packages.

Top behaviors

See all behaviors

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Top vulnerabilities

No vulnerabilities found.

Fira Code and Material Icon Theme

SAFE Assessment

Compliance

Security

Threats

Popularity

Top issues

TH16704Detected presence of development extensions that can collect sensitive system information.Causes risk: dangerous develop extensionshunting

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

TH17127Detected presence of files containing URLs that link to raw files on GitHub.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

Top behaviors

Reads from version control configuration files.steal

Prevalence in Visual Studio Code community

Reads from cloud provider configuration files.steal

Prevalence in Visual Studio Code community

Reads from CI/CD configuration files.steal

Prevalence in Visual Studio Code community

Writes to version control configuration files.file

Prevalence in Visual Studio Code community

Writes to directories managed by package managers.file

Prevalence in Visual Studio Code community

Top vulnerabilities

FAQ for Fira Code and Material Icon Theme

What is Fira Code and Material Icon Theme?

Is Fira Code and Material Icon Theme malicious or is it safe to use?

Is Fira Code and Material Icon Theme popular?

How do I secure Fira Code and Material Icon Theme once it is in my app?

Did you know...

Popularity

Top issues

TH16704Detected presence of development extensions that can collect sensitive system information.Causes risk: dangerous develop extensionshunting

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

TH17127Detected presence of files containing URLs that link to raw files on GitHub.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

Top behaviors

Reads from version control configuration files.steal

Prevalence in Visual Studio Code community

Reads from cloud provider configuration files.steal

Prevalence in Visual Studio Code community

Reads from CI/CD configuration files.steal

Prevalence in Visual Studio Code community

Writes to version control configuration files.file

Prevalence in Visual Studio Code community

Writes to directories managed by package managers.file

Prevalence in Visual Studio Code community

Top vulnerabilities