Secure your dependencies. Ship with confidence.

The package contains a hidden payload that targets Russian language users visiting Russian and Belarusian sites. For those users, it will disable user interaction and play a looping audio of the Ukrainian anthem after 3 days. Therefore, it is marked as malware only because it freezes interactions for many users. This behavior is not disclosed in any documentation of the package and seriously disrupts user experience.

The code provides valuable insights into the potential security risks associated with the MakeRequest function and the need for thorough input validation.

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

The code poses a potential privacy violation risk as it collects and sends user data to a remote server without sanitization and user consent. The tracking data should be reviewed and sent to a trusted server if necessary.

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

This file collects internal and external IP addresses, DNS servers, hostnames, and user information, then transmits this data via a hardcoded webhook at discord[.]com. It also fetches additional details from ipinfo[.]io to gather external IP and related location data. Conditional checks are in place to avoid exfiltration in specific environments, suggesting an attempt to evade detection. This behavior constitutes data exfiltration without user consent and is considered malicious.

The primary security risks in this code are the use of eval to execute decrypted content from install.json and the hardcoded secret key. These practices can lead to remote code execution and other security vulnerabilities if the file content is tampered with or malicious.

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

The code exhibits malicious behavior by collecting and exfiltrating system information to an external domain using DNS queries. This poses a significant security risk.

This script is highly malicious as it attempts to exfiltrate sensitive information from the system to a remote server, posing a significant security risk.

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

This code poses a serious security risk and should not be used.

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

The code presents a significant security risk due to the use of 'exec' with unsanitized user input, enabling command injection attacks. While no malicious behavior or obfuscation is detected, this vulnerability could allow an attacker to execute arbitrary shell commands on the host system. It is recommended to sanitize or validate the 'url' input or use safer alternatives such as HTTP request libraries instead of shelling out to curl. The code itself does not contain malware but poses a high security risk if used with untrusted input.

The code is malicious, designed to establish a reverse shell connection by executing a payload fetched from an external source. This poses a significant security risk and should be treated as malware.

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

The code poses a significant security risk due to its ability to execute arbitrary commands fetched from a remote server. This can potentially lead to a system compromise. The lack of proper error handling and validation further exacerbates the risk.

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

The code is highly obfuscated and contains elements that suggest potentially malicious behavior, such as executing shell commands and making network requests. Further deobfuscation and analysis are needed to confirm any malicious intent.

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

This file contains code that collects sensitive system information, including user details, DNS server data, and contents of /etc/passwd and /etc/hosts, then sends it to a suspicious remote host at 7ltxf0qwu6urkwd8dmov4nb1zs5mtch1[.]oastify[.]com via HTTPS. This behavior constitutes unauthorized data exfiltration and poses a serious security risk.

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

The script logs into a user's Discord account using a provided token, collects sensitive information, and transmits it to a hardcoded external webhook. This behavior is indicative of an account information theft, posing a significant security risk.

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

The code exhibits malicious behavior by exfiltrating sensitive data to an external webhook using hardcoded credentials. Specifically, it generates API keys and sends them to a webhook without user consent, and logs bot tokens in plain text files. These actions can lead to unauthorized access and compromise of the system, as sensitive information is transmitted and stored insecurely.

The code exhibits behavior consistent with data exfiltration by sending environment variables to a remote server. This poses a significant security risk as environment variables can contain sensitive information.

Live on npm for 12 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 11 minutes before removal. Socket users were protected even while the package was live.

The source code contains malicious functionality that covertly exfiltrates sensitive bot and user data to a remote server using obfuscated HTTP requests. This behavior constitutes a serious privacy breach and malware activity. The obfuscation and hardcoded external IP indicate intent to hide this behavior. The code should be considered highly suspicious and unsafe to use.

The code is clearly malicious, as it collects and exfiltrates sensitive system information to an external server without user consent. The use of base64 encoding and the 'ping' command indicates an attempt to obfuscate the exfiltration process.

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

This script is making a request to a remote server and passing the hostname of the system as a parameter. This behavior is potentially suspicious and could be used for data exfiltration or other malicious activities.

This file downloads an executable from https://example[.]com/pL5qZ and executes it without any validation or user consent. The shortened link obscures the true destination, increasing the likelihood of malicious or unauthorized behavior. This poses a severe security risk by allowing remote code execution on the system.

Live on PyPI for 5 days, 9 hours and 31 minutes before removal. Socket users were protected even while the package was live.

The code is designed to exfiltrate sensitive system information to an external domain using DNS queries, which is a clear indication of malicious intent. The use of encoding and DNS queries suggests an attempt to hide this activity.

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

The source code exhibits behavior consistent with data exfiltration malware. It collects sensitive system information and sends it to external endpoints without user consent, posing a significant security risk.

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

This script is potentially malicious as it sends sensitive information to an external URL without clear justification or consent. It could be exfiltrating data or performing unauthorized tracking.

The code poses a significant security risk by downloading and executing an external executable file without any validation or user consent. This behavior is indicative of potential malware activity.

Live on PyPI for 7 hours and 32 minutes before removal. Socket users were protected even while the package was live.

