Top issues
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 services 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 leverages the GitHub service to deliver malicious payloads.Prevalence in Visual Studio Code community
78 packages
found in
Top 100
618 packages
found in
Top 1k
4203 packages
found in
Top 10k
27868 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.
Detected presence of software components that were recently published to the public package repository.
hunting
Problem
Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Software developers publish components they have authored to public repositories. While a new software project is a welcome addition to the open source community, it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of being the first to try out a new project lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.Prevalence in Visual Studio Code community
0 packages
found in
Top 100
4 packages
found in
Top 1k
44 packages
found in
Top 10k
7143 packages
in community
Next steps
Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.
Top behaviors
Modifies file/directory permissions.
permissions
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
65 packages
found in
Top 100
535 packages
found in
Top 1k
2853 packages
found in
Top 10k
14133 packages
in community
Might contain potentially obfuscated code or data.
anomaly
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
85 packages
found in
Top 100
673 packages
found in
Top 1k
4329 packages
found in
Top 10k
28768 packages
in community
Encodes data using the Base64 algorithm.
packer
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
81 packages
found in
Top 100
631 packages
found in
Top 1k
3887 packages
found in
Top 10k
24357 packages
in community
Decodes data using the Base64 algorithm.
packer
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
73 packages
found in
Top 100
573 packages
found in
Top 1k
3170 packages
found in
Top 10k
17492 packages
in community
Contains URLs that link to raw files on GitHub.
network
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
78 packages
found in
Top 100
618 packages
found in
Top 1k
4203 packages
found in
Top 10k
27868 packages
in community
Top vulnerabilities
No vulnerabilities found.