Secure your dependencies. Ship with confidence.

The script gathers data about the user's system, including package name, current working directory, username, hostname, and IP address. This data is then encoded and sent as DNS queries to a remote server.

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

This code performs unauthorized data exfiltration of sensitive system and environment information to a suspicious remote server, constituting malicious behavior and a serious privacy violation. It should be considered malware with high security risk.

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

The code contains dynamic URL alterations and uses 'os.system' with user inputs, posing a security risk. It is recommended to review the code for safer alternatives.

This script removes the './node_modules/@types/react' folder. While this may not be malicious, it is potentially unsafe as it could cause issues with the React type definitions.

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

This code collects potentially sensitive system information and sends it to a remote server without user consent, which is indicative of malicious behavior. The presence of a suspicious Telegram contact link further raises concerns.

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

Performing a DNS lookup on a domain can be a legitimate action, but it could also be used for data exfiltration or to establish communication with a malicious server. The intent and context of this script should be further investigated to determine if it poses a security risk.

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

This file contains malicious code that functions as a backdoor with data exfiltration and remote code execution capabilities. The code systematically collects sensitive system information including all environment variables, platform details, hostname, username, and MAC addresses from network interfaces. This data is then transmitted via HTTP POST request to a suspicious remote server at https://log-server-lovat[.]vercel[.]app/api/ipcheck/703 with a custom header 'x-secret-header: secret'. After sending the collected data, the malware evaluates the server's response as JavaScript code using eval(), enabling arbitrary remote code execution. The code employs obfuscation by hex-encoding critical strings like 'require', 'axios', 'post', and the target URL to evade detection. Error handling is deliberately suppressed to prevent detection of failed operations. This represents a critical supply chain attack vector that compromises system security through both data theft and remote control capabilities.

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

The code exhibits behaviors consistent with malicious activities, particularly due to the use of eval() with code fetched from an external source. This can lead to arbitrary code execution, posing a significant security risk.

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

The purpose of this code appears to be collecting specific environment variables and package information, compressing and encoding it, and sending it over HTTP to a remote domain. The intent and purpose of this behavior are unclear from the provided code fragment alone.

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

