Spectra Assure
Community
Docs
failIncident: Malware
Scanned: 1 day ago

Test Runner for Java

Artifact:
malicious
Top 100
Run and debug JUnit or TestNG test cases.
License: unknown
Published: almost 7 years ago
Publisher: vscjava
Visit Github
See on Visual Studio Code

SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
12 severe vulnerabilities exploited
Hardening
No application hardening issues

Threats

Tampering
1 suspicious application behaviors
Malware
1 malicious dependencies found

INCIDENTS:

malware
1 day agoReported By: ReversingLabs (Automated)
Learn more about malware detection

Popularity

39.53M
Total Installs
1
Contributor
12
Declared Dependencies
8
Dependents

Top issues

See all issues

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

No prevalence information at this time

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

No prevalence information at this time

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

No prevalence information at this time

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.

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

No prevalence information at this time

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 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. While the majority of open source contributors are altruistic and trustworthy, some software developers have a history of making harmful changes to the projects they maintain. Changes that are considered harmful include destructive and disruptive actions, and other developer behaviors that might cause them to be considered untrustworthy in their community. Code written by these software developers should be put under higher degree of scrutiny, and continuously reviewed for unexpected changes.

Prevalence in Visual Studio Code community

No prevalence information at this time

Next steps

Investigate reported detections.
You should consider delaying the software release until the investigation is completed, or until the issue is risk accepted.
Consider replacing the software component with an alternative.

Top behaviors

See all behaviors

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Prevalence in Visual Studio Code community

No behavior prevalence information at this time

Top vulnerabilities

See all vulnerabilities
Vulnerability Exploitation Lifecycle
(25 Active Vulnerabilities)
6 (6 Fixable)
CVE-2019-15598c
CVE-2019-15599c
CVE-2022-25647h
19 (19 Fixable)
CVE-2019-10744c
CVE-2021-21353c
CVE-2021-43138h
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated

FAQ for Test Runner for Java

What is Test Runner for Java?

Run and debug JUnit or TestNG test cases. For more information about this package, visit its homepage.

Is Test Runner for Java malicious or is it safe to use?

The VS Code package Test Runner for Java 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. 12 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.

Is Test Runner for Java popular?

The VS Code package Test Runner for Java ranks among the top 100 projects in this community. It has 40M 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 Test Runner for Java once it is in my app?

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