Supply-chain attacks move fast. We stay ahead.

Free campaign tracking

Spectra Assure

Community

Toolbox

Explore

Learn

ReversingLabs

Spectra Assure

Community

npm

Search by package name, PURL or hash

failIncident: Malware

Scanned:

@nx/node

removed

malicious

Research

The Node Plugin for Nx contains generators to manage Node applications within an Nx workspace.

License: Permissive (MIT)

Published:

Visit GitHub

See on npm

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

1 critical severity vulnerabilities

Hardening

No application hardening issues

Threats

Tampering

2 malware-like behaviors found

Malware

4 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

malware

Reported By: Community (StepSecurity)

More info

malware

Reported By: Community (jahredhope)

More info

malware

Reported By: Community (FrozenPandaz)

More info

malware

Reported By: Community (GitHub Advisory)

More info

malware

Reported By: Community (Wiz)

More info

malware

Reported By: Community (Socket)

More info

malware

Reported By: Community (OpenSSF)

More info

removal

Reported By: Community

malware

Reported By: ReversingLabs (Researcher)

Learn more about malware detection

Overview issues6 vulnerabilities1 malware4 behaviors27 dependencies5 contributors8 versions1977

Popularity

121.03M

Recorded Downloads Since 2021

Contributors

Declared Dependencies

158

Dependents

Top issues

See all issues

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

14 packages

found in

Top 1k

38 packages

found in

Top 10k

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

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

9 packages

found in

Top 100

12 packages

found in

Top 1k

35 packages

found in

Top 10k

35.68k packages

in community

Next steps

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

Avoid using this software package.

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

8 packages

found in

Top 100

57 packages

found in

Top 1k

1010 packages

found in

Top 10k

466.07k packages

in community

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 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 exclusively used by malicious software with the intent to cause harm. When a software package matches behavior traits of malicious software, it becomes flagged by security solutions. It is highly likely that the software package was tampered with by a malicious actor or a rogue insider. Detected threat type matches the behaviors typically exhibited by the infostealer malware profile. Infostealers are commonly used to steal sensitive user data such as stored login details, financial information, and other personally identifiable information.

Prevalence in npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

14 packages

found in

Top 10k

16.61k packages

in community

Next steps

Investigate reported detections.

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

You should delay the software release until the investigation is completed.

In the case this behavior is intended, rewrite the flagged code without using the malware-like behaviors.

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. Node Package Manager (NPM) repository is often abused by threat actors to publish software packages that exhibit malicious behaviors. Malware authors use numerous tactics to lure developers into including malicious NPM packages in their software projects. Most malicious packages published on NPM target developers and their workstations. However, some are designed to activate only when deployed in the end-user environment. Both types of NodeJS malicious packages are detected by proprietary ReversingLabs threat hunting algorithms. This detection method is considered proactive, and it is based on Machine Learning (ML) algorithms that can detect novel malware. 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 software packages to be detected by this policy.

Prevalence in npm community

1 packages

found in

Top 100

11 packages

found in

Top 1k

67 packages

found in

Top 10k

74.4k 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 often found in this community (Common)

8 packages

found in

Top 100

69 packages

found in

Top 1k

1020 packages

found in

Top 10k

476.28k packages

in community

Prevalence in npm community

Behavior often found in this community (Common)

11 packages

found in

Top 100

58 packages

found in

Top 1k

1021 packages

found in

Top 10k

269.45k packages

in community

Prevalence in npm community

Behavior often found in this community (Common)

95 packages

found in

Top 100

729 packages

found in

Top 1k

7513 packages

found in

Top 10k

5.23M packages

in community

Prevalence in npm community

Behavior often found in this community (Common)

16 packages

found in

Top 100

55 packages

found in

Top 1k

623 packages

found in

Top 10k

267.49k packages

in community

Prevalence in npm community

Behavior often found in this community (Common)

5 packages

found in

Top 100

23 packages

found in

Top 1k

411 packages

found in

Top 10k

98.85k packages

in community

Top vulnerabilities

See all vulnerabilities

Vulnerability Exploitation Lifecycle

(1 Active Vulnerabilities)

1 (1 Fixable)

CVE-2025-10894c

None

Exploits Unknown

Exploits Exist

Exploited by Malware

Patching Mandated

FAQ for @nx/node

What is @nx/node?

The Node Plugin for Nx contains generators to manage Node applications within an Nx workspace. For more information about this package, visit its homepage.

Is @nx/node malicious or is it safe to use?

The npm package @nx/node 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. 3 other issues and risky behaviors were 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. There have been 2 compromised malicious versions of @nx/node. The most recent was 20.9.0 1 year ago.

Does @nx/node have known vulnerabilities?

Yes, we detected 1 critical severity vulnerability, including CVE-2025-10894. Explore the Vulnerabilities tab for more information.

Is @nx/node popular?

The npm package @nx/node is not widely used. It has 121M 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.

Read our best practices for protecting your software supply chain guide.

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.

Popularity

121.03M

Recorded Downloads Since 2021

Contributors

Declared Dependencies

158

Dependents

Top issues

See all issues

Problem

Prevalence in npm community

9 packages

found in

Top 100

14 packages

found in

Top 1k

38 packages

found in

