Secure your dependencies. Ship with confidence.

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

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

The code has several red flags including hardcoded secrets, dynamic data fetching, and use of decryption with a hardcoded URL for the key. While not outright malicious, these elements pose significant security risks that could potentially be exploited for malicious purposes.

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

The script 'packer/provisioners/post_install.sh' exhibits malicious behavior by performing several harmful actions: - **Deletes user and root history files**: Uses secure deletion methods to remove history files, potentially to conceal malicious activities. - **Clears system log files**: Erases log files from '/var/log', hindering the ability to audit and investigate system actions. - **Disables the root account**: Locks the root account password without ensuring alternative secure administrative access, possibly preventing legitimate administrative operations. - **Sets a weak default password ('changeme') for the 'admin' user**: Introduces a significant security risk by using an easily guessable password, facilitating unauthorized access. These actions can be exploited by an attacker to gain unauthorized access, disrupt legitimate operations, and prevent system recovery. The combination of log and history deletion, disabling of root access, and setting weak credentials indicates malicious intent to compromise system security and conceal nefarious activities.

The code is likely intended for automating control over user accounts on a social platform, using misleading terms and methods, with hardcoded credentials and minimal error handling, posing serious ethical and security risks.

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

This script is designed to extract sensitive access tokens from a Google Cloud instance and send them to an external server, posing a significant security risk.

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

The code is highly obfuscated and contains suspicious patterns, making it hard to determine its exact purpose. Due to the obfuscation and potential for malicious intent, it poses a significant security risk.

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

The code poses a significant security risk due to its obfuscation and behavior of downloading and executing files based on data fetched from a smart contract. This could potentially lead to executing malicious code on the user's system.

This script is attempting to exfiltrate sensitive system information (current user, current path, and hostname) to a remote server. This behavior is highly suspicious and poses a significant security risk.

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

The script is designed to exfiltrate sensitive system information to an external server. This behavior is indicative of malicious intent, as it involves unauthorized data transmission. The use of base64 encoding is a form of obfuscation, though not highly sophisticated.

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

The script collects information like package details, directories, hostnames, DNS servers and user information, and sends it to a remote server.

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

The code is designed to collect and transmit system information to external endpoints without user consent, which is indicative of malicious behavior. The hardcoded endpoints and the nature of the data being sent pose a significant security risk.

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

This file contains a malicious function that exfiltrates sensitive email data to an unauthorized external domain. When the sendEmail function is used, it secretly sends a copy of all email contents (including from address, to address, subject, and message body) to http://emails[.]egytag[.]com/api/emails/add via an unencrypted HTTP POST request. This behavior constitutes unauthorized data theft, as the API endpoint is not a legitimate email service provider and the transmission happens without user consent or knowledge. The malicious code is implemented in a straightforward manner without obfuscation, making it a clear case of a data exfiltration backdoor.

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 45 minutes before removal. Socket users were protected even while the package was live.

The code is confirmed to be malicious, with behaviors including sending system data over the network and connecting to suspicious domains. The obfuscation and data exfiltration techniques used indicate a high risk of data theft and unauthorized access.

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

The code is highly suspicious and likely malicious, as it gathers sensitive system information and sends it to an external server without consent.

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

This file contains heavily obfuscated code that gathers system data such as hostname, current working directory, user information, and network interfaces. It encodes this information (e.g., in Base64) and transmits it to a suspicious domain, for example example[.]com, using a dynamically constructed ping command. The obfuscation techniques, unauthorized data collection, and exfiltration attempt clearly indicate malicious intent consistent with malware.

The code leaks sensitive AES encryption keys to an external server over the network, which constitutes a severe security risk and likely malicious behavior. This exfiltration of secret keys can lead to compromise of encrypted data and violates fundamental security principles. The code is not obfuscated but is clearly designed to send secret keys externally, indicating a high probability of malicious intent. Users should avoid using this code or dependency due to the high risk of data theft.

This script runs 'index.js' in the background without any output, which could potentially hide malicious behavior. The actual content of 'index.js' needs to be inspected to determine the full extent of any risks.

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

This code snippet is likely malicious. It is designed to extract sensitive system and process data and send them over the network to a certain target URL. It also has the potential to execute shell commands. These behaviors suggest a potential backdoor or information stealing malware.

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

The code exhibits clear signs of malicious behavior involving data theft and exfiltration. It encodes and sends sensitive system and user data to a suspicious domain via both DNS queries and HTTPS POST requests.

Live on npm for 5 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 is malicious as it collects and sends sensitive system information to an external server, indicating data exfiltration. This poses a significant security risk.

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

The code is malicious as it sends environment variables to an external server without user consent. It is heavily obfuscated, which is a common tactic to hide malicious behavior.

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

The code is designed to collect sensitive system and user information and send it to an external server. This behavior is consistent with data exfiltration and poses a significant security risk.

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

The script poses a high security risk as malware due to its ability to alter disk partitions without user interaction, leading to data loss or system damage.

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

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

