Spectra Assure
Community
Docs
failIncident: Malware
Scanned: about 15 hours ago

Vetur E

Artifact:
latest
malicious
Top 10k
Research
Vue tooling for VS Code
License: unknown
Published: over 7 years ago
Publisher: qiang014
Visit Github
See on Visual Studio Code

SAFE Assessment

Compliance

Licenses
2 copyleft licensed components
Secrets
No sensitive information found

Security

Vulnerabilities
31 severe vulnerabilities exploited
Hardening
No application hardening issues

Threats

Tampering
1 suspicious application behaviors
Malware
4 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

malware
8 months agoReported By: ReversingLabs (Automated)
Learn more about malware detection
malware
Reported By: ReversingLabs (Researcher)
Learn more about malware detection

Popularity

65.38k
Total Installs
1
Contributor
2
Declared Dependencies
0
Dependents

Top issues

See all issues

Problem

Potentially unwanted applications (PUAs) can be considered a risk by some software users. This threat type typically collects private user data, or in more extreme cases, tampers with system security settings. Most threat prevention solutions detect and block PUAs. Software packages that trigger security solution detections also tend to increase the number of support calls and open tickets from users.

Prevalence in Visual Studio Code community

2 packages
found in
Top 100
2 packages
found in
Top 1k
2 packages
found in
Top 10k
47 packages
in community

Next steps

Revise the use of components that raise these alarms. If you can't deprecate those components, make sure they are well-documented.

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
16 packages
found in
Top 1k
55 packages
found in
Top 10k
301 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.

Problem

Proprietary ReversingLabs malware detection algorithms have determined that the software package has one or more malicious dependencies. Some software dependencies may be optional, and could be installed or downloaded only if a certain pre-defined condition is met. When software dependencies are confirmed to be found within the software package, additional issues might also be reported. 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.

Prevalence in Visual Studio Code community

5 packages
found in
Top 100
48 packages
found in
Top 1k
192 packages
found in
Top 10k
638 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 they are well-documented.
Avoid using this software package until it is vetted as safe.

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

71 packages
found in
Top 100
568 packages
found in
Top 1k
3198 packages
found in
Top 10k
16595 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 critical severity.

Prevalence in Visual Studio Code community

64 packages
found in
Top 100
445 packages
found in
Top 1k
2064 packages
found in
Top 10k
9214 packages
in community

Next steps

Perform impact analysis for the reported CVEs.
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.

Top behaviors

See all behaviors

Prevalence in Visual Studio Code community

Behavior commonly used by malicious software (Important)
Behavior uncommon for this community (Uncommon)
7 packages
found in
Top 100
40 packages
found in
Top 1k
131 packages
found in
Top 10k
507 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
48 packages
found in
Top 100
323 packages
found in
Top 1k
1111 packages
found in
Top 10k
4964 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
65 packages
found in
Top 100
535 packages
found in
Top 1k
2853 packages
found in
Top 10k
14133 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
15 packages
found in
Top 100
110 packages
found in
Top 1k
397 packages
found in
Top 10k
2369 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
42 packages
found in
Top 100
313 packages
found in
Top 1k
1548 packages
found in
Top 10k
7212 packages
in community

Top vulnerabilities

See all vulnerabilities
Vulnerability Exploitation Lifecycle
(61 Active Vulnerabilities)
16 (15 Fixable)
CVE-2018-1000620c
CVE-2021-37701h
CVE-2021-37712h
45 (43 Fixable)
CVE-2018-16492c
CVE-2018-3750c
CVE-2019-10746c
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated

FAQ for Vetur E

What is Vetur E?

Vue tooling for VS Code.

Is Vetur E malicious or is it safe to use?

The VS Code package Vetur E was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. Malware or tampering has been detected, making it unsafe to download and use. 31 other issues and risky behaviors were found. 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. All versions of the Vetur E package were malicious.

Is Vetur E popular?

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

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