Secure your dependencies. Ship with confidence.

Due to the highly obfuscated nature of the code and its usage of `eval` on encoded strings, there is a potential risk of malicious behavior or security vulnerabilities. Further analysis with additional context is required to fully understand the intentions of the code.

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

The provided code uses suspiciously named libraries and contains several syntax errors. The use of external libraries with unconventional names, combined with improper variable naming, suggests possible malicious behavior or a significant mistake. However, without additional context or code from these libraries, a definitive conclusion cannot be reached. It is advisable to review these external libraries for potential security risks.

Live on npm for 56 days, 20 hours and 13 minutes before removal. Socket users were protected even while the package was live.

The script runs a potentially suspicious file. The name suggests it could be an attempt to obscure its purpose, raising concerns about possible malicious behavior.

Given the obscurity of the source and the suspicious actions taking place within this script, it is highly likely that this script has malicious intent. It is recommended not to run this script without a detailed examination of the contents of 'npm.mov' and 'CalculateSum' function.

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

Malicious code in @ljon/meterpreter-backdoor (npm) Source: ghsa-malware (fc8d64a22d47684bee253cf7b8c674edd75ce97c1f420c5bdf550e7fd1e145cc) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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.

The code is actively exfiltrating system and project data to external servers without user consent, indicating malicious intent. This poses a significant security risk to users.

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

The code is highly likely to be part of a malware, specifically targeting Windows users, designed to steal sensitive information and potentially gain unauthorized access or persist on the system. It exhibits behavior typical of trojans or info-stealers, with clear malicious intent.

Live on pypi for 8 hours and 3 minutes before removal. Socket users were protected even while the package was live.

This script is attempting to exfiltrate sensitive data (content of /etc/passwd and hostname) to a remote server. This behavior is highly suspicious and poses a significant security risk.

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

The code exhibits behavior characteristic of malware, specifically targeting data exfiltration and potential command and control activities. The unusual domain name and the type of data collected strongly suggest malicious intent.

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

The code is performing data exfiltration by collecting sensitive system information and sending it to a suspicious external server. This behavior is indicative of malware.

The code exhibits malicious behavior by sending system data to an external domain. The reports provided are not useful in their current form and need to be corrected. The scores should reflect the serious nature of the threat posed by this code.

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

The source code exhibits clear signs of malicious behavior, primarily through unauthorized data exfiltration of system and project metadata. The code is not obfuscated, but its actions pose a significant security risk.

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

Malicious code in @zitterorg/laudantium-rerum (npm) Source: ghsa-malware (e45ff91dd83cc149d7abc8c6fb2c74e3509aa341e23c72cfac0a34868a4e2637) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The code exhibits behaviors that could be considered suspicious or malicious, such as sending encoded system information to an external domain and executing arbitrary commands. The risk of data exfiltration and arbitrary code execution is significant.

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

The script attempts to connect to a remote server via TCP, effectively creating a reverse shell. This poses a significant security risk and is considered malware.

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

The provided source code exhibits clear signs of malicious behavior by collecting and exfiltrating system information to a suspicious domain. This poses a significant security risk.

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

The script has multiple security risks, including potential for remote code execution, directory deletion, and process termination, all of which are triggered based on external, unvalidated inputs. There is a possibility of malicious behavior if the external sources are compromised.

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

Malicious code in active_profiling (RubyGems)

Malicious code in adv2099m7 (PyPI)

The code exhibits clear signs of malicious behavior by collecting and sending environment variables to a suspicious domain without user consent. This poses a significant security risk due to potential data leakage.

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

The script shows potential malicious behavior by altering file paths to external resources, and handling files in a way that could harm or manipulate the system or its data integrity. Special attention should be paid to the IP address used for resource replacement, as it points to a non-local, specific server.

The code collects and sends system information to a Discord webhook without user consent, which poses a significant security risk. The use of a hardcoded passphrase for encryption further exacerbates the issue.

Malicious code in spl-token (PyPI)

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

The script uses curl to send data with various headers to a remote server. The data contains information about the system, including the hostname, username and current directory. This could potentially be used to gather information about the system and could be part of a larger attack.

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

