Spectra Assure

warningRisk: Secrets

Scanned:

snyk

latest

Top 10k

snyk library and cli utility

License: Permissive (Apache-2.0)

Published:

Visit GitHub

See on npm

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

2 web service credentials found

Security

Vulnerabilities

No known vulnerabilities detected

Hardening

2 execution hijacking concerns

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

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

Policies

Info

Problem

Proprietary ReversingLabs analysis engine supports a wide range of commonly used archive and software packaging formats. Using automated static file decomposition technologies, the engine recursively analyzes complex software packages. Software analysis is typically conducted in multiple steps. Content identification, unpacking, validation, and classification are some of the steps performed on each analyzed file. The analysis engine may sometimes report file integrity problems while performing unpacking or validation steps. In this case, no content was extracted from the package before an analysis error was encountered. This issue is commonly reported for packages with content that may be incomplete or corrupted. In rare occurrences this issue may indicate a problem with the analysis engine's file format parsing functions.

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

19 packages

found in

Top 10k

3.74k packages

in community

Next steps

Confirm that the software package contains incomplete or corrupted content.

Create a new version of the software package that resolves content integrity issues.

Contact the ReversingLabs support team if you suspect that the analysis engine may be causing the issue.

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 npm community

10 packages

found in

Top 100

53 packages

found in

Top 1k

981 packages

found in

Top 10k

194.82k 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

Buffer overrun protection on Linux is achieved in two ways. The most common solution is to use the stack canary (also called cookie). The stack canary is a special value written onto the stack that allows the operating system to detect and terminate the program if a stack overrun occurs. In most cases, compilers will apply the stack canary conservatively in order to avoid a negative performance impact. Therefore, stack canaries are often used together with another stack overrun mitigation - fortified functions. Fortified functions are usually wrappers around standard glibc functions (such as memcpy) which perform boundary checks either at compile time or run time to determine if a memory violation has occurred. The compiler needs additional context to generate such calls (for example, array size that needs to be known at compile time). Because of this, the compiler will virtually never substitute all viable functions with their fortified counterparts in complex programs. However, when combined with the stack canary, fortified functions provide a good measure of buffer overrun protection.

Prevalence in npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

98 packages

found in

Top 10k

12.03k packages

in community

Next steps

Presence of unfortified memory functions may indicate use of unsafe programming practices, and you should avoid it if possible.

In GCC, enable fortified functions with -fstack-protector and -D_FORTIFY_SOURCE=2 flag, while using at least -O1 optimization level.

Problem

Prevalence in npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

84 packages

found in

Top 10k

10.19k packages

in community

Next steps

Presence of some input functions may indicate use of unsafe programming practices, and you should avoid it if possible.

In GCC, enable fortified functions with -fstack-protector and -D_FORTIFY_SOURCE=2 flag, while using at least -O1 optimization level.

Problem

Various network communication protocols allow including plaintext authentication credentials. Information such as user names and passwords could be passed through a non-encrypted channel, and therefore intercepted by malicious actors. Credentials are considered secrets, and should be kept encrypted until they are used. This policy control matches the following URI pattern protocol://username:password@domain within any software package component.

Prevalence in npm community

1 packages

found in

Top 100

3 packages

found in

Top 1k

110 packages

found in

Top 10k

22.4k packages

in community

Next steps

Review the reported matches. If the warning refers to a placeholder credential value, it can be safely ignored.

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. URL paths provide additional information to a web service when making a request. They are an optional, but an important part of the URL, as they may define specific content or actions based on the data being passed. Some parameters they pass might be considered sensitive information. Since path components are not encrypted this might cause sensitive information to leak. This issue is raised for URL paths than might contain information that attackers can easily intercept. Examples of sensitive information fields include passwords and other similar parameters.

Prevalence in npm community

1 packages

found in

Top 100

11 packages

found in

Top 1k

131 packages

found in

Top 10k

30.49k 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

On Linux, external symbols are resolved via the procedure linkage table (PLT) and the global offset table (GOT). Without any protection, both are writable at runtime and thus leave the executable vulnerable to pointer hijacking - an attack where the function address is overwritten with an address of a malicious function. Pointer hijacking can be mitigated by using full read-only relocations, which instruct the compiler to unify global offset tables into a single read-only table. This requires that all external function symbols are resolved at load-time instead of during execution, and may increase loading time for large programs.

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

79 packages

found in

Top 10k

9.13k packages

in community

Next steps

In most cases, it's recommended to use full read-only relocations (in GCC: -Wl,-z,relro,-z,now).

If the executable load-time is an issue, you should use partial read-only relocations.

Problem

Common compilers often embed source code information into executables for debugging purposes, usually by mapping symbols to source filenames or paths. While this is typically desirable in open-source software and standard tools, that information can be used to determine security weaknesses, code repository layout, trade secrets and similar sensitive information. Such symbols make it easier to reverse-engineer a closed source application.

Prevalence in npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

119 packages

found in

Top 10k

14.5k packages

in community

Next steps

Strip out such information in the linking phase by using compiler options like the -s flag in GCC, or in the post-build phase by using the strip tool.

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 npm community

5 packages

found in

Top 100

21 packages

found in

Top 1k

374 packages

found in

Top 10k

113.9k 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

Operating systems allow multiple user accounts to coexist on a single computer system. Each registered user has identity information associated with their account. At the very least, user accounts consist of a user name and an optional password. In some cases, user account data may also include personally identifiable information. Extended personal information may include user's given and last name, their email and mailing address, personal photo and their telephone number. Financially motivated attackers may seek to collect personal information for purposes of selling the private data to a third-party. Malicious code that typically exhibits these behavior traits is commonly referred to as an information stealer. While the presence of code that accesses identity information does not necessarily imply malicious intent, all of its uses in a software package should be documented and approved. Accessing identity information is a very common behavior for software packages. One example of acceptable use for such functions is verifying that the active user has purchased a software license that allows them to run the application.

