Spectra Assure

failIncident: Malware

Scanned:

n8n-nodes-gg-udhasudsh-hgjkhg-official

latest

removed

malicious

Research

security holding package

License: unknown

Published:

Visit GitHub

See on npm

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

1 components prone to hijacking

Malware

1 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

malware

Reported By: ReversingLabs (Researcher)

Learn more about malware detection

removal

Reported By: Community

malware

Reported By: Community (GitHub Advisory)

More info

malware

Reported By: Community (OpenSSF)

More info

malware

Reported By: ReversingLabs (Automated)

Learn more about malware detection

Popularity

11.5k

Recorded Downloads Since 2021

Contributor

Declared Dependencies

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

0 packages

found in

Top 100

3 packages

found in

Top 1k

16 packages

found in

Top 10k

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

9 packages

found in

Top 100

9 packages

found in

Top 1k

37 packages

found in

Top 10k

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

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. Software developers publish components they have authored to public repositories. Open source projects are the intellectual property of their respective authors. At any time, the authors may choose to completely remove the software component from a public repository. This often occurs when a software project reaches its end-of-life stage, or when the software authors lose interest in maintaining the project. This kind of removal frees up the software package name, its unique software identifier in the public repository, for other developers to use. However, new software project owners might have malicious intent. Threat actors are continuously monitoring popular package names in case their unique identifiers suddenly become available for hijacking. Once the software projects falls under new ownership, the new maintainers may opt to use the project popularity to spread malware to unsuspecting users.

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

6 packages

found in

Top 10k

516.56k 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 that their versions are pinned.

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

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. Software developers publish components they have authored to public repositories. Developers that use open source components within their applications can specify the exact version of the component their application depends on. However, since components are frequently updated, some developers opt to always use the latest version of the software component. This helps reduce the number of vulnerabilities that open source components can introduce in the application. However, it does expose the developer and the build environment to risks associated with software supply chain attacks. Should a threat actor hijack the ownership of the software component publishing account, or even its publishing token, they could issue a malicious update that can infect the build environment or the application itself. To ensure that the build system updates the software component to a malicious version, threat actors often set the version number to an unusually high value. If a build system is instructed to use the latest component version, it will install the component with the highest version number, and execute its code.

Prevalence in npm community

1 packages

found in

Top 100

2 packages

found in

Top 1k

47 packages

found in

Top 10k

160.89k packages

in community

Next steps

Review software component versions to ensure there were no accidental code updates.

If the software component versions differ from expected, investigate the build and release environment for software supply chain compromise.

Consider pinning the software component version to prevent accidental code updates.

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

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

9 packages

found in

Top 100

29 packages

found in

Top 1k

255 packages

found in

Top 10k

95.32k 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.

Top behaviors

See all behaviors

Prevalence in npm community

Behavior commonly used by malicious software (Important)

Behavior often found in this community (Common)

1 packages

found in

Top 100

2 packages

found in

Top 1k

47 packages

found in

Top 10k

160.89k packages

in community

Top vulnerabilities

No vulnerabilities found.

FAQ for n8n-nodes-gg-udhasudsh-hgjkhg-official

What is n8n-nodes-gg-udhasudsh-hgjkhg-official?

security holding package.

Is n8n-nodes-gg-udhasudsh-hgjkhg-official malicious or is it safe to use?

The npm package n8n-nodes-gg-udhasudsh-hgjkhg-official has been removed from registry. It was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. Malware or tampering has been detected, making it unsafe to use. 1 other issue and risky behavior was found. The package contains risks, and the analysis results should be reviewed before it is used. Visit the Issues and Behaviors sections of the analysis for more details. All versions of the n8n-nodes-gg-udhasudsh-hgjkhg-official package were malicious.

Is n8n-nodes-gg-udhasudsh-hgjkhg-official popular?

The npm package n8n-nodes-gg-udhasudsh-hgjkhg-official is not widely used. It has 11K 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 n8n-nodes-gg-udhasudsh-hgjkhg-official once it is in my app?

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

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.

Popularity

11.5k

Recorded Downloads Since 2021

Contributor

Declared Dependencies

Dependents

Top issues