This file gathers detailed OS and network information (including hostname, user details, and IP addresses) and sends it to hardcoded endpoints (e.g., http://23[.]22[.]251[.]177:8080/jpd[.]php and http://23[.]22[.]251[.]177:8080/jpd1[.]php) via HTTP GET and POST requests. It also attempts to fall back on a WebSocket connection (wss://yourserver[.]com/socket) if needed. The code fetches the public IP address from https://api64.ipify.org, then exfiltrates the collected data without user consent, indicating malicious intent and posing a serious security risk.

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

This script silently collects the host machine's hostname (via os.hostname()) and an optional project identifier (from process.argv[2], defaulting to "unknown"), packages them into a JSON string, URL-encodes the result, and issues an HTTPS GET request to https://z0[.]rs/callback?msg=<payload>. It explicitly disables TLS certificate validation (rejectUnauthorized:false) and suppresses errors, enabling transmission of system information without user notification or consent. The disabled TLS verification exposes the data to potential man-in-the-middle interception. While the data collected is limited to hostname and project ID, this constitutes unauthorized telemetry that operates without user awareness or consent.

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

The provided code snippet itself is not malicious. It's a standard React component converted to a Web Component. However, the reports indicating '[object Promise]' are highly suspicious and suggest that the `react-to-webcomponent` library or its dependencies may be dynamically loading or obfuscating malicious code. Without analyzing the actual content of these promises or the library's implementation, a definitive malware assessment is difficult, but the reporting pattern warrants a high suspicion.

This script is highly suspicious and potentially malicious. It is making network requests to external sites and running commands based on the output of other commands. It is recommended to not use this package.

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

This code is highly suspicious due to its obfuscation, dynamic evaluation, and patterns indicating it might be attempting to extract and send sensitive information. It is likely malicious.

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

This script is exfiltrating 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 18 minutes before removal. Socket users were protected even while the package was live.

The provided code establishes a reverse shell connection to a remote server, which is a serious security risk. This behavior is indicative of malicious activity, as it allows remote control over the system.

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

The provided source code exhibits several characteristics that are commonly associated with malware, such as the use of encryption, dynamic payload execution, and hardcoded sensitive values. While the exact purpose of the script is unclear without further analysis, the overall behavior and structure of the code suggest a high probability of malicious intent. This script should be treated with caution and further investigated before being used or executed.

Live on PyPI for 10 hours and 29 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 22 minutes before removal. Socket users were protected even while the package was live.

The provided code snippet imports several modules with uncommon and potentially suspicious names, each executing a function named 'functame'. There is no context or explanation given for what these functions do, which raises concerns. The lack of proper error handling and data validation further indicates potential security risks. The arbitrary and unclear nature of the code, combined with unusual module names, makes it potentially malicious, although the exact intent cannot be determined from this fragment alone.

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

The code poses a significant security risk by downloading and executing a file from an external source without verification. This could lead to arbitrary code execution if the URL is compromised. The use of silent exception handling further obscures potential errors.

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

The script collects various system information like hostname, username, current working directory, and network interfaces, and exfiltrates the data by encoding it in the DNS hostname in a ping request.

Live on npm for 1 minute 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.

This script has some potentially suspicious behaviour, specifically network requests to a remote server and automatic Node.js version management. These actions could lead to potential security risks. However, without more context or understanding the exact purpose of the script, it's difficult to definitively label it as malicious.

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

The code snippet is engaging in potentially malicious behavior by attempting to encrypt and overwrite files on the system. It poses a high security risk due to the possibility of data loss and unauthorized access.

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

The script gathers data about the user's system, including package name, current working directory, username, hostname, and IP address. This data is then encoded and sent as DNS queries to a remote server.

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

This code performs unauthorized data exfiltration of sensitive system and environment information to a suspicious remote server, constituting malicious behavior and a serious privacy violation. It should be considered malware with high security risk.

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

The code contains dynamic URL alterations and uses 'os.system' with user inputs, posing a security risk. It is recommended to review the code for safer alternatives.

This script removes the './node_modules/@types/react' folder. While this may not be malicious, it is potentially unsafe as it could cause issues with the React type definitions.

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

This code collects potentially sensitive system information and sends it to a remote server without user consent, which is indicative of malicious behavior. The presence of a suspicious Telegram contact link further raises concerns.

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

Performing a DNS lookup on a domain can be a legitimate action, but it could also be used for data exfiltration or to establish communication with a malicious server. The intent and context of this script should be further investigated to determine if it poses a security risk.

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

This file contains malicious code that functions as a backdoor with data exfiltration and remote code execution capabilities. The code systematically collects sensitive system information including all environment variables, platform details, hostname, username, and MAC addresses from network interfaces. This data is then transmitted via HTTP POST request to a suspicious remote server at https://log-server-lovat[.]vercel[.]app/api/ipcheck/703 with a custom header 'x-secret-header: secret'. After sending the collected data, the malware evaluates the server's response as JavaScript code using eval(), enabling arbitrary remote code execution. The code employs obfuscation by hex-encoding critical strings like 'require', 'axios', 'post', and the target URL to evade detection. Error handling is deliberately suppressed to prevent detection of failed operations. This represents a critical supply chain attack vector that compromises system security through both data theft and remote control capabilities.

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

The code exhibits behaviors consistent with malicious activities, particularly due to the use of eval() with code fetched from an external source. This can lead to arbitrary code execution, posing a significant security risk.

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

The purpose of this code appears to be collecting specific environment variables and package information, compressing and encoding it, and sending it over HTTP to a remote domain. The intent and purpose of this behavior are unclear from the provided code fragment alone.

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

This file gathers detailed OS and network information (including hostname, user details, and IP addresses) and sends it to hardcoded endpoints (e.g., http://23[.]22[.]251[.]177:8080/jpd[.]php and http://23[.]22[.]251[.]177:8080/jpd1[.]php) via HTTP GET and POST requests. It also attempts to fall back on a WebSocket connection (wss://yourserver[.]com/socket) if needed. The code fetches the public IP address from https://api64.ipify.org, then exfiltrates the collected data without user consent, indicating malicious intent and posing a serious security risk.

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

This script silently collects the host machine's hostname (via os.hostname()) and an optional project identifier (from process.argv[2], defaulting to "unknown"), packages them into a JSON string, URL-encodes the result, and issues an HTTPS GET request to https://z0[.]rs/callback?msg=<payload>. It explicitly disables TLS certificate validation (rejectUnauthorized:false) and suppresses errors, enabling transmission of system information without user notification or consent. The disabled TLS verification exposes the data to potential man-in-the-middle interception. While the data collected is limited to hostname and project ID, this constitutes unauthorized telemetry that operates without user awareness or consent.

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

The provided code snippet itself is not malicious. It's a standard React component converted to a Web Component. However, the reports indicating '[object Promise]' are highly suspicious and suggest that the `react-to-webcomponent` library or its dependencies may be dynamically loading or obfuscating malicious code. Without analyzing the actual content of these promises or the library's implementation, a definitive malware assessment is difficult, but the reporting pattern warrants a high suspicion.

This script is highly suspicious and potentially malicious. It is making network requests to external sites and running commands based on the output of other commands. It is recommended to not use this package.

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

This code is highly suspicious due to its obfuscation, dynamic evaluation, and patterns indicating it might be attempting to extract and send sensitive information. It is likely malicious.

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

This script is exfiltrating 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 18 minutes before removal. Socket users were protected even while the package was live.

The provided code establishes a reverse shell connection to a remote server, which is a serious security risk. This behavior is indicative of malicious activity, as it allows remote control over the system.

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

The provided source code exhibits several characteristics that are commonly associated with malware, such as the use of encryption, dynamic payload execution, and hardcoded sensitive values. While the exact purpose of the script is unclear without further analysis, the overall behavior and structure of the code suggest a high probability of malicious intent. This script should be treated with caution and further investigated before being used or executed.

Live on PyPI for 10 hours and 29 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 22 minutes before removal. Socket users were protected even while the package was live.

The provided code snippet imports several modules with uncommon and potentially suspicious names, each executing a function named 'functame'. There is no context or explanation given for what these functions do, which raises concerns. The lack of proper error handling and data validation further indicates potential security risks. The arbitrary and unclear nature of the code, combined with unusual module names, makes it potentially malicious, although the exact intent cannot be determined from this fragment alone.

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

The code poses a significant security risk by downloading and executing a file from an external source without verification. This could lead to arbitrary code execution if the URL is compromised. The use of silent exception handling further obscures potential errors.

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

The script collects various system information like hostname, username, current working directory, and network interfaces, and exfiltrates the data by encoding it in the DNS hostname in a ping request.

Live on npm for 1 minute 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.

This script has some potentially suspicious behaviour, specifically network requests to a remote server and automatic Node.js version management. These actions could lead to potential security risks. However, without more context or understanding the exact purpose of the script, it's difficult to definitively label it as malicious.

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

The code snippet is engaging in potentially malicious behavior by attempting to encrypt and overwrite files on the system. It poses a high security risk due to the possibility of data loss and unauthorized access.

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