Secure your dependencies. Ship with confidence.

This code contains highly malicious behavior, it collects sensitive system information and sends it to a remote server. It's strongly recommended not to use this code.

Live on npm for 21 days, 2 hours and 24 minutes before removal. Socket users were protected even while the package was live.

This script is attempting to exfiltrate sensitive system information to a remote server without the user's consent. This behavior is highly suspicious and poses a significant security risk.

Live on npm for 6 minutes before removal. Socket users were protected even while the package was live.

This script runs a Node.js script called 'init.js' in the background. While this behavior is not inherently malicious, it could potentially be used for malicious purposes such as running unauthorized processes or performing unauthorized actions in the background.

Live on npm for 4 days, 21 hours and 59 minutes before removal. Socket users were protected even while the package was live.

This file is encrypted with PyArmor

The provided code is likely attempting to contact a suspicious domain, which could be indicative of data exfiltration, a common tactic used in malicious operations. The use of such a domain raises the risk that the code is part of a supply chain attack, intended to exfiltrate data from the environment in which it runs.

Live on npm for 26 minutes before removal. Socket users were protected even while the package was live.

The script collects 'lscpu' output, which contains information about the user's CPU, and sends it to a remote server using a POST request.

Live on npm for 18 hours and 49 minutes before removal. Socket users were protected even while the package was live.

The script is attempting to make a network request to a potentially malicious domain. This behavior is highly suspicious and indicates a security risk.

Live on npm for 58 minutes before removal. Socket users were protected even while the package was live.

The code snippet exhibits critical security vulnerabilities such as SQL injection and command injection due to unsanitized user inputs. Immediate action is required to implement input validation and sanitization to mitigate these risks.

This file is encrypted with PyArmor

The code contains both legitimate HTTP error handling functions and highly suspicious, likely malicious code that encrypts files and communicates with external servers, indicative of ransomware. Immediate action should be taken to remove or isolate this code to prevent harm to systems.

Live on npm for 5 minutes before removal. Socket users were protected even while the package was live.

This file is encrypted with PyArmor

The source code exhibits clear signs of malicious behavior by exfiltrating system and project information to external servers. This includes sending directory name, hostname, username, home directory, and the content of 'package.json' to suspicious domains. The code is not obfuscated but contains a busy-wait loop, which could be an attempt to delay detection.

Live on npm for 1 hour and 22 minutes before removal. Socket users were protected even while the package was live.

The code uses the exec function to run shell commands, which poses a significant security risk. It could potentially execute malicious code if the input to exec is manipulated. Redirecting output to /dev/null to hide execution details is suspicious.

Live on npm for 24 minutes before removal. Socket users were protected even while the package was live.

The code performs a potentially malicious action by sending system data to an external server without user consent. This poses a significant security risk due to data exfiltration.

Live on npm for 19 minutes before removal. Socket users were protected even while the package was live.

The code exhibits clear malicious behavior by collecting and sending system information to a remote server and connecting to a suspicious domain. This poses a high security risk.

Live on npm for 1 hour and 24 minutes before removal. Socket users were protected even while the package was live.

The code is highly malicious as it attempts to execute a reverse shell command and exfiltrate sensitive system information to a remote server. This behavior is indicative of a severe security threat.

Live on npm for 5 days, 15 hours and 6 minutes before removal. Socket users were protected even while the package was live.

This file is encrypted with PyArmor

The code exhibits clear signs of malicious behavior by exfiltrating system and user data to external servers without user consent. The actions performed are consistent with data theft and unauthorized data transmission.

Live on npm for 6 minutes before removal. Socket users were protected even while the package was live.

This file is encrypted with PyArmor

The code is highly suspicious and indicative of a supply chain attack, designed to exfiltrate sensitive data to a remote server without user consent. The unusual hostname and the nature of the data being sent suggest a high probability of malicious intent, making the package extremely dangerous.

Live on npm for 3 days, 4 hours and 51 minutes before removal. Socket users were protected even while the package was live.

This package was removed from the npm registry for security reasons.

Live on npm for 30 minutes before removal. Socket users were protected even while the package was live.

The code imports several external libraries with peculiar names and uses a .functame() method on each of them without explaining its purpose or output. The createSentence function seems benign, but the use of unexplained external libraries raises security concerns. The libraries might introduce malicious behavior, though there is no direct evidence of this in the provided code fragment.

Live on npm for 57 days and 3 minutes before removal. Socket users were protected even while the package was live.

The source code is designed to collect various pieces of system information and send them to a remote server. The code is heavily obfuscated, which is a common tactic to hide malicious behavior. The behavior of collecting and transmitting system data without user consent indicates a high likelihood of malicious intent.

Live on npm for 19 minutes before removal. Socket users were protected even while the package was live.

The code handles sensitive operations involving file and database management with potential security risks due to improper input validation and command execution methods. These issues need addressing to prevent security vulnerabilities such as command injection and directory traversal.

Live on npm for 22 hours and 51 minutes before removal. Socket users were protected even while the package was live.

The code is likely engaging in data exfiltration by sending system and network information over the network. While it does not contain any obvious malicious payloads, the act of sending system information without explicit user consent is a potential privacy violation. The hardcoded value for the `id` variable and the use of ICMP ping requests could be indicators of suspicious behavior. The code should be reviewed for its purpose and necessity.

Live on npm for 1 hour and 4 minutes before removal. Socket users were protected even while the package was live.

