Spectra Assure

failIncident: Removal

Scanned:

legacyreact-aws-s3-typescript

latest

removed

security holding package

License: unknown

Published:

Visit GitHub

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 components with malware history

Malware

No evidence of malware inclusion

IMPORTANT: All versions of this package have been malicious

Latest malware incident detected:

Version: 1.2.4

INCIDENTS FOR THIS VERSION:

removal

Reported By: Community

List of software quality issues with the number of affected components.

Policies

Info

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.

TH30106

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

hunting

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.

TH30113

Detected presence of software components with unusual package versions.

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

TH15103

Detected presence of files with behaviors commonly used by malicious software.

hunting

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

9 packages

found in

Top 100

29 packages

found in

Top 1k

255 packages

found in

Top 10k

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

TH30107

Detected presence of software components that are rarely included by other public software packages.

hunting

Problem

Prevalence in npm community

1 packages

found in

Top 100

2 packages

found in

Top 1k

66 packages

found in

Top 10k

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

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.

List of software quality issues with the number of affected components.

Policies

Info

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.

TH30106

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

hunting

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.

TH30113

Detected presence of software components with unusual package versions.

hunting

Problem

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.

TH15103

Detected presence of files with behaviors commonly used by malicious software.

hunting

Problem

Prevalence in npm community

9 packages

found in

Top 100

29 packages

found in

Top 1k

255 packages

found in

Top 10k

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

TH30107

Detected presence of software components that are rarely included by other public software packages.

hunting

Problem

Prevalence in npm community

1 packages

found in

Top 100

2 packages

found in

Top 1k

66 packages

found in

Top 10k

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