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
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.
Detected digital signatures that have not been performed with an extended validation certificate.
signatures
Problem
Digital signatures are applied to applications, packages and documents as a cryptographically secured authenticity record. Signatures are made using digital certificates, which can either be purchased from certificate authorities or be self-issued. When a certificate is purchased from a certificate authority, the subject that requests it goes through an identity validation process. Depending on the certificate type, those checks can be basic or extended. Confirming the subject identity is a multi-step process, and the requesting subject can be mapped to its legal entity name only through extended validation of submitted documents. Extended identity validation typically costs more, and it takes longer for a certificate to be issued when this process is correctly followed.Prevalence in Visual Studio Code community
31 packages
found in
Top 100
127 packages
found in
Top 1k
356 packages
found in
Top 10k
1.42k packages
in community
Next steps
Consider the benefits of acquiring extended validation certificates. Operating systems tend to be more trusting of software packages signed in this way. Certain security warnings and prompts might also be automatically suppressed. This reduces the number of support tickets for organizations that opt to use extended validation certificates.
Problem
Operating systems allow multiple user accounts to coexist on a single computer system. Each registered user has identity information associated with their account. At the very least, user accounts consist of a user name and an optional password. In some cases, user account data may also include personally identifiable information. Extended personal information may include user's given and last name, their email and mailing address, personal photo and their telephone number. Financially motivated attackers may seek to collect personal information for purposes of selling the private data to a third-party. Malicious code that typically exhibits these behavior traits is commonly referred to as an information stealer. While the presence of code that accesses identity information does not necessarily imply malicious intent, all of its uses in a software package should be documented and approved. Accessing identity information is a very common behavior for software packages. One example of acceptable use for such functions is verifying that the active user has purchased a software license that allows them to run the application.Prevalence in Visual Studio Code community
65 packages
found in
Top 100
419 packages
found in
Top 1k
1961 packages
found in
Top 10k
9.65k packages
in community
Next steps
Investigate reported detections as indicators of software tampering.
Consult Mitre ATT&CK documentation: T1033 - System Owner/User Discovery.
Top behaviors
Tampers with keyboard bindings.
stealth
Prevalence in Visual Studio Code community
Behavior uncommon for this community (Uncommon)
2 packages
found in
Top 100
1 packages
found in
Top 1k
5 packages
found in
Top 10k
17 packages
in community
Retrieves the name of the user associated with the process.
search
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
26 packages
found in
Top 100
136 packages
found in
Top 1k
330 packages
found in
Top 10k
1.5k packages
in community
Loads additional snap-ins or modules to the current session.
payload
Prevalence in Visual Studio Code community
Behavior uncommon for this community (Uncommon)
2 packages
found in
Top 100
5 packages
found in
Top 1k
15 packages
found in
Top 10k
61 packages
in community
Interacts with Microsoft .NET Framework code, types and assemblies.
execution
Prevalence in Visual Studio Code community
Behavior uncommon for this community (Uncommon)
11 packages
found in
Top 100
50 packages
found in
Top 1k
198 packages
found in
Top 10k
882 packages
in community
Executes a file.
execution
Prevalence in Visual Studio Code community
Behavior often found in this community (Common)
52 packages
found in
Top 100
290 packages
found in
Top 1k
981 packages
found in
Top 10k
4.36k packages
in community
Top vulnerabilities
No vulnerabilities found.