From 100k to 1M lookups per month for just $99/year.

New Community+ plan

Spectra Assure

Community

Toolbox

Explore

Learn

ReversingLabs

Spectra Assure

Community

npm

Search by package name, PURL or hash

Quarantine

Scanned:

node-dlls

latest

removed

malicious

Research

Advanced kernel package

License: Permissive (ISC)

Published:

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

4 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

removal

Reported By: Community

malware

Reported By: ReversingLabs (Researcher)

Learn more about malware detection

malware

Reported By: Community (OpenSSF)

More info

malware

Reported By: Community (Snyk)

More info

malware

Reported By: Community (Socket)

More info

malware

Reported By: Community (The Hacker News)

More info

Overview issues10 vulnerabilities0 malware4 behaviors4 dependencies0 contributors1 versions1

FAQ for node-dlls

What is node-dlls?

Advanced kernel package.

Is node-dlls malicious or is it safe to use?

The npm package node-dlls 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 node-dlls package were malicious. There has been 1 compromised malicious version of node-dlls. The most recent was 1.0.0 2 years ago.

Does node-dlls have known vulnerabilities?

No vulnerabilities have been detected for this version of node-dlls.

Is node-dlls popular?

The npm package node-dlls is not widely used. It has 77 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.

node-dlls@1.0.0 Malicious npm package analysis | ReversingLabs Spectra Assure Community

Popularity

Recorded Downloads Since 2021

Contributor

Declared Dependencies

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 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. The ReversingLabs community package index may place software packages into quarantine during an ongoing security incident investigation. When a software project is placed into quarantine, it is typically unavailable for installation. Additionally, repository maintainers may also hide quarantined software projects from users that might stumble upon them using repository search functions. Quarantine is typically raised for software projects that were reported for unusual code changes or unexpected software behaviors.

Prevalence in npm community

1 packages

found in

Top 100

2 packages

found in

Top 1k

36 packages

found in

Top 10k

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

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

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

1 packages

found in

Top 100

2 packages

found in

Top 1k

47 packages

found in

Top 10k

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

Top behaviors

See all behaviors

Prevalence in npm community

Behavior commonly used by malicious software (Important)

Behavior often found in this community (Common)

9 packages

found in

Top 100

6 packages

found in

Top 1k

16 packages

found in

Top 10k

12.81k 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)

17 packages

found in

Top 100

145 packages

found in

Top 1k

1822 packages

found in

Top 10k

3.31M packages

in community

Prevalence in npm community

Behavior often found in this community (Common)

7 packages

found in

Top 100

15 packages

found in

Top 1k

335 packages

found in

Top 10k

91.83k packages

in community

Top vulnerabilities

No vulnerabilities found.

node-dlls

SAFE Assessment

Compliance

Security

Threats

IMPORTANT: All versions of this package have been maliciousLatest version with malware incident detected: about 2 years agoVersion: 1.0.0

INCIDENTS FOR THIS VERSION:

FAQ for node-dlls

What is node-dlls?

Is node-dlls malicious or is it safe to use?

Does node-dlls have known vulnerabilities?

Is node-dlls 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

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

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

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

Top behaviors

Contains potentially obfuscated code or data.packer

Prevalence in npm community

Executes files during installation or upon launch.execution

Prevalence in npm community

The software package does not declare any source code repository.anomaly

Prevalence in npm community

Contains a reference to a common dynamic library or an executable file.execution

Prevalence in npm community

Top vulnerabilities