Our AI threat analyst detects malicious packages and blogs about OSS compromises
7000 write-ups and countingRead one

Spectra Assure

Toolbox

Explore

Learn

ReversingLabs

Spectra Assure

Community

npm

Search by package name, PURL or hash

failIncident: Malware

Scanned:

strip-ansi

removed

malicious

Top 10

Research

Strip ANSI escape codes from a string

License: Permissive (MIT)

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

No evidence of software tampering

Malware

4 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

malware

Reported By: Community (akido)

More info

malware

Reported By: Community (sindresorhus)

More info

malware

Reported By: Community (Snyk)

More info

malware

Reported By: Community (debug-js)

More info

malware

Reported By: Community (chalk)

More info

malware

Reported By: Community (jdstaerk)

More info

malware

Reported By: Community (Socket)

More info

malware

Reported By: Community (Bleeping Computer)

More info

malware

Reported By: Community (GitHub Advisory)

More info

removal

Reported By: Community

malware

Reported By: ReversingLabs (Researcher)

See more info on our blog

malware

Reported By: Community (OpenSSF)

More info

Overview issues4 vulnerabilities0 malware4 behaviors4 dependencies1 contributors4 versions23

Popularity

57.47B

Recorded Downloads Since 2021

Contributors

Declared Dependencies

16.78k

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

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.

Problem

Obfuscation is a process of mangling the software code legibility. Obfuscation can be applied to both the application source and its compiled code counterpart. In both cases, obfuscation can interfere with the accuracy of security and software quality assessment solutions. For this reason, obfuscation is a technique commonly used by malicious actors as a means of bypassing security solutions and avoiding detection. While presence of obfuscation does not imply malicious intent, all of its uses in a software package should be documented and approved. One example of acceptable use for code obfuscation is minimizing the size of script files that are not intended to be read by humans. In such a case, the trade-off between file size and code legibility is considered acceptable.

Prevalence in npm community

9 packages

found in

Top 100

6 packages

found in

Top 1k

10 packages

found in

Top 10k

9.71k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1027 - Obfuscated Files or Information.

Consider an alternative to code obfuscation to lower the risk of being mistakenly flagged by security solutions.

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

9 packages

found in

Top 10k

9.17k packages

in community

Prevalence in npm community

Behavior often found in this community (Common)

95 packages

found in

Top 100

726 packages

found in

Top 1k

7488 packages

found in

Top 10k

4.56M packages

in community

Prevalence in npm community

Behavior often found in this community (Common)

97 packages

found in

Top 100

819 packages

found in

Top 1k

8086 packages

found in

Top 10k

2.83M packages

in community

Prevalence in npm community

Behavior often found in this community (Common)

92 packages

found in

Top 100

715 packages

found in

Top 1k

7216 packages

found in

Top 10k

2.27M packages

in community

Top vulnerabilities

No vulnerabilities found.

FAQ for strip-ansi

What is strip-ansi?

Strip ANSI escape codes from a string. For more information about this package, visit its homepage.

Is strip-ansi malicious or is it safe to use?

The npm package strip-ansi 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. 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 strip-ansi had 1 incidents in versions published within 2 years prior to the latest.

Is strip-ansi popular?

The npm package strip-ansi ranks among the top 10 projects in this community. It has 57B 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 strip-ansi once it is in my app?

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

Popularity

57.47B

Recorded Downloads Since 2021

Contributors

Declared Dependencies

16.78k

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

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.

Problem

Prevalence in npm community

9 packages

found in

Top 100

6 packages

found in

Top 1k

10 packages

found in

Top 10k

9.71k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1027 - Obfuscated Files or Information.

Consider an alternative to code obfuscation to lower the risk of being mistakenly flagged by security solutions.

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

9 packages

found in

Top 10k

9.17k packages

in community

Prevalence in npm community

Behavior often found in this community (Common)

95 packages

found in

Top 100

726 packages

found in

Top 1k

7488 packages

found in

Top 10k

4.56M packages

in community

Prevalence in npm community

Behavior often found in this community (Common)

97 packages

found in

Top 100

819 packages

found in

Top 1k

8086 packages

found in

Top 10k

2.83M packages

in community

Prevalence in npm community

Behavior often found in this community (Common)

92 packages

found in

Top 100

715 packages

found in

Top 1k

7216 packages

found in

Top 10k

2.27M packages

in community

Top vulnerabilities

No vulnerabilities found.

strip-ansi

SAFE Assessment

Compliance

Security

Threats

IMPORTANT: This package had 1 malicious incident in versions published within 2 years prior to the latestLatest version with malware incident detected: about 1 year agoVersion: 7.1.1

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

TH15103Detected presence of files with behaviors commonly used by malicious software.hunting

Problem

Prevalence in npm community

Next steps

TH16101Detected presence of obfuscated software components.hunting

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

Contains single-line comments.behavior

Prevalence in npm community

Contains multi-line comments.behavior

Prevalence in npm community

Top vulnerabilities

FAQ for strip-ansi

What is strip-ansi?

Is strip-ansi malicious or is it safe to use?

Is strip-ansi popular?

How do I secure strip-ansi 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

TH15103Detected presence of files with behaviors commonly used by malicious software.hunting

Problem

Prevalence in npm community

Next steps

TH16101Detected presence of obfuscated software components.hunting

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

Contains single-line comments.behavior

Prevalence in npm community

Contains multi-line comments.behavior

Prevalence in npm community

Top vulnerabilities