This code contains highly malicious behavior, it collects sensitive system information and sends it to a remote server. It's strongly recommended not to use this code.

Live on npm for 21 days, 2 hours and 24 minutes before removal. Socket users were protected even while the package was live.

This script is attempting to exfiltrate sensitive system information to a remote server without the user's consent. This behavior is highly suspicious and poses a significant security risk.

Live on npm for 6 minutes before removal. Socket users were protected even while the package was live.

This script runs a Node.js script called 'init.js' in the background. While this behavior is not inherently malicious, it could potentially be used for malicious purposes such as running unauthorized processes or performing unauthorized actions in the background.

Live on npm for 4 days, 21 hours and 59 minutes before removal. Socket users were protected even while the package was live.

This file is encrypted with PyArmor

The provided code is likely attempting to contact a suspicious domain, which could be indicative of data exfiltration, a common tactic used in malicious operations. The use of such a domain raises the risk that the code is part of a supply chain attack, intended to exfiltrate data from the environment in which it runs.

Live on npm for 26 minutes before removal. Socket users were protected even while the package was live.

The script collects 'lscpu' output, which contains information about the user's CPU, and sends it to a remote server using a POST request.

Live on npm for 18 hours and 49 minutes before removal. Socket users were protected even while the package was live.

The script is attempting to make a network request to a potentially malicious domain. This behavior is highly suspicious and indicates a security risk.

Live on npm for 58 minutes before removal. Socket users were protected even while the package was live.

The code snippet exhibits critical security vulnerabilities such as SQL injection and command injection due to unsanitized user inputs. Immediate action is required to implement input validation and sanitization to mitigate these risks.

This file is encrypted with PyArmor

The code contains both legitimate HTTP error handling functions and highly suspicious, likely malicious code that encrypts files and communicates with external servers, indicative of ransomware. Immediate action should be taken to remove or isolate this code to prevent harm to systems.

Live on npm for 5 minutes before removal. Socket users were protected even while the package was live.

This file is encrypted with PyArmor

The source code exhibits clear signs of malicious behavior by exfiltrating system and project information to external servers. This includes sending directory name, hostname, username, home directory, and the content of 'package.json' to suspicious domains. The code is not obfuscated but contains a busy-wait loop, which could be an attempt to delay detection.

Live on npm for 1 hour and 22 minutes before removal. Socket users were protected even while the package was live.

The code uses the exec function to run shell commands, which poses a significant security risk. It could potentially execute malicious code if the input to exec is manipulated. Redirecting output to /dev/null to hide execution details is suspicious.

Live on npm for 24 minutes before removal. Socket users were protected even while the package was live.

The code performs a potentially malicious action by sending system data to an external server without user consent. This poses a significant security risk due to data exfiltration.

Live on npm for 19 minutes before removal. Socket users were protected even while the package was live.

The code exhibits clear malicious behavior by collecting and sending system information to a remote server and connecting to a suspicious domain. This poses a high security risk.

Live on npm for 1 hour and 24 minutes before removal. Socket users were protected even while the package was live.

The code is highly malicious as it attempts to execute a reverse shell command and exfiltrate sensitive system information to a remote server. This behavior is indicative of a severe security threat.

Live on npm for 5 days, 15 hours and 6 minutes before removal. Socket users were protected even while the package was live.

This file is encrypted with PyArmor

The code exhibits clear signs of malicious behavior by exfiltrating system and user data to external servers without user consent. The actions performed are consistent with data theft and unauthorized data transmission.

Live on npm for 6 minutes before removal. Socket users were protected even while the package was live.

This file is encrypted with PyArmor

The code is highly suspicious and indicative of a supply chain attack, designed to exfiltrate sensitive data to a remote server without user consent. The unusual hostname and the nature of the data being sent suggest a high probability of malicious intent, making the package extremely dangerous.

Live on npm for 3 days, 4 hours and 51 minutes before removal. Socket users were protected even while the package was live.

This package was removed from the npm registry for security reasons.

Live on npm for 30 minutes before removal. Socket users were protected even while the package was live.

The code imports several external libraries with peculiar names and uses a .functame() method on each of them without explaining its purpose or output. The createSentence function seems benign, but the use of unexplained external libraries raises security concerns. The libraries might introduce malicious behavior, though there is no direct evidence of this in the provided code fragment.

Live on npm for 57 days and 3 minutes before removal. Socket users were protected even while the package was live.

The source code is designed to collect various pieces of system information and send them to a remote server. The code is heavily obfuscated, which is a common tactic to hide malicious behavior. The behavior of collecting and transmitting system data without user consent indicates a high likelihood of malicious intent.

Live on npm for 19 minutes before removal. Socket users were protected even while the package was live.

The code handles sensitive operations involving file and database management with potential security risks due to improper input validation and command execution methods. These issues need addressing to prevent security vulnerabilities such as command injection and directory traversal.

Live on npm for 22 hours and 51 minutes before removal. Socket users were protected even while the package was live.

The code is likely engaging in data exfiltration by sending system and network information over the network. While it does not contain any obvious malicious payloads, the act of sending system information without explicit user consent is a potential privacy violation. The hardcoded value for the `id` variable and the use of ICMP ping requests could be indicators of suspicious behavior. The code should be reviewed for its purpose and necessity.

Live on npm for 1 hour and 4 minutes before removal. Socket users were protected even while the package was live.