Spectra Assure

failIncident: Malware

Scanned:

js-logger-pack

removed

malicious

Research

Pretty colorized changelog-style logger with timestamps and level icons

License: Permissive (MIT)

Published:

See on npm

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

1 low severity vulnerabilities

Hardening

No application hardening issues

Threats

Tampering

2 malware-like behaviors found

Malware

1 supply chain attack artifacts

INCIDENTS FOR THIS VERSION:

malware

Reported By: ReversingLabs (Researcher)

See more info on our blog

malware

Reported By: Community (OpenSSF)

More info

malware

Reported By: Community (SafeDep)

More info

malware

Reported By: Community (GitHub Advisory)

More info

malware

Reported By: Community (JFrog)

More info

removal

Reported By: Community

Popularity

7.25k

Recorded Downloads Since 2021

Contributors

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

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 exclusively used by malicious software with the intent to cause harm. When a software package matches behavior traits of malicious software, it becomes flagged by security solutions. It is highly likely that the software package was tampered with by a malicious actor or a rogue insider. Detected threat type matches the behaviors typically exhibited by the backdoor malware profile. Backdoors are commonly used by malicious actors to gain unauthorized access to exposed computer systems over the internet. However, due to high-privilege access requirements, some security solutions may also trigger this detection when analyzed.

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

0 packages

found in

Top 10k

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

In the case this behavior is intended, rewrite the flagged code without using the malware-like behaviors.

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.

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

0 packages

found in

Top 100

0 packages

found in

Top 1k

6 packages

found in

Top 10k

516.56k 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 often found in this community (Common)

6 packages

found in

Top 100

12 packages

found in

Top 1k

329 packages

found in

Top 10k

62.19k 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 often found in this community (Common)

6 packages

found in

Top 100

45 packages

found in

Top 1k

684 packages

found in

Top 10k

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

1 packages

found in

Top 100

14 packages

found in

Top 1k

243 packages

found in

Top 10k

49.18k packages

in community

Top vulnerabilities

See all vulnerabilities

Vulnerability Exploitation Lifecycle

(1 Active Vulnerabilities)

None

1 (0 Fixable)

CVE-2024-53384l

None

Exploits Unknown

Exploits Exist

Exploited by Malware

Patching Mandated

FAQ for js-logger-pack

What is js-logger-pack?

Pretty colorized changelog-style logger with timestamps and level icons.

Is js-logger-pack malicious or is it safe to use?

The npm package js-logger-pack 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. 2 other issues and risky behaviors were 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 js-logger-pack package were malicious.

Is js-logger-pack popular?

The npm package js-logger-pack is not widely used. It has 7K 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 js-logger-pack once it is in my app?

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

7.25k

Recorded Downloads Since 2021

Contributors

Declared Dependencies

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

0 packages

found in

Top 100

0 packages

found in

Top 1k

0 packages

found in

Top 10k

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

In the case this behavior is intended, rewrite the flagged code without using the malware-like behaviors.

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.

Problem

Prevalence in npm community

0 packages

found in

Top 100

0 packages

found in

Top 1k

6 packages

found in

Top 10k

516.56k 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 often found in this community (Common)

6 packages

found in

Top 100

12 packages

found in

Top 1k

329 packages

found in

Top 10k

62.19k 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 often found in this community (Common)

6 packages

found in

Top 100

45 packages

found in

Top 1k

684 packages

found in

Top 10k

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

1 packages

found in

Top 100

14 packages

found in

Top 1k

243 packages

found in

Top 10k

49.18k packages

in community

Top vulnerabilities

See all vulnerabilities

Vulnerability Exploitation Lifecycle

(1 Active Vulnerabilities)

None

1 (0 Fixable)

CVE-2024-53384l

None

Exploits Unknown

Exploits Exist

Exploited by Malware

Patching Mandated

js-logger-pack

SAFE Assessment

Compliance

Security

Threats

IMPORTANT: All versions of this package have been maliciousLatest version with malware incident detected: 27 days agoVersion: 1.1.27

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

TH15106Detected presence of files with behaviors that match the backdoor malware profile.Causes risk: malware-like behaviors 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

Modifies file/directory permissions.permissions

Prevalence in npm community

Might contain potentially obfuscated code or data.anomaly

Prevalence in npm community

Decodes data using the Base64 algorithm.packer

Prevalence in npm community

Executes files during installation or upon launch.execution

Prevalence in npm community

Compresses data using the GZip algorithm.packer

Prevalence in npm community

Top vulnerabilities

FAQ for js-logger-pack

What is js-logger-pack?

Is js-logger-pack malicious or is it safe to use?

Is js-logger-pack popular?

How do I secure js-logger-pack 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

TH15106Detected presence of files with behaviors that match the backdoor malware profile.Causes risk: malware-like behaviors 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

Modifies file/directory permissions.permissions

Prevalence in npm community

Might contain potentially obfuscated code or data.anomaly

Prevalence in npm community

Decodes data using the Base64 algorithm.packer

Prevalence in npm community

Executes files during installation or upon launch.execution

Prevalence in npm community

Compresses data using the GZip algorithm.packer

Prevalence in npm community