Spectra Assure

warningRisk: Tampering

Scanned:

Relative Path

Artifact:

latest

Top 1k

Get relative url paths from files in the current workspace.

License: Permissive (MIT)

Published:

Publisher: jakob101

Visit GitHub

See on Visual Studio Code

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

1 low severity vulnerabilities

Hardening

No application hardening issues

Threats

Tampering

1 suspicious application behaviors

Malware

No evidence of malware inclusion

List of software quality issues with the number of affected components.

Policies

Info

Problem

Software components contain executable code that performs actions implemented during its development. These actions are called behaviors. In the analysis report, behaviors are presented as human-readable descriptions that best match the underlying code intent. Node Package Manager (NPM) repository is often abused by threat actors to publish software packages that exhibit malicious behaviors. Malware authors use numerous tactics to lure developers into including malicious NPM packages in their software projects. Most malicious packages published on NPM target developers and their workstations. However, some are designed to activate only when deployed in the end-user environment. Both types of NodeJS malicious packages are detected by proprietary ReversingLabs threat hunting algorithms. This detection method is considered proactive, and it is based on Machine Learning (ML) algorithms that can detect novel malware. The detection is strongly influenced by behaviors that software components exhibit. Behaviors similar to previously discovered malware and software supply chain attacks may cause some otherwise benign software packages to be detected by this policy.

Prevalence in Visual Studio Code community

10 packages

found in

Top 100

69 packages

found in

Top 1k

311 packages

found in

Top 10k

1.86k packages

in community

Next steps

Investigate reported detections.

If the software intent does not relate to the reported behavior, 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 rewriting the flagged code without using the marked behaviors.

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 low severity.

Prevalence in Visual Studio Code community

52 packages

found in

Top 100

388 packages

found in

Top 1k

2065 packages

found in

Top 10k

10.51k packages

in community

Next steps

Perform impact analysis for the reported CVEs.

Update the component to the latest version.

Lower severity vulnerabilities can be resolved with less urgency, but you should still make a plan to do so.

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. A port number is associated with a network address of a host, such as an IP address, and the type of network protocol used for communication. Within URLs, the ports are optional. Ports can be specified in a URL immediately following the domain name. Each network protocol, or schema, has a set of standard ports on which the service operates. This issue is raised when a mismatch between a network protocol and its expected port number is detected. While the presence of non-standard ports does not imply malicious intent, all of their uses in a software package should be documented and approved.

Prevalence in Visual Studio Code community

79 packages

found in

Top 100

560 packages

found in

Top 1k

2912 packages

found in

Top 10k

17.75k 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 changing the port to one that is standard for the networking protocol.

Problem

Private keys and certificates are considered sensitive information that should not be included in released software packages. However, developers frequently release sensitive information alongside their applications to facilitate automated software testing. Testing keys and certificates often proliferate through the software supply chain. When such information gets shared publicly, it is catalogued by file reputation databases. Any private key and certificate files seen by a file reputation database prior to configured time threshold can be automatically suppressed. Commonly shared sensitive information is not considered to be secret.

Prevalence in Visual Studio Code community

52 packages

found in

Top 100

399 packages

found in

Top 1k

1849 packages

found in

Top 10k

9.29k packages

in community

Next steps

Review the commonly shared sensitive information for evidence of inadvertently exposed secrets.

If the keys were published unintentionally and the software has been made public, you should revoke the keys and file a security incident.

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.

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.

List of software quality issues with the number of affected components.

Policies

Info

Problem

Prevalence in Visual Studio Code community

10 packages

found in

Top 100

69 packages

found in

Top 1k

311 packages

found in

Top 10k

1.86k packages

in community

Next steps

Investigate reported detections.

If the software intent does not relate to the reported behavior, 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 rewriting the flagged code without using the marked behaviors.

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 low severity.

Prevalence in Visual Studio Code community

52 packages

found in

Top 100

388 packages

found in

Top 1k

2065 packages

found in

Top 10k

10.51k packages

in community

Next steps

Perform impact analysis for the reported CVEs.

Update the component to the latest version.

Lower severity vulnerabilities can be resolved with less urgency, but you should still make a plan to do so.

Problem

Prevalence in Visual Studio Code community

79 packages

found in

Top 100

560 packages

found in

Top 1k

2912 packages

found in

Top 10k

17.75k 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 changing the port to one that is standard for the networking protocol.

Problem

Prevalence in Visual Studio Code community

52 packages

found in

Top 100

399 packages

found in

Top 1k

1849 packages

found in

Top 10k

9.29k packages

in community

Next steps

Review the commonly shared sensitive information for evidence of inadvertently exposed secrets.

If the keys were published unintentionally and the software has been made public, you should revoke the keys and file a security incident.

Problem

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.

Relative Path

SAFE Assessment

Compliance

Security

Threats

TH15502Detected presence of files with behaviors similar to malicious packages published on NPM.Causes risk: suspicious application behaviorshunting

Problem

Prevalence in Visual Studio Code community

Next steps

SQ31107Detected presence of low severity vulnerabilities.Causes risk: low severity vulnerabilitiesvulnerabilities

Problem

Prevalence in Visual Studio Code community

Next steps

TH17115Detected presence of files containing URLs that use non-standard ports.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

SQ34101Detected presence of commonly distributed sensitive data.secrets

Problem

Prevalence in Visual Studio Code community

Next steps

TH16126Detected presence of software components that can access user identity information.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

Did you know...

TH15502Detected presence of files with behaviors similar to malicious packages published on NPM.Causes risk: suspicious application behaviorshunting

Problem

Prevalence in Visual Studio Code community

Next steps

SQ31107Detected presence of low severity vulnerabilities.Causes risk: low severity vulnerabilitiesvulnerabilities

Problem

Prevalence in Visual Studio Code community

Next steps

TH17115Detected presence of files containing URLs that use non-standard ports.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

SQ34101Detected presence of commonly distributed sensitive data.secrets

Problem

Prevalence in Visual Studio Code community

Next steps

TH16126Detected presence of software components that can access user identity information.hunting

Problem

Prevalence in Visual Studio Code community

Next steps