Spectra Assure

passEverything is awesome!

Scanned:

Salesforce Live Preview

Artifact:

latest

Top 10k

Salesforce Live Preview for Lightning Web Components

License: Permissive (BSD-3-Clause)

Published:

Publisher: salesforce

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

No evidence of software tampering

Malware

No evidence of malware inclusion

Popularity

37.09k

Total Installs

Contributor

Declared Dependencies

Dependents

Top issues

See all 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.

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. While most behaviors are benign on their own, some might become important for analysis when observed alongside other capabilities the component exhibits. This issue is reported for files that can enumerate user information and make HTTP requests. While presence of this behavior combination does not imply malicious intent, it is advised that the reported files are reviewed. One example of acceptable use for this type of data collection is the opt-in telemetry for software debugging purposes.

Prevalence in Visual Studio Code community

28 packages

found in

Top 100

137 packages

found in

Top 1k

348 packages

found in

Top 10k

1.67k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1033 - System Owner/User Discovery.

Consider limiting the collection of user information to a minimum.

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. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up the reputation of their open source projects by developing in public. Modern source code repositories have many social features that allow software developers to handle bug reports, have discussions with their users, and convey reaching significant project milestones. It is uncommon to find open source projects that omit linking their component to a publicly accessible source code repository.

Prevalence in Visual Studio Code community

53 packages

found in

Top 100

442 packages

found in

Top 1k

3405 packages

found in

Top 10k

57.88k 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.

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

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

See all behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

67 packages

found in

Top 100

547 packages

found in

Top 1k

2891 packages

found in

Top 10k

14.99k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

45 packages

found in

Top 100

315 packages

found in

Top 1k

1576 packages

found in

Top 10k

7.59k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

84 packages

found in

Top 100

679 packages

found in

Top 1k

4393 packages

found in

Top 10k

30.42k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

18 packages

found in

Top 100

122 packages

found in

Top 1k

340 packages

found in

Top 10k

1.37k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

34 packages

found in

Top 100

237 packages

found in

Top 1k

903 packages

found in

Top 10k

4.31k packages

in community

Top vulnerabilities

No vulnerabilities found.

FAQ for Salesforce Live Preview

What is Salesforce Live Preview?

Salesforce Live Preview for Lightning Web Components. For more information about this package, visit its homepage.

Is Salesforce Live Preview malicious or is it safe to use?

The VS Code package Salesforce Live Preview was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. No risks were detected, therefore, this version of the package is currently considered as safe to use.

Is Salesforce Live Preview popular?

The VS Code package Salesforce Live Preview ranks among the top 10000 projects in this community. It has 37K 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 Salesforce Live Preview once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how Salesforce Live Preview behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a Salesforce Live Preview 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

37.09k

Total Installs

Contributor

Declared Dependencies

Dependents

Top issues

See all issues

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.

Problem

Prevalence in Visual Studio Code community

28 packages

found in

Top 100

137 packages

found in

Top 1k

348 packages

found in

Top 10k

1.67k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1033 - System Owner/User Discovery.

Consider limiting the collection of user information to a minimum.

Problem

Prevalence in Visual Studio Code community

53 packages

found in

Top 100

442 packages

found in

Top 1k

3405 packages

found in

Top 10k

57.88k 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.

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

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

See all behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

67 packages

found in

Top 100

547 packages

found in

Top 1k

2891 packages

found in

Top 10k

14.99k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

45 packages

found in

Top 100

315 packages

found in

Top 1k

1576 packages

found in

Top 10k

7.59k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

84 packages

found in

Top 100

679 packages

found in

Top 1k

4393 packages

found in

Top 10k

30.42k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

18 packages

found in

Top 100

122 packages

found in

Top 1k

340 packages

found in

Top 10k

1.37k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

34 packages

found in

Top 100

237 packages

found in

Top 1k

903 packages

found in

Top 10k

4.31k packages

in community

Top vulnerabilities

No vulnerabilities found.

Salesforce Live Preview

SAFE Assessment

Compliance

Security

Threats

Popularity

Top issues

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

Problem

Prevalence in Visual Studio Code community

Next steps

TH16106Detected presence of files that collect and exfiltrate user information.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH30112Detected presence of software components without a declared source code repository.hunting

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

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

Problem

Prevalence in Visual Studio Code community

Next steps

Top behaviors

Modifies file/directory permissions.permissions

Prevalence in Visual Studio Code community

Changes file ownership.file

Prevalence in Visual Studio Code community

Might contain potentially obfuscated code or data.anomaly

Prevalence in Visual Studio Code community

Encrypts data using SEED cipher.packer

Prevalence in Visual Studio Code community

Encrypts data using Advanced Encryption Standard (AES).packer

Prevalence in Visual Studio Code community

Top vulnerabilities

FAQ for Salesforce Live Preview

What is Salesforce Live Preview?

Is Salesforce Live Preview malicious or is it safe to use?

Is Salesforce Live Preview popular?

How do I secure Salesforce Live Preview once it is in my app?

Did you know...

Popularity

Top issues

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

Problem

Prevalence in Visual Studio Code community

Next steps

TH16106Detected presence of files that collect and exfiltrate user information.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH30112Detected presence of software components without a declared source code repository.hunting

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

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

Problem

Prevalence in Visual Studio Code community

Next steps

Top behaviors

Modifies file/directory permissions.permissions

Prevalence in Visual Studio Code community

Changes file ownership.file

Prevalence in Visual Studio Code community

Might contain potentially obfuscated code or data.anomaly

Prevalence in Visual Studio Code community

Encrypts data using SEED cipher.packer

Prevalence in Visual Studio Code community

Encrypts data using Advanced Encryption Standard (AES).packer

Prevalence in Visual Studio Code community

Top vulnerabilities