Spectra Assure

Toolbox

Explore

Learn

ReversingLabs

Spectra Assure

Community

npm

Search by package name, PURL or hash

failIncident: Malware

Scanned:

ng2-file-upload

removed

malicious

Top 30k

Research

Angular file uploader

License: Permissive (MIT)

Published:

See on npm

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

8 high severity vulnerabilities

Hardening

No application hardening issues

Threats

Tampering

1 restricted network references

Malware

4 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

malware

Reported By: Community (Socket)

More info

malware

Reported By: Community (StepSecurity)

More info

malware

Reported By: Community (Semgrep)

More info

malware

Reported By: Community (GitHub Advisory)

More info

malware

Reported By: Community (patlkli)

More info

malware

Reported By: ReversingLabs (Researcher)

See more info on our blog

removal

Reported By: Community

malware

Reported By: Community (Aikido)

More info

malware

Reported By: Community (OpenSSF)

More info

malware

Reported By: Community (Wiz)

More info

malware

Reported By: Community (Checkmarx)

More info

malware

Reported By: Community (Sonatype)

More info

Overview issues9 vulnerabilities10 malware4 behaviors80 dependencies3 contributors4 versions37

Popularity

23.77M

Recorded Downloads Since 2021

Contributors

Declared Dependencies

542

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

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

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

7 packages

found in

Top 1k

26 packages

found in

Top 10k

19.19k packages

in community

Next steps

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

Avoid using this software package.

Problem

Uniform Resource Locators (URLs) are structured addresses that point to locations and assets on the internet. URLs allow software developers to build complex applications that exchange data with servers that can be hosted in multiple geographical regions. URLs can commonly be found embedded in documentation, configuration files, source code and compiled binaries. One or more embedded URLs were discovered to link to an address known to distribute hacking tools. Hacking tools are commonly used by malicious actors to bypass security solutions, exploit system weaknesses, collect personal information, and exfiltrate data. Software components that contain links to network locations distributing hacking tools are reported as malicious.

Prevalence in npm community

No prevalence information at this time

Next steps

Investigate reported detections.

Consult Mitre ATT&CK documentation: T1588.002 - Obtain Capabilities: Tool.

If the software should not include these network references, 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.

Remove all references to flagged network locations.

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

22 packages

found in

Top 100

114 packages

found in

Top 1k

1440 packages

found in

Top 10k

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

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

5 packages

found in

Top 100

2 packages

found in

Top 1k

39 packages

found in

Top 10k

21.37k packages

in community

Next steps

CVE-2026-54267h

None

Exploits Unknown

Exploits Exist

Exploited by Malware

Patching Mandated

FAQ for ng2-file-upload

What is ng2-file-upload?

Angular file uploader. For more information about this package, visit its homepage.

Is ng2-file-upload malicious or is it safe to use?

The npm package ng2-file-upload 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. The package ng2-file-upload had 6 incidents in versions published within 2 years prior to the latest.

Is ng2-file-upload popular?

The npm package ng2-file-upload ranks among the top 30000 projects in this community. It has 24M 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 ng2-file-upload once it is in my app?

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

23.77M

Recorded Downloads Since 2021

Contributors

Declared Dependencies

542

Dependents

Top issues

See all issues

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

9 packages

found in

Top 100

7 packages

found in

Top 1k

26 packages

found in

Top 10k

19.19k packages

in community

Next steps

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

Avoid using this software package.

Problem

Prevalence in npm community

No prevalence information at this time

Next steps

Investigate reported detections.

Consult Mitre ATT&CK documentation: T1588.002 - Obtain Capabilities: Tool.

If the software should not include these network references, 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.

Remove all references to flagged network locations.

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

22 packages

found in

Top 100

114 packages

found in

Top 1k

1440 packages

found in

Top 10k

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

Problem

Prevalence in npm community

5 packages

found in

Top 100

2 packages

found in

Top 1k

39 packages

found in

Top 10k

21.37k packages

in community

Next steps

CVE-2026-54267h

None

Exploits Unknown

Exploits Exist

Exploited by Malware

Patching Mandated

ng2-file-upload

SAFE Assessment

Compliance

Security

Threats

IMPORTANT: This package had 6 malicious incidents in versions published within 2 years prior to the latestLatest version with malware incident detected: 11 months agoVersion: 7.0.3

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

TH17134Detected presence of files containing URLs that are used to distribute hacktools.Causes risk: restricted network referenceshunting

Problem

Prevalence in npm community

Next steps

SQ31105Detected presence of high severity vulnerabilities.Causes risk: high severity vulnerabilitiesvulnerabilities

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

Enumerates an environment variable that holds an Amazon Web Services (AWS) session token.search

Prevalence in npm community

Enumerates an environment variable that holds an Amazon Web Services (AWS) secret access key.search

Prevalence in npm community

Enumerates an environment variable that holds an Amazon Web Services (AWS) access key.search

Prevalence in npm community

Might contain potentially obfuscated code or data.anomaly

Prevalence in npm community

Enumerates an environment variable that holds an Amazon Web Services (AWS) web identity token location.search

Prevalence in npm community

Top vulnerabilities

FAQ for ng2-file-upload

What is ng2-file-upload?

Is ng2-file-upload malicious or is it safe to use?

Is ng2-file-upload popular?

How do I secure ng2-file-upload once it is in my app?

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

TH17134Detected presence of files containing URLs that are used to distribute hacktools.Causes risk: restricted network referenceshunting

Problem

Prevalence in npm community

Next steps

SQ31105Detected presence of high severity vulnerabilities.Causes risk: high severity vulnerabilitiesvulnerabilities

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

Enumerates an environment variable that holds an Amazon Web Services (AWS) session token.search

Prevalence in npm community

Enumerates an environment variable that holds an Amazon Web Services (AWS) secret access key.search

Prevalence in npm community

Enumerates an environment variable that holds an Amazon Web Services (AWS) access key.search

Prevalence in npm community

Might contain potentially obfuscated code or data.anomaly

Prevalence in npm community

Enumerates an environment variable that holds an Amazon Web Services (AWS) web identity token location.search

Prevalence in npm community