See all issues

Problem

Prevalence in npm community

0 packages

found in

Top 100

3 packages

found in

Top 1k

16 packages

found in

Top 10k

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

Prevalence in npm community

9 packages

found in

Top 100

9 packages

found in

Top 1k

37 packages

found in

Top 10k

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

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

6 packages

found in

Top 10k

516.56k 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 that their versions are pinned.

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

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. Software developers publish components they have authored to public repositories. Developers that use open source components within their applications can specify the exact version of the component their application depends on. However, since components are frequently updated, some developers opt to always use the latest version of the software component. This helps reduce the number of vulnerabilities that open source components can introduce in the application. However, it does expose the developer and the build environment to risks associated with software supply chain attacks. Should a threat actor hijack the ownership of the software component publishing account, or even its publishing token, they could issue a malicious update that can infect the build environment or the application itself. To ensure that the build system updates the software component to a malicious version, threat actors often set the version number to an unusually high value. If a build system is instructed to use the latest component version, it will install the component with the highest version number, and execute its code.

Prevalence in npm community

1 packages

found in

Top 100

2 packages

found in

Top 1k

47 packages

found in

Top 10k

160.89k packages

in community

Next steps

Review software component versions to ensure there were no accidental code updates.

If the software component versions differ from expected, investigate the build and release environment for software supply chain compromise.

Consider pinning the software component version to prevent accidental code updates.

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

Problem

Prevalence in npm community

9 packages

found in

Top 100

29 packages

found in

Top 1k

255 packages

found in

Top 10k

95.32k 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.

Top behaviors

See all behaviors

Prevalence in npm community

Behavior commonly used by malicious software (Important)

Behavior often found in this community (Common)

1 packages

found in

Top 100

2 packages

found in

Top 1k

47 packages

found in

Top 10k

160.89k packages

in community

Top vulnerabilities

No vulnerabilities found.

n8n-nodes-gg-udhasudsh-hgjkhg-official

SAFE Assessment

Compliance

Security

Threats

IMPORTANT: All versions of this package have been maliciousLatest version with malware incident detected: 3 months agoVersion: 0.0.1-security

INCIDENTS FOR THIS VERSION:

Popularity

Top issues

SQ30103Detected presence of potentially unwanted applications.Causes risk: undesirable applications foundthreats

Problem

Prevalence in npm community

Next steps

SQ30105Detected presence of known software supply chain attack artifacts.Causes risk: supply chain attack artifactsthreats

Problem

Prevalence in npm community

Next steps

TH30103Detected presence of software components that were removed from the public package repository.Causes risk: components prone to hijackinghunting

Problem

Prevalence in npm community

Next steps

TH30113Detected presence of software components with unusual package versions.hunting

Problem

Prevalence in npm community

Next steps

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

Problem

Prevalence in npm community

Next steps

Top behaviors

The software package is published with an unusual version number.anomaly

Prevalence in npm community

Top vulnerabilities

FAQ for n8n-nodes-gg-udhasudsh-hgjkhg-official

What is n8n-nodes-gg-udhasudsh-hgjkhg-official?

Is n8n-nodes-gg-udhasudsh-hgjkhg-official malicious or is it safe to use?

Is n8n-nodes-gg-udhasudsh-hgjkhg-official popular?

How do I secure n8n-nodes-gg-udhasudsh-hgjkhg-official once it is in my app?

Did you know...

Popularity

Top issues

SQ30103Detected presence of potentially unwanted applications.Causes risk: undesirable applications foundthreats

Problem

Prevalence in npm community

Next steps

SQ30105Detected presence of known software supply chain attack artifacts.Causes risk: supply chain attack artifactsthreats

Problem

Prevalence in npm community

Next steps

TH30103Detected presence of software components that were removed from the public package repository.Causes risk: components prone to hijackinghunting

Problem

Prevalence in npm community

Next steps

TH30113Detected presence of software components with unusual package versions.hunting

Problem

Prevalence in npm community

Next steps

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

Problem

Prevalence in npm community

Next steps

Top behaviors

The software package is published with an unusual version number.anomaly

Prevalence in npm community

Top vulnerabilities