Top 10k

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

9 packages

found in

Top 100

12 packages

found in

Top 1k

35 packages

found in

Top 10k

35.68k packages

in community

Next steps

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

Avoid using this software package.

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

8 packages

found in

Top 100

57 packages

found in

Top 1k

1010 packages

found in

Top 10k

466.07k packages

in community

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

Prevalence in npm community

0 packages

found in

Top 100

1 packages

found in

Top 1k

14 packages

found in

Top 10k

16.61k packages

in community

Next steps

Investigate reported detections.

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

You should delay the software release until the investigation is completed.

In the case this behavior is intended, rewrite the flagged code without using the malware-like behaviors.

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. Node Package Manager (NPM) repository is often abused by threat actors to publish software packages that exhibit malicious behaviors. Malware authors use numerous tactics to lure developers into including malicious NPM packages in their software projects. Most malicious packages published on NPM target developers and their workstations. However, some are designed to activate only when deployed in the end-user environment. Both types of NodeJS malicious packages are detected by proprietary ReversingLabs threat hunting algorithms. This detection method is considered proactive, and it is based on Machine Learning (ML) algorithms that can detect novel malware. 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 software packages to be detected by this policy.

Prevalence in npm community

1 packages

found in

Top 100

11 packages

found in

Top 1k

67 packages

found in

Top 10k

74.4k 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 often found in this community (Common)

8 packages

found in

Top 100

69 packages

found in

Top 1k

1020 packages

found in

Top 10k

476.28k packages

in community

Prevalence in npm community

Behavior often found in this community (Common)

11 packages

found in

Top 100

58 packages

found in

Top 1k

1021 packages

found in

Top 10k

269.45k packages

in community

Prevalence in npm community

Behavior often found in this community (Common)

95 packages

found in

Top 100

729 packages

found in

Top 1k

7513 packages

found in

Top 10k

5.23M packages

in community

Prevalence in npm community

Behavior often found in this community (Common)

16 packages

found in

Top 100

55 packages

found in

Top 1k

623 packages

found in

Top 10k

267.49k packages

in community

Prevalence in npm community

Behavior often found in this community (Common)

5 packages

found in

Top 100

23 packages

found in

Top 1k

411 packages

found in

Top 10k

98.85k packages

in community

Top vulnerabilities

See all vulnerabilities

Vulnerability Exploitation Lifecycle

(1 Active Vulnerabilities)

1 (1 Fixable)

CVE-2025-10894c

None

Exploits Unknown

Exploits Exist

Exploited by Malware

Patching Mandated

@nx/node

SAFE Assessment

Compliance

Security

Threats

IMPORTANT: This package had 2 malicious incidents in versions published within 2 years prior to the latestLatest version with malware incident detected: about 1 year agoVersion: 20.9.0

INCIDENTS FOR THIS VERSION:

Popularity

Top issues

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

Problem

Prevalence in npm community

Next steps

SQ30109Detected presence of malicious files through analyst-vetted file reputation.Causes risk: analyst-vetted malware foundthreats

Problem

Prevalence in npm community

Next steps

SQ31104Detected presence of critical severity vulnerabilities.Causes risk: critical severity vulnerabilitiesvulnerabilities

Problem

Prevalence in npm community

Next steps

TH15108Detected presence of files with behaviors that match the infostealer malware profile.Causes risk: malware-like behaviors foundhunting

Problem

Prevalence in npm community

Next steps

TH15502Detected presence of files with behaviors similar to malicious packages published on NPM.Causes risk: suspicious application behaviorshunting

Problem

Prevalence in npm community

Next steps

Top behaviors

Encodes data using the Base64 algorithm.packer

Prevalence in npm community

Contains URLs that link to raw files on GitHub.network

Prevalence in npm community

Executes files during installation or upon launch.execution

Prevalence in npm community

Creates a process.execution

Prevalence in npm community

Enumerates the operating system platform.search

Prevalence in npm community

Top vulnerabilities

FAQ for @nx/node

What is @nx/node?

Is @nx/node malicious or is it safe to use?

Does @nx/node have known vulnerabilities?

Is @nx/node popular?

Did you know...

Popularity

Top issues

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

Problem

Prevalence in npm community

Next steps

SQ30109Detected presence of malicious files through analyst-vetted file reputation.Causes risk: analyst-vetted malware foundthreats

Problem

Prevalence in npm community

Next steps

SQ31104Detected presence of critical severity vulnerabilities.Causes risk: critical severity vulnerabilitiesvulnerabilities

Problem

Prevalence in npm community

Next steps

TH15108Detected presence of files with behaviors that match the infostealer malware profile.Causes risk: malware-like behaviors foundhunting

Problem

Prevalence in npm community

Next steps

TH15502Detected presence of files with behaviors similar to malicious packages published on NPM.Causes risk: suspicious application behaviorshunting

Problem

Prevalence in npm community

Next steps

Top behaviors

Encodes data using the Base64 algorithm.packer

Prevalence in npm community

Contains URLs that link to raw files on GitHub.network

Prevalence in npm community

Executes files during installation or upon launch.execution

Prevalence in npm community

Creates a process.execution

Prevalence in npm community

Enumerates the operating system platform.search

Prevalence in npm community