Prevalence in npm community

2 packages

found in

Top 100

6 packages

found in

Top 1k

181 packages

found in

Top 10k

39.81k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1033 - System Owner/User Discovery.

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 npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

19 packages

found in

Top 10k

3.74k packages

in community

Next steps

Confirm that the software package contains incomplete or corrupted content.

Create a new version of the software package that resolves content integrity issues.

Contact the ReversingLabs support team if you suspect that the analysis engine may be causing the issue.

Problem

Prevalence in npm community

10 packages

found in

Top 100

53 packages

found in

Top 1k

981 packages

found in

Top 10k

194.82k 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 npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

98 packages

found in

Top 10k

12.03k packages

in community

Next steps

Presence of unfortified memory functions may indicate use of unsafe programming practices, and you should avoid it if possible.

In GCC, enable fortified functions with -fstack-protector and -D_FORTIFY_SOURCE=2 flag, while using at least -O1 optimization level.

Problem

Prevalence in npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

84 packages

found in

Top 10k

10.19k packages

in community

Next steps

Presence of some input functions may indicate use of unsafe programming practices, and you should avoid it if possible.

In GCC, enable fortified functions with -fstack-protector and -D_FORTIFY_SOURCE=2 flag, while using at least -O1 optimization level.

Problem

Prevalence in npm community

1 packages

found in

Top 100

3 packages

found in

Top 1k

110 packages

found in

Top 10k

22.4k packages

in community

Next steps

Review the reported matches. If the warning refers to a placeholder credential value, it can be safely ignored.

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. URL paths provide additional information to a web service when making a request. They are an optional, but an important part of the URL, as they may define specific content or actions based on the data being passed. Some parameters they pass might be considered sensitive information. Since path components are not encrypted this might cause sensitive information to leak. This issue is raised for URL paths than might contain information that attackers can easily intercept. Examples of sensitive information fields include passwords and other similar parameters.

Prevalence in npm community

1 packages

found in

Top 100

11 packages

found in

Top 1k

131 packages

found in

Top 10k

30.49k 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 npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

79 packages

found in

Top 10k

9.13k packages

in community

Next steps

In most cases, it's recommended to use full read-only relocations (in GCC: -Wl,-z,relro,-z,now).

If the executable load-time is an issue, you should use partial read-only relocations.

Problem

Prevalence in npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

119 packages

found in

Top 10k

14.5k packages

in community

Next steps

Strip out such information in the linking phase by using compiler options like the -s flag in GCC, or in the post-build phase by using the strip tool.

Problem

Prevalence in npm community

5 packages

found in

Top 100

21 packages

found in

Top 1k

374 packages

found in

Top 10k

113.9k 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 npm community

2 packages

found in

Top 100

6 packages

found in

Top 1k

181 packages

found in

Top 10k

39.81k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1033 - System Owner/User Discovery.

snyk

SAFE Assessment

Compliance

Security

Threats

SQ25102Detected packages with content that may be incomplete or corrupted.integrity

Problem

Prevalence in npm community

Next steps

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

Problem

Prevalence in npm community

Next steps

SQ18106Detected Linux executable files compiled without any kind of buffer overrun protection while using banned memory functions.Causes risk: misconfigured toolchains detectedhardening

Problem

Prevalence in npm community

Next steps

SQ18107Detected Linux executable files compiled without any kind of buffer overrun protection while using banned input functions.Causes risk: misconfigured toolchains detectedhardening

Problem

Prevalence in npm community

Next steps

SQ34302Detected presence of plaintext credentials within network protocol strings.Causes risk: web service credentials foundsecrets

Problem

Prevalence in npm community

Next steps

TH17119Detected presence of files containing URLs with suspicious path components.hunting

Problem

Prevalence in npm community

Next steps

SQ18113Detected Linux executable files that were compiled without the recommended dynamic symbol hijacking protections.Causes risk: execution hijacking concernshardening

Problem

Prevalence in npm community

Next steps

SQ34204Detected presence of hardcoded source code filenames or paths.Causes risk: debugging symbols foundsecrets

Problem

Prevalence in npm community

Next steps

TH16102Detected presence of files containing bidirectional Unicode control characters.hunting

Problem

Prevalence in npm community

Next steps

TH16126Detected presence of software components that can access user identity information.hunting

Problem

Prevalence in npm community

Next steps

Did you know...

SQ25102Detected packages with content that may be incomplete or corrupted.integrity

Problem

Prevalence in npm community

Next steps

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

Problem

Prevalence in npm community

Next steps

SQ18106Detected Linux executable files compiled without any kind of buffer overrun protection while using banned memory functions.Causes risk: misconfigured toolchains detectedhardening

Problem

Prevalence in npm community

Next steps

SQ18107Detected Linux executable files compiled without any kind of buffer overrun protection while using banned input functions.Causes risk: misconfigured toolchains detectedhardening

Problem

Prevalence in npm community

Next steps

SQ34302Detected presence of plaintext credentials within network protocol strings.Causes risk: web service credentials foundsecrets

Problem

Prevalence in npm community

Next steps

TH17119Detected presence of files containing URLs with suspicious path components.hunting

Problem

Prevalence in npm community

Next steps

SQ18113Detected Linux executable files that were compiled without the recommended dynamic symbol hijacking protections.Causes risk: execution hijacking concernshardening

Problem

Prevalence in npm community

Next steps

SQ34204Detected presence of hardcoded source code filenames or paths.Causes risk: debugging symbols foundsecrets

Problem

Prevalence in npm community

Next steps

TH16102Detected presence of files containing bidirectional Unicode control characters.hunting

Problem