n158@0.0.1-security

security holding package

latest version

0.0.1-security

first published

6 days ago

latest version published

6 days ago

View n158 package health on Snyk (opens in a new tab)

Go back to all versions of this package

Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the n158 package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free

Vulnerability Vulnerable Version

Vulnerability	Vulnerable Version
C Malicious Package n158 is a malicious package. This package contains malicious code, and its content was removed from the official package manager. While this package might be attempting to impersonate a valid organization, there is no connection between that organization and this package authorship. How to fix Malicious Package? Avoid using all malicious instances of the `n158` package.	*
H Command Injection Affected versions of this package are vulnerable to Command Injection due to improper input sanitization in the 'module.exports' function. Note: To execute the code snippet and potentially exploit the vulnerability, the attacker needs to have the ability to run Node.js code within the target environment. This typically requires some level of access to the system or application hosting the Node.js environment. How to fix Command Injection? There is no fixed version for `n158`.	*

Malicious Package

n158 is a malicious package. This package contains malicious code, and its content was removed from the official package manager. While this package might be attempting to impersonate a valid organization, there is no connection between that organization and this package authorship.

How to fix Malicious Package?

Avoid using all malicious instances of the n158 package.

Command Injection

Affected versions of this package are vulnerable to Command Injection due to improper input sanitization in the 'module.exports' function.

Note:

To execute the code snippet and potentially exploit the vulnerability, the attacker needs to have the ability to run Node.js code within the target environment. This typically requires some level of access to the system or application hosting the Node.js environment.

How to fix Command Injection?

There is no fixed version for n158.

Go back to all versions of this package