Spectra Assure
Community
failIncident: Malware
Scanned: 4 days ago

@art-ws/fastify-http-server

Fastify Http server
License: unknown
Published: 4 months ago



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 suspicious application behaviors
Malware
4 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

malware
4 months agoReported By: Community (Socket)
malware
4 months agoReported By: Community (StepSecurity)
malware
4 months agoReported By: Community (Semgrep)
malware
4 months agoReported By: Community (Aikido)
malware
4 months agoReported By: ReversingLabs (Researcher)
See more info on our blog
malware
4 months agoReported By: Community (Wiz)
malware
4 months agoReported By: Community (Checkmarx)
malware
4 months agoReported By: Community (Sonatype)
malware
4 months agoReported By: Community (GitHub Advisory)
malware
4 months agoReported By: Community (OpenSSF)
malware
4 months agoReported By: ReversingLabs (Automated)
Learn more about malware detection
removal
N/AReported By: Community

Popularity

3.05k
Recorded Downloads Since 2021
Contributor
Declared Dependencies
2
Dependents

Top issues

Problem

Potentially unwanted applications (PUAs) can be considered a risk by some software users. This threat type typically collects private user data, or in more extreme cases, tampers with system security settings. Most threat prevention solutions detect and block PUAs. Software packages that trigger security solution detections also tend to increase the number of support calls and open tickets from users.

Prevalence in npm community

0 packages
found in
Top 100
3 packages
found in
Top 1k
16 packages
found in
Top 10k
8.13k packages
in community

Next steps

Revise the use of components that raise these alarms. If you can't deprecate those components, make sure they are well-documented.

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

Potentially unwanted applications (PUAs) can be considered a risk by some software users. This threat type typically collects private user data, or in more extreme cases, tampers with system security settings. Most threat prevention solutions detect and block PUAs. Some software dependencies may be optional, and could be installed or downloaded only if a certain pre-defined condition is met. When software dependencies are confirmed to be found within the software package, additional issues might also be reported. Software packages that trigger security solution detections also tend to increase the number of support calls and open tickets from users.

Prevalence in npm community

0 packages
found in
Top 100
0 packages
found in
Top 1k
0 packages
found in
Top 10k
5.48k packages
in community

Next steps

Revise the use of components that raise these alarms. If you can't deprecate those components, make sure they are well-documented.

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

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

Prevalence in npm community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
19 packages
found in
Top 10k
2.71k packages
in community

Prevalence in npm community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
21 packages
found in
Top 10k
2.85k packages
in community

Prevalence in npm community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
18 packages
found in
Top 10k
2.86k packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
22 packages
found in
Top 100
136 packages
found in
Top 1k
1267 packages
found in
Top 10k
411.22k packages
in community

Prevalence in npm community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
15 packages
found in
Top 10k
2.32k packages
in community

Top vulnerabilities

No vulnerabilities found.