Our AI threat analyst detects malicious packages and blogs about OSS compromises
7000 write-ups and countingRead one

Spectra Assure

Toolbox

Explore

Learn

ReversingLabs

Spectra Assure

Community

npm

Search by package name, PURL or hash

Quarantine

Scanned:

networkx

latest

removed

security holding package

License: unknown

Published:

Visit source repository

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 quarantined components found

Malware

No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

removal

Reported By: Community

Overview issues7 vulnerabilities0 malware0 behaviors1 dependencies0 contributors1 versions19

FAQ for networkx

What is networkx?

security holding package.

Is networkx malicious or is it safe to use?

The npm package networkx 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. 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 networkx package were malicious.

Is networkx popular?

The npm package networkx is not widely used. It has 3K 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 networkx once it is in my app?

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

Popularity

2.55k

Recorded Downloads Since 2021

Contributor

Declared Dependencies

Dependents

Top issues

See all issues

Problem

Prevalence in npm community

No prevalence information at this time

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 they are well-documented.

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

Problem

Prevalence in npm community

10 packages

found in

Top 100

14 packages

found in

Top 1k

81 packages

found in

Top 10k

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

Prevalence in npm community

2 packages

found in

Top 100

6 packages

found in

Top 1k

99 packages

found in

Top 10k

4.51M 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.

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.

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.

networkx

SAFE Assessment

Compliance

Security

Threats

IMPORTANT: All versions of this package have been maliciousLatest version with malware incident detected: over 1 year agoVersion: 1.0.0

INCIDENTS FOR THIS VERSION:

FAQ for networkx

What is networkx?

Is networkx malicious or is it safe to use?

Is networkx popular?

How do I secure networkx once it is in my app?

Did you know...

Popularity

Top issues

TH30102Detected presence of software components that are quarantined in the community package index.Causes risk: quarantined components foundhunting

Problem

Prevalence in npm community

Next steps

TH30101Detected presence of software components that had a recent malware or tampering incident.Causes risk: components with malware historyhunting

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

TH30106Detected presence of software components that have low popularity or number of downloads.hunting

Problem

Prevalence in npm community

Next steps

TH30113Detected presence of software components with unusual package versions.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