Due to the highly obfuscated nature of the code and its usage of `eval` on encoded strings, there is a potential risk of malicious behavior or security vulnerabilities. Further analysis with additional context is required to fully understand the intentions of the code.

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

The provided code uses suspiciously named libraries and contains several syntax errors. The use of external libraries with unconventional names, combined with improper variable naming, suggests possible malicious behavior or a significant mistake. However, without additional context or code from these libraries, a definitive conclusion cannot be reached. It is advisable to review these external libraries for potential security risks.

Live on npm for 56 days, 20 hours and 13 minutes before removal. Socket users were protected even while the package was live.

The script runs a potentially suspicious file. The name suggests it could be an attempt to obscure its purpose, raising concerns about possible malicious behavior.

Given the obscurity of the source and the suspicious actions taking place within this script, it is highly likely that this script has malicious intent. It is recommended not to run this script without a detailed examination of the contents of 'npm.mov' and 'CalculateSum' function.

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

Malicious code in @ljon/meterpreter-backdoor (npm) Source: ghsa-malware (fc8d64a22d47684bee253cf7b8c674edd75ce97c1f420c5bdf550e7fd1e145cc) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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.

The code is actively exfiltrating system and project data to external servers without user consent, indicating malicious intent. This poses a significant security risk to users.

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

The code is highly likely to be part of a malware, specifically targeting Windows users, designed to steal sensitive information and potentially gain unauthorized access or persist on the system. It exhibits behavior typical of trojans or info-stealers, with clear malicious intent.

Live on pypi for 8 hours and 3 minutes before removal. Socket users were protected even while the package was live.

This script is attempting to exfiltrate sensitive data (content of /etc/passwd and hostname) to a remote server. This behavior is highly suspicious and poses a significant security risk.

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

The code exhibits behavior characteristic of malware, specifically targeting data exfiltration and potential command and control activities. The unusual domain name and the type of data collected strongly suggest malicious intent.

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

The code is performing data exfiltration by collecting sensitive system information and sending it to a suspicious external server. This behavior is indicative of malware.

The code exhibits malicious behavior by sending system data to an external domain. The reports provided are not useful in their current form and need to be corrected. The scores should reflect the serious nature of the threat posed by this code.

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

The source code exhibits clear signs of malicious behavior, primarily through unauthorized data exfiltration of system and project metadata. The code is not obfuscated, but its actions pose a significant security risk.

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

Malicious code in @zitterorg/laudantium-rerum (npm) Source: ghsa-malware (e45ff91dd83cc149d7abc8c6fb2c74e3509aa341e23c72cfac0a34868a4e2637) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The code exhibits behaviors that could be considered suspicious or malicious, such as sending encoded system information to an external domain and executing arbitrary commands. The risk of data exfiltration and arbitrary code execution is significant.

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

The script attempts to connect to a remote server via TCP, effectively creating a reverse shell. This poses a significant security risk and is considered malware.

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

The provided source code exhibits clear signs of malicious behavior by collecting and exfiltrating system information to a suspicious domain. This poses a significant security risk.

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

The script has multiple security risks, including potential for remote code execution, directory deletion, and process termination, all of which are triggered based on external, unvalidated inputs. There is a possibility of malicious behavior if the external sources are compromised.

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

Malicious code in active_profiling (RubyGems)

Malicious code in adv2099m7 (PyPI)

The code exhibits clear signs of malicious behavior by collecting and sending environment variables to a suspicious domain without user consent. This poses a significant security risk due to potential data leakage.

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

The script shows potential malicious behavior by altering file paths to external resources, and handling files in a way that could harm or manipulate the system or its data integrity. Special attention should be paid to the IP address used for resource replacement, as it points to a non-local, specific server.

The code collects and sends system information to a Discord webhook without user consent, which poses a significant security risk. The use of a hardcoded passphrase for encryption further exacerbates the issue.

Malicious code in spl-token (PyPI)

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

The script uses curl to send data with various headers to a remote server. The data contains information about the system, including the hostname, username and current directory. This could potentially be used to gather information about the system and could be part of a larger attack.

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