The package contains a hidden payload that targets Russian language users visiting Russian and Belarusian sites. For those users, it will disable user interaction and play a looping audio of the Ukrainian anthem after 3 days. Therefore, it is marked as malware only because it freezes interactions for many users. This behavior is not disclosed in any documentation of the package and seriously disrupts user experience.

The code provides valuable insights into the potential security risks associated with the MakeRequest function and the need for thorough input validation.

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

The code poses a potential privacy violation risk as it collects and sends user data to a remote server without sanitization and user consent. The tracking data should be reviewed and sent to a trusted server if necessary.

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

This file collects internal and external IP addresses, DNS servers, hostnames, and user information, then transmits this data via a hardcoded webhook at discord[.]com. It also fetches additional details from ipinfo[.]io to gather external IP and related location data. Conditional checks are in place to avoid exfiltration in specific environments, suggesting an attempt to evade detection. This behavior constitutes data exfiltration without user consent and is considered malicious.

The primary security risks in this code are the use of eval to execute decrypted content from install.json and the hardcoded secret key. These practices can lead to remote code execution and other security vulnerabilities if the file content is tampered with or malicious.

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

The code exhibits malicious behavior by collecting and exfiltrating system information to an external domain using DNS queries. This poses a significant security risk.

This script is highly malicious as it attempts to exfiltrate sensitive information from the system to a remote server, posing a significant security risk.

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

This code poses a serious security risk and should not be used.

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

The code presents a significant security risk due to the use of 'exec' with unsanitized user input, enabling command injection attacks. While no malicious behavior or obfuscation is detected, this vulnerability could allow an attacker to execute arbitrary shell commands on the host system. It is recommended to sanitize or validate the 'url' input or use safer alternatives such as HTTP request libraries instead of shelling out to curl. The code itself does not contain malware but poses a high security risk if used with untrusted input.

The code is malicious, designed to establish a reverse shell connection by executing a payload fetched from an external source. This poses a significant security risk and should be treated as malware.

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

The code poses a significant security risk due to its ability to execute arbitrary commands fetched from a remote server. This can potentially lead to a system compromise. The lack of proper error handling and validation further exacerbates the risk.

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

The code is highly obfuscated and contains elements that suggest potentially malicious behavior, such as executing shell commands and making network requests. Further deobfuscation and analysis are needed to confirm any malicious intent.

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

This file contains code that collects sensitive system information, including user details, DNS server data, and contents of /etc/passwd and /etc/hosts, then sends it to a suspicious remote host at 7ltxf0qwu6urkwd8dmov4nb1zs5mtch1[.]oastify[.]com via HTTPS. This behavior constitutes unauthorized data exfiltration and poses a serious security risk.

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

The script logs into a user's Discord account using a provided token, collects sensitive information, and transmits it to a hardcoded external webhook. This behavior is indicative of an account information theft, posing a significant security risk.

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

The code exhibits malicious behavior by exfiltrating sensitive data to an external webhook using hardcoded credentials. Specifically, it generates API keys and sends them to a webhook without user consent, and logs bot tokens in plain text files. These actions can lead to unauthorized access and compromise of the system, as sensitive information is transmitted and stored insecurely.

The code exhibits behavior consistent with data exfiltration by sending environment variables to a remote server. This poses a significant security risk as environment variables can contain sensitive information.

Live on npm for 12 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 11 minutes before removal. Socket users were protected even while the package was live.

The source code contains malicious functionality that covertly exfiltrates sensitive bot and user data to a remote server using obfuscated HTTP requests. This behavior constitutes a serious privacy breach and malware activity. The obfuscation and hardcoded external IP indicate intent to hide this behavior. The code should be considered highly suspicious and unsafe to use.

The code is clearly malicious, as it collects and exfiltrates sensitive system information to an external server without user consent. The use of base64 encoding and the 'ping' command indicates an attempt to obfuscate the exfiltration process.

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

This script is making a request to a remote server and passing the hostname of the system as a parameter. This behavior is potentially suspicious and could be used for data exfiltration or other malicious activities.

This file downloads an executable from https://example[.]com/pL5qZ and executes it without any validation or user consent. The shortened link obscures the true destination, increasing the likelihood of malicious or unauthorized behavior. This poses a severe security risk by allowing remote code execution on the system.

Live on PyPI for 5 days, 9 hours and 31 minutes before removal. Socket users were protected even while the package was live.

The code is designed to exfiltrate sensitive system information to an external domain using DNS queries, which is a clear indication of malicious intent. The use of encoding and DNS queries suggests an attempt to hide this activity.

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

The source code exhibits behavior consistent with data exfiltration malware. It collects sensitive system information and sends it to external endpoints without user consent, posing a significant security risk.

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

This script is potentially malicious as it sends sensitive information to an external URL without clear justification or consent. It could be exfiltrating data or performing unauthorized tracking.

The code poses a significant security risk by downloading and executing an external executable file without any validation or user consent. This behavior is indicative of potential malware activity.

Live on PyPI for 7 hours and 32 minutes before removal. Socket users were protected even while the package was live.