Top issues
Detected presence of known software supply chain attack artifacts.
Causes risk: supply chain attack artifacts
threats
Problem
Proprietary ReversingLabs malware detection algorithms have determined that the software package contains one or more malicious components. The detection was made by either a static byte signature, software component identity, or a complete file hash. This malware detection method is considered highly accurate, and can typically attribute malware to previously discovered software supply chain attacks. It is common to have multiple supply chain attack artifacts that relate to a single malware incident.Prevalence in Visual Studio Code community
2 packages
found in
Top 100
15 packages
found in
Top 1k
51 packages
found in
Top 10k
341 packages
in community
Next steps
If the software intent does not relate to malicious behavior, investigate the build and release environment for software supply chain compromise.
Avoid using this software package.
Detected presence of malicious files through analyst-vetted file reputation.
Causes risk: analyst-vetted malware found
threats
Problem
Threat researchers have manually inspected the software package and determined that it contains one or more malicious files. The detection was made by a hash-based file reputation lookup. This malware detection method is considered highly accurate, and can typically identify the malware family by name.Prevalence in Visual Studio Code community
0 packages
found in
Top 100
3 packages
found in
Top 1k
3 packages
found in
Top 10k
191 packages
in community
Next steps
Investigate the build and release environment for software supply chain compromise.
Avoid using this software package.
Detected presence of software components that were removed from the public package repository.
Causes risk: components prone to hijacking
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. Open source projects are the intellectual property of their respective authors. At any time, the authors may choose to completely remove the software component from a public repository. This often occurs when a software project reaches its end-of-life stage, or when the software authors lose interest in maintaining the project. This kind of removal frees up the software package name, its unique software identifier in the public repository, for other developers to use. However, new software project owners might have malicious intent. Threat actors are continuously monitoring popular package names in case their unique identifiers suddenly become available for hijacking. Once the software projects falls under new ownership, the new maintainers may opt to use the project popularity to spread malware to unsuspecting users.Prevalence in Visual Studio Code community
1 packages
found in
Top 100
42 packages
found in
Top 1k
375 packages
found in
Top 10k
34.8k packages
in community
Next steps
Inspect behaviors exhibited by the detected software components.
If the software behaviors differ from expected, investigate the build and release environment for software supply chain compromise.
Revise the use of components that raise these alarms. If you can't deprecate those components, make sure that their versions are pinned.
Avoid using this software package until it is vetted as safe.
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
2 packages
found in
Top 100
5 packages
found in
Top 1k
44 packages
found in
Top 10k
7.07k 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
Encodes data using the Base64 algorithm.
packer
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
82 packages
found in
Top 100
636 packages
found in
Top 1k
3971 packages
found in
Top 10k
25.82k packages
in community
Decodes data using the Base64 algorithm.
packer
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
74 packages
found in
Top 100
578 packages
found in
Top 1k
3262 packages
found in
Top 10k
18.65k packages
in community
Encodes data using the Base16 algorithm.
file
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
81 packages
found in
Top 100
643 packages
found in
Top 1k
4030 packages
found in
Top 10k
25.17k packages
in community
Decodes data using the Base16 algorithm.
file
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
72 packages
found in
Top 100
531 packages
found in
Top 1k
2840 packages
found in
Top 10k
14.21k packages
in community
Executes files during installation or upon launch.
execution
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
94 packages
found in
Top 100
837 packages
found in
Top 1k
6746 packages
found in
Top 10k
87.76k packages
in community
Top vulnerabilities
No vulnerabilities found.