Spectra Assure

Toolbox

Explore

Learn

ReversingLabs

Spectra Assure

Community

VS Code

Search by package name, PURL or hash

failIncident: Malware

Scanned:

Source Code Visualizer

Artifact:

malicious

Top 10k

Visualize the calling structure of source code in a class diagram-like fashion

License: unknown

Published:

Publisher: visualprogrammingx

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

1 malformed components found

INCIDENTS FOR THIS VERSION:

malware

Reported By: ReversingLabs (Automated)

Learn more about malware detection

Overview issues5 vulnerabilities0 malware1 behaviors53 dependencies0 contributors1 versions10

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

Policies

Info

Problem

File formats are either textual or binary structured object streams. Programs that work with them, called parsers, depend on understanding the format structure. Intentional deviations from the expected file format structure can cause parsing issues, and trigger unintended code execution. During the scan, supported file formats have their specification conformance validated. While some deviations are allowed due to how widespread they are, most are subject to advanced heuristics that can detect attempts to cause format parsing issues.

Prevalence in Visual Studio Code community

4 packages

found in

Top 100

3 packages

found in

Top 1k

8 packages

found in

Top 10k

59 packages

in community

Next steps

When such detections occur, you should first review them for accuracy and assign vulnerability labels upon confirmation.

If the software intent does not relate to file format validation, investigate the build and release environment for software supply chain compromise.

Proceed with increased caution when using this software package.

Problem

Applications communicate with web services by exchanging HTTP requests. During software development, externally hosted services are used by developers to debug software quality issues relating to exchanging HTTP requests. Attackers commonly abuse tools designed for HTTP request inspection to monitor network traffic and extract sensitive information from the HTTP traffic. While the presence of domains related to HTTP inspection does not imply malicious intent, all of their uses in a software package should be documented and approved. Attackers might have purposely injected security testing tools in the software package to monitor the network traffic of the infected computer system. It is also possible that the software package has mistakenly included a part of its testing infrastructure during packaging.

Prevalence in Visual Studio Code community

32 packages

found in

Top 100

236 packages

found in

Top 1k

1220 packages

found in

Top 10k

7.61k 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 removing all references to flagged network locations.

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, some are commonly abused by malicious software with the intent to cause harm. When a software package shares behavior traits with malicious software, it may become flagged by security solutions. Any detection from security solutions can cause friction for the end-users during software deployment. While the behavior is likely intended by the developer, there is a small chance this detection is true positive, and an early indication of a software supply chain attack.

Prevalence in Visual Studio Code community

60 packages

found in

Top 100

434 packages

found in

Top 1k

2301 packages

found in

Top 10k

13.88k packages

in community

Next steps

Investigate reported detections.

If the software intent does not relate to the reported behavior, 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 rewriting the flagged code without using the marked behaviors.

Problem

Unicode is a text encoding standard designed to support the use of text written in all of the major languages and writing systems. While most languages are written from left to right, some are written in alternative directions. To accommodate encoding text written in such languages, the Unicode standard includes a number of special characters that allow the text direction to be specified. However, changing text direction can have adverse effects on how the encoded text is displayed and interpreted. For this reason, bidirectional Unicode control characters are commonly abused by malicious actors as a means of bypassing security solutions and avoiding detection. While presence of special Unicode characters does not imply malicious intent, all of its uses in a software package should be documented and approved. One example of acceptable use for these special characters is in script files that parse, validate, and transform Unicode-encoded text.

Prevalence in Visual Studio Code community

67 packages

found in

Top 100

487 packages

found in

Top 1k

2562 packages

found in

Top 10k

13.67k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1036.002 - Masquerading: Right-to-Left Override.

Consult publicly available materials on the Trojan Source vulnerability.

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. Paste-and-share services are websites that allow their users to easily share code snippets and simple plain text documents. Users typically do not need to be registered on the website to publish and access shared information. For this reason, paste-and-share services are commonly used by malicious actors to deliver stages of their malware payloads. Many software supply chain attacks in the open source space leverage paste-and-share services to deliver malicious payloads. Presence of paste-and-share service references does not imply malicious intent. Software developers commonly include links to such services as documentation for various issues they encounter while writing and maintaining code bases.

Prevalence in Visual Studio Code community

14 packages

found in

Top 100

110 packages

found in

Top 1k

719 packages

found in

Top 10k

3.69k 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 removing all references to flagged network locations.

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.

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

Policies

Info

Problem

Prevalence in Visual Studio Code community

4 packages

found in

Top 100

3 packages

found in

Top 1k

8 packages

found in

Top 10k

59 packages

in community

Next steps

When such detections occur, you should first review them for accuracy and assign vulnerability labels upon confirmation.

If the software intent does not relate to file format validation, investigate the build and release environment for software supply chain compromise.

Proceed with increased caution when using this software package.

Problem

Prevalence in Visual Studio Code community

32 packages

found in

Top 100

236 packages

found in

Top 1k

1220 packages

found in

Top 10k

7.61k 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 removing all references to flagged network locations.

Problem

Prevalence in Visual Studio Code community

60 packages

found in

Top 100

434 packages

found in

Top 1k

2301 packages

found in

Top 10k

13.88k packages

in community

Next steps

Investigate reported detections.

If the software intent does not relate to the reported behavior, 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 rewriting the flagged code without using the marked behaviors.

Problem

Prevalence in Visual Studio Code community

67 packages

found in

Top 100

487 packages

found in

Top 1k

2562 packages

found in

Top 10k

13.67k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1036.002 - Masquerading: Right-to-Left Override.

Consult publicly available materials on the Trojan Source vulnerability.

Problem

Prevalence in Visual Studio Code community

14 packages

found in

Top 100

110 packages

found in

Top 1k

719 packages

found in

Top 10k

3.69k 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 removing all references to flagged network locations.

Source Code Visualizer

SAFE Assessment

Compliance

Security

Threats

IMPORTANT: All versions of this package have been maliciousLatest version with malware incident detected: almost 2 years agoVersion: 0.1.9

INCIDENTS FOR THIS VERSION:

SQ30119Detected presence of suspicious file structure malformations.Causes risk: malformed components foundthreats

Problem

Prevalence in Visual Studio Code community

Next steps

TH17131Detected presence of files containing domains used for intercepting and inspecting HTTP requests.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH15103Detected presence of files with behaviors commonly used by malicious software.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH16102Detected presence of files containing bidirectional Unicode control characters.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH17104Detected presence of files containing URLs related to paste-and-share services.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

Did you know...

SQ30119Detected presence of suspicious file structure malformations.Causes risk: malformed components foundthreats

Problem

Prevalence in Visual Studio Code community

Next steps

TH17131Detected presence of files containing domains used for intercepting and inspecting HTTP requests.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH15103Detected presence of files with behaviors commonly used by malicious software.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH16102Detected presence of files containing bidirectional Unicode control characters.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH17104Detected presence of files containing URLs related to paste-and-share services.hunting

Problem

Prevalence in Visual Studio Code community

Next steps