Our AI threat analyst detects malicious packages and blogs about OSS compromises
7000 write-ups and countingRead one

Spectra Assure

Toolbox

Explore

Learn

ReversingLabs

Spectra Assure

Community

VS Code

Search by package name, PURL or hash

failRisk: Vulnerabilities

Scanned:

⚡ Modern Live Server Pro

Artifact:

latest

Top 10k

Next-generation live server with instant reload, WebSocket sync, and zero-config setup. Perfect for modern web development with React, Vue, or vanilla HTML/CSS/JS projects.

License: unknown

Published:

Publisher: Shellomo

Visit GitHub

See on Visual Studio Code

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

1 severe vulnerabilities exploited

Hardening

2 execution hijacking concerns

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

Overview issues21 vulnerabilities13 malware0 behaviors162 dependencies10 contributors1 versions6

Popularity

10.73k

Total Installs

Contributor

Declared Dependencies

Dependents

Top issues

See all issues

Problem

Software composition analysis has identified a component with one or more known severe vulnerabilities. Available threat intelligence telemetry has confirmed that the reported high or critical severity vulnerabilities are actively being exploited by malicious actors.

Prevalence in Visual Studio Code community

67 packages

found in

Top 100

548 packages

found in

Top 1k

3078 packages

found in

Top 10k

17.39k packages

in community

Next steps

We strongly advise updating the component to the latest version.

If the update can't resolve the issue, create a plan to isolate or replace the affected component.

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

Prevalence in Visual Studio Code community

68 packages

found in

Top 100

555 packages

found in

Top 1k

3086 packages

found in

Top 10k

17.47k packages

in community

Next steps

Perform impact analysis for the reported CVEs.

Update the component to the latest version.

If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Problem

Software components are typically distributed in standardized packaging formats. Software packages are built from instructions written within package manifests that act as blueprints for package assembly. A package manifest declares the most important software properties, such as the package name, its authors and license, external dependencies, and various actions that may occur during the package lifecycle. Package managers are specialized tools used by developers to manage software components. Package managers read these manifests to deploy software components along with their dependencies. The premise of the package management system is that software components are isolated from each other, and that they rely on the package manager to provide their dependencies. However, it was detected that a software component includes code capable of accessing or modifying directories that are maintained exclusively by package managers. This is unusual as it resembles tactics used by threat actors that tamper with installed software components and inject malicious code into trusted execution paths.

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1554 - Compromise Host Software Binary.

Consider rewriting the flagged code without using the marked behaviors.

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 service 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 leverage 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

Review software component documentation for the reasons behind the recent version removal.

If the software version was removed due to a security incident, 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.

Top behaviors

CVE-2025-15284m

CVE-2026-2391m

None

Exploits Unknown

Exploits Exist

Exploited by Malware

Patching Mandated

FAQ for ⚡ Modern Live Server Pro

What is ⚡ Modern Live Server Pro?

Next-generation live server with instant reload, WebSocket sync, and zero-config setup. Perfect for modern web development with React, Vue, or vanilla HTML/CSS/JS projects. For more information about this package, visit its homepage.

Is ⚡ Modern Live Server Pro malicious or is it safe to use?

The VS Code package ⚡ Modern Live Server Pro was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. The package contains risks, and the analysis results should be reviewed before it is downloaded and used. Visit the Issues and Behaviors sections of the analysis for more details.

Is ⚡ Modern Live Server Pro popular?

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

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

10.73k

Total Installs

Contributor

Declared Dependencies

Dependents

Top issues

See all issues

Problem

Prevalence in Visual Studio Code community

67 packages

found in

Top 100

548 packages

found in

Top 1k

3078 packages

found in

Top 10k

17.39k packages

in community

Next steps

We strongly advise updating the component to the latest version.

If the update can't resolve the issue, create a plan to isolate or replace the affected component.

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

Prevalence in Visual Studio Code community

68 packages

found in

Top 100

555 packages

found in

Top 1k

3086 packages

found in

Top 10k

17.47k packages

in community

Next steps

Perform impact analysis for the reported CVEs.

Update the component to the latest version.

If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Problem

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1554 - Compromise Host Software Binary.

Consider rewriting the flagged code without using the marked behaviors.

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

11 packages

found in

Top 100

39 packages

found in

Top 1k

152 packages

found in

Top 10k

1.25k packages

in community

Next steps

Review software component documentation for the reasons behind the recent version removal.

If the software version was removed due to a security incident, 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.

Top behaviors

CVE-2025-15284m

CVE-2026-2391m

None

Exploits Unknown

Exploits Exist

Exploited by Malware

Patching Mandated

⚡ Modern Live Server Pro

SAFE Assessment

Compliance

Security

Threats

Popularity

Top issues

SQ31102Detected presence of severe vulnerabilities with active exploitation.Causes risk: actively exploited vulnerabilitiesvulnerabilities

Problem

Prevalence in Visual Studio Code community

Next steps

SQ31105Detected presence of high severity vulnerabilities.Causes risk: high severity vulnerabilitiesvulnerabilities

Problem

Prevalence in Visual Studio Code community

Next steps

TH16129Detected presence of software components that can tamper with other installed software.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

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

Problem

Prevalence in Visual Studio Code community

Next steps

TH30104Detected presence of software components that had a recent package version removal incident.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

Top behaviors

Writes to directories managed by package managers.file

Prevalence in Visual Studio Code community

Might contain potentially obfuscated code or data.anomaly

Prevalence in Visual Studio Code community

Encodes data using the Base64 algorithm.packer

Prevalence in Visual Studio Code community

Decodes data using the Base64 algorithm.packer

Prevalence in Visual Studio Code community

Contains a sequence of bytes that can be decoded into a printable string.packer

Prevalence in Visual Studio Code community

Top vulnerabilities

FAQ for ⚡ Modern Live Server Pro

What is ⚡ Modern Live Server Pro?

Is ⚡ Modern Live Server Pro malicious or is it safe to use?

Is ⚡ Modern Live Server Pro popular?

How do I secure ⚡ Modern Live Server Pro once it is in my app?

Did you know...

Popularity

Top issues

SQ31102Detected presence of severe vulnerabilities with active exploitation.Causes risk: actively exploited vulnerabilitiesvulnerabilities

Problem

Prevalence in Visual Studio Code community

Next steps

SQ31105Detected presence of high severity vulnerabilities.Causes risk: high severity vulnerabilitiesvulnerabilities

Problem

Prevalence in Visual Studio Code community

Next steps

TH16129Detected presence of software components that can tamper with other installed software.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

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

Problem

Prevalence in Visual Studio Code community

Next steps

TH30104Detected presence of software components that had a recent package version removal incident.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

Top behaviors

Writes to directories managed by package managers.file

Prevalence in Visual Studio Code community

Might contain potentially obfuscated code or data.anomaly

Prevalence in Visual Studio Code community

Encodes data using the Base64 algorithm.packer

Prevalence in Visual Studio Code community

Decodes data using the Base64 algorithm.packer

Prevalence in Visual Studio Code community

Contains a sequence of bytes that can be decoded into a printable string.packer

Prevalence in Visual Studio Code community

Top vulnerabilities