The code has several red flags including hardcoded secrets, dynamic data fetching, and use of decryption with a hardcoded URL for the key. While not outright malicious, these elements pose significant security risks that could potentially be exploited for malicious purposes.

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

The script 'packer/provisioners/post_install.sh' exhibits malicious behavior by performing several harmful actions: - **Deletes user and root history files**: Uses secure deletion methods to remove history files, potentially to conceal malicious activities. - **Clears system log files**: Erases log files from '/var/log', hindering the ability to audit and investigate system actions. - **Disables the root account**: Locks the root account password without ensuring alternative secure administrative access, possibly preventing legitimate administrative operations. - **Sets a weak default password ('changeme') for the 'admin' user**: Introduces a significant security risk by using an easily guessable password, facilitating unauthorized access. These actions can be exploited by an attacker to gain unauthorized access, disrupt legitimate operations, and prevent system recovery. The combination of log and history deletion, disabling of root access, and setting weak credentials indicates malicious intent to compromise system security and conceal nefarious activities.

The code is likely intended for automating control over user accounts on a social platform, using misleading terms and methods, with hardcoded credentials and minimal error handling, posing serious ethical and security risks.

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

This script is designed to extract sensitive access tokens from a Google Cloud instance and send them to an external server, posing a significant security risk.

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

The code is highly obfuscated and contains suspicious patterns, making it hard to determine its exact purpose. Due to the obfuscation and potential for malicious intent, it poses a significant security risk.

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

The code poses a significant security risk due to its obfuscation and behavior of downloading and executing files based on data fetched from a smart contract. This could potentially lead to executing malicious code on the user's system.

This script is attempting to exfiltrate sensitive system information (current user, current path, and hostname) to a remote server. This behavior is highly suspicious and poses a significant security risk.

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

The script is designed to exfiltrate sensitive system information to an external server. This behavior is indicative of malicious intent, as it involves unauthorized data transmission. The use of base64 encoding is a form of obfuscation, though not highly sophisticated.

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

The script collects information like package details, directories, hostnames, DNS servers and user information, and sends it to a remote server.

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

The code is designed to collect and transmit system information to external endpoints without user consent, which is indicative of malicious behavior. The hardcoded endpoints and the nature of the data being sent pose a significant security risk.

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

This file contains a malicious function that exfiltrates sensitive email data to an unauthorized external domain. When the sendEmail function is used, it secretly sends a copy of all email contents (including from address, to address, subject, and message body) to http://emails[.]egytag[.]com/api/emails/add via an unencrypted HTTP POST request. This behavior constitutes unauthorized data theft, as the API endpoint is not a legitimate email service provider and the transmission happens without user consent or knowledge. The malicious code is implemented in a straightforward manner without obfuscation, making it a clear case of a data exfiltration backdoor.

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 45 minutes before removal. Socket users were protected even while the package was live.

The code is confirmed to be malicious, with behaviors including sending system data over the network and connecting to suspicious domains. The obfuscation and data exfiltration techniques used indicate a high risk of data theft and unauthorized access.

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

The code is highly suspicious and likely malicious, as it gathers sensitive system information and sends it to an external server without consent.

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

This file contains heavily obfuscated code that gathers system data such as hostname, current working directory, user information, and network interfaces. It encodes this information (e.g., in Base64) and transmits it to a suspicious domain, for example example[.]com, using a dynamically constructed ping command. The obfuscation techniques, unauthorized data collection, and exfiltration attempt clearly indicate malicious intent consistent with malware.

The code leaks sensitive AES encryption keys to an external server over the network, which constitutes a severe security risk and likely malicious behavior. This exfiltration of secret keys can lead to compromise of encrypted data and violates fundamental security principles. The code is not obfuscated but is clearly designed to send secret keys externally, indicating a high probability of malicious intent. Users should avoid using this code or dependency due to the high risk of data theft.

This script runs 'index.js' in the background without any output, which could potentially hide malicious behavior. The actual content of 'index.js' needs to be inspected to determine the full extent of any risks.

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

This code snippet is likely malicious. It is designed to extract sensitive system and process data and send them over the network to a certain target URL. It also has the potential to execute shell commands. These behaviors suggest a potential backdoor or information stealing malware.

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

The code exhibits clear signs of malicious behavior involving data theft and exfiltration. It encodes and sends sensitive system and user data to a suspicious domain via both DNS queries and HTTPS POST requests.

Live on npm for 5 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 is malicious as it collects and sends sensitive system information to an external server, indicating data exfiltration. This poses a significant security risk.

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

The code is malicious as it sends environment variables to an external server without user consent. It is heavily obfuscated, which is a common tactic to hide malicious behavior.

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

The code is designed to collect sensitive system and user information and send it to an external server. This behavior is consistent with data exfiltration and poses a significant security risk.

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

The script poses a high security risk as malware due to its ability to alter disk partitions without user interaction, leading to data loss or system damage.