Spectra Assure

failIncident: Malware

Scanned:

bashling Theme Remake

Artifact:

latest

malicious

License: unknown

Published:

Publisher: Malkolm

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

1 misconfigured toolchains detected

Threats

Tampering

No evidence of software tampering

Malware

2 analyst-vetted malware found

IMPORTANT: All versions of this package have been malicious

Latest malware incident detected:

Version: 1.0.0

INCIDENTS FOR THIS VERSION:

malware

Reported By: ReversingLabs (Automated)

Learn more about malware detection

malware

Reported By: ReversingLabs (Researcher)

Learn more about malware detection

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

Policies

Info

Count

Problem

Proprietary ReversingLabs malware detection algorithms have determined that the software package contains one or more malicious files. The detection was made by a machine learning model. This malware detection method is considered proactive, and can typically identify the malware threat type. 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 components to be detected as malicious.

Prevalence in Visual Studio Code community

13 packages

found in

Top 100

26 packages

found in

Top 1k

67 packages

found in

Top 10k

218 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.

Avoid using this software package until it is vetted as safe.

Consider rewriting code that may have triggered the detection due to its malware similarity.

SQ30109

Detected presence of malicious files through analyst-vetted file reputation.

Causes risk: analyst-vetted malware found

threats

Problem

Threat researchers have manually inspected the software package and determined that it contains one or more malicious files. The detection was made by a hash-based file reputation lookup. This malware detection method is considered highly accurate, and can typically identify the malware family by name.

Prevalence in Visual Studio Code community

1 packages

found in

Top 100

15 packages

found in

Top 1k

52 packages

found in

Top 10k

312 packages

in community

Next steps

Investigate the build and release environment for software supply chain compromise.

Avoid using this software package.

TH17127

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

hunting

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

78 packages

found in

Top 100

618 packages

found in

Top 1k

4203 packages

found in

Top 10k

27868 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.

SQ14138

Detected Windows executable files that were compiled without following the recommended SDL process.

Causes risk: misconfigured toolchains detected

hardening

Problem

Security Development Lifecycle (SDL) is a group of enhanced compile-time checks that report common coding mistakes as errors, preventing them from reaching production. These checks minimize the number of security issues by enforcing strict memory access checks. They also prevent the use of hard-to-secure string and memory manipulation functions. To prove the binary has been compiled with these checks enabled, the compiler emits a special debug object. Removing the debug table eliminates this proof. Therefore, this check only applies to binaries that still have their debug tables.

Prevalence in Visual Studio Code community

38 packages

found in

Top 100

250 packages

found in

Top 1k

719 packages

found in

Top 10k

3448 packages

in community

Next steps

You should keep the debug table to prove that the SDL process has been followed.

To enable these checks, refer to your programming language toolchain documentation.

In Microsoft VisualStudio, you can enable this feature by setting the compiler option /SDL to ON.

TH30112

Detected presence of software components without a declared source code repository.

hunting

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

57 packages

found in

Top 100

447 packages

found in

Top 1k

3421 packages

found in

Top 10k

56684 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.

SQ14127

Detected Windows executable files that do not implement long jump control flow vulnerability mitigation protection.

Causes risk: low priority mitigations absent

hardening

Problem

Control Flow Guard (CFG/CFI) protects the code flow integrity by ensuring that indirect calls are made only to vetted functions. This mitigation protects dynamically resolved function targets by instrumenting the code responsible for transferring execution control. Higher-level programming languages implement structured exception handling by managing their own code flow execution paths. As such, they are subject to code flow hijacking during runtime. Language-specific exception handling mitigation enforces execution integrity by instrumenting calls to manage execution context switching. Any deviation from the known and trusted code flow paths will cause the application to terminate. This makes malicious code less likely to execute.

Prevalence in Visual Studio Code community

43 packages

found in

Top 100

278 packages

found in

Top 1k

880 packages

found in

Top 10k

4106 packages

in community

Next steps

It's highly recommended to enable this option for all software components used at security boundaries, or those that process user controlled inputs.

To enable this mitigation, refer to your programming language toolchain documentation.

In Microsoft VisualStudio, you can enable CFG mitigation by passing the /guard:cf parameter to the compiler and linker.

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.

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

Policies

Info

Count

Problem

Prevalence in Visual Studio Code community

13 packages

found in

Top 100

26 packages

found in

Top 1k

67 packages

found in

Top 10k

218 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.

Avoid using this software package until it is vetted as safe.

Consider rewriting code that may have triggered the detection due to its malware similarity.

SQ30109

Detected presence of malicious files through analyst-vetted file reputation.

Causes risk: analyst-vetted malware found

threats

Problem

Prevalence in Visual Studio Code community

1 packages

found in

Top 100

15 packages

found in

Top 1k

52 packages

found in

Top 10k

312 packages

in community

Next steps

Investigate the build and release environment for software supply chain compromise.

Avoid using this software package.

TH17127

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

hunting

Problem

Prevalence in Visual Studio Code community

78 packages

found in

Top 100

618 packages

found in

Top 1k

4203 packages

found in

Top 10k

27868 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.

SQ14138

Detected Windows executable files that were compiled without following the recommended SDL process.

Causes risk: misconfigured toolchains detected

hardening

Problem

Prevalence in Visual Studio Code community

38 packages

found in

Top 100

250 packages

found in

Top 1k

719 packages

found in

Top 10k

3448 packages

in community

Next steps

You should keep the debug table to prove that the SDL process has been followed.

To enable these checks, refer to your programming language toolchain documentation.

In Microsoft VisualStudio, you can enable this feature by setting the compiler option /SDL to ON.

TH30112

Detected presence of software components without a declared source code repository.

hunting

Problem

Prevalence in Visual Studio Code community

57 packages

found in

Top 100

447 packages

found in

Top 1k

3421 packages

found in

Top 10k

56684 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.

SQ14127

Detected Windows executable files that do not implement long jump control flow vulnerability mitigation protection.

Causes risk: low priority mitigations absent

hardening

Problem

Prevalence in Visual Studio Code community

43 packages

found in

Top 100

278 packages

found in

Top 1k

880 packages

found in

Top 10k

4106 packages

in community

Next steps

It's highly recommended to enable this option for all software components used at security boundaries, or those that process user controlled inputs.

To enable this mitigation, refer to your programming language toolchain documentation.

In Microsoft VisualStudio, you can enable CFG mitigation by passing the /guard:cf parameter to the compiler and linker.