Top issues
Detected presence of known software supply chain attack artifacts.
Causes risk: supply chain attack artifacts
threats
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 NuGet community
0 packages
found in
Top 100
0 packages
found in
Top 1k
0 packages
found in
Top 10k
741 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.
Detected presence of malicious files through analyst-vetted file reputation.
Causes risk: analyst-vetted malware found
threats
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 NuGet community
0 packages
found in
Top 100
0 packages
found in
Top 1k
0 packages
found in
Top 10k
741 packages
in community
Next steps
Investigate the build and release environment for software supply chain compromise.
Avoid using this software package.
Detected presence of high severity vulnerabilities.
Causes risk: high severity vulnerabilities
vulnerabilities
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 high severity.Prevalence in NuGet community
0 packages
found in
Top 100
4 packages
found in
Top 1k
115 packages
found in
Top 10k
88612 packages
in community
Next steps
Perform impact analysis for the reported CVEs.
Update the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.
Detected presence of software components that were removed from the public package repository.
Causes risk: components prone to hijacking
hunting
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 NuGet community
No prevalence information at this timeNext 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 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 NuGet community
0 packages
found in
Top 100
0 packages
found in
Top 1k
4 packages
found in
Top 10k
1095 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
Executes a file.
execution
Prevalence in NuGet community
Behavior often found in this community (Common)
0 packages
found in
Top 100
12 packages
found in
Top 1k
98 packages
found in
Top 10k
39014 packages
in community
Checks operating system version.
search
Prevalence in NuGet community
Behavior often found in this community (Common)
0 packages
found in
Top 100
9 packages
found in
Top 1k
67 packages
found in
Top 10k
16582 packages
in community
Downloads a file.
network
Prevalence in NuGet community
Behavior often found in this community (Common)
0 packages
found in
Top 100
17 packages
found in
Top 1k
100 packages
found in
Top 10k
34755 packages
in community
Contains IP addresses.
network
Prevalence in NuGet community
Behavior often found in this community (Common)
0 packages
found in
Top 100
59 packages
found in
Top 1k
458 packages
found in
Top 10k
532614 packages
in community
Queries information about a display monitor.
search
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
12 packages
found in
Top 10k
3957 packages
in community
Top vulnerabilities
Vulnerability Exploitation Lifecycle
(2 Active Vulnerabilities)
2 (2 Fixable)
CVE-2024-30105h
CVE-2024-43485h
None
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated