Secure your dependencies. Ship with confidence.

The file contains code that secretly gathers detailed system information, such as hostname, OS type, platform, release, architecture, local IP addresses, public IP address (fetched via an external API), username, and current working directory. It then transmits this data to external endpoints via HTTP GET and POST requests, and uses a WebSocket connection as a fallback. The endpoints are hardcoded, for example, to URLs like http://example.com/jpd3.php, http://example.com/jpd4.php, and wss://example.com/socket, which are not transparent or verified services. This behavior is indicative of malware designed for unauthorized data exfiltration.

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

The code is highly suspicious due to its collection and transmission of system information to external servers without user consent. The use of hardcoded IP addresses and fallback mechanisms for data transmission indicates potential malicious intent.

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

The analyzed source code is malicious and performs unauthorized data exfiltration of sensitive system and user information to a suspicious external server. This constitutes a critical supply chain security risk and privacy violation. The code should be considered malware with high confidence, and the package containing it should be avoided or removed immediately.

Live on npm for 53 days, 16 hours and 55 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 21 minutes before removal. Socket users were protected even while the package was live.

The code is performing unauthorized data exfiltration by sending system information to a remote server. This is a clear indication of malicious behavior, posing a significant security risk.

Live on npm for 1 hour and 47 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 11 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.

The script is designed to send sensitive system information to an external server, which poses a significant security risk and is indicative of malicious behavior.

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

The script collects sensitive user information from the Discord API, including usernames, emails, and IDs, and saves it to a file without user consent. It automates interactions with Discord, including sending unsolicited messages to channels (spamming), and uses a captcha solving service to bypass security measures. The script contains hardcoded API keys and tokens, posing significant security risks if shared or leaked. Additionally, it includes obfuscated JavaScript code to manipulate local storage tokens, suggesting attempts to hijack or misuse user accounts.

The code is designed to send sensitive system information to a remote server, which is a significant security risk. This behavior is consistent with malicious activity, specifically data exfiltration.

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

The code contains several concerning elements, including the installation of packages without user consent and the caching of sensitive user data. These behaviors suggest potential malicious intent and warrant a moderate to high risk assessment.

While the script itself is not necessarily malicious, it is performing a network operation by pinging a hostname. This behavior could be used for reconnaissance or to establish a connection with a potentially malicious server.

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

The code collects and sends potentially sensitive system information to a remote server without user consent. This behavior is indicative of malicious intent and poses a significant security risk.

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

The code is part of a tool that provides extensive system-level access and manipulation capabilities. While it is not inherently malicious, its functionalities can be used for both legitimate and malicious purposes, depending on the context and user intent.

The code exhibits malicious behavior by intercepting network requests and sending data to an external server without user consent.

The script attempts to run a JSON file called 'index.json' using Node.js. This behavior is considered suspicious and could potentially execute malicious code.

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

The script collects hostname, home directory, current directory, and IP addresses, then encodes the data and sends it as DNS queries to a hardcoded DNS server. Additionally, it sends an HTTP request to a hardcoded URL.

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

This file executes shell commands (e.g., hostname, pwd, whoami) and retrieves the public IP address, then exfiltrates the collected data to 1wy3rk316x8qqy4fyxtvcs4kkbq2es2h[.]oastify[.]com using curl. This unauthorized data exfiltration poses a severe security risk.

This script is designed to exfiltrate sensitive information from the user's machine to an external server, indicating malicious behavior.

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

This file defines a function that sends potentially sensitive data (via the 'key' parameter) to basseqwevewcewcewecwcw[.]xyz, a suspicious domain. The request includes a hardcoded cookie and embeds unvalidated user input in both the URL and POST body, indicating potential data exfiltration or unauthorized data transmission.

This script is designed to exfiltrate potentially sensitive information to a remote server, indicating malicious behavior.

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

The code exhibits behavior consistent with malware by collecting and transmitting sensitive system data to an external server. This poses a significant security risk due to the potential misuse of the data.

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

The code is part of a C2 framework used for remote control, which can be misused if deployed in unauthorized contexts. The insecure TLS configuration is a notable security risk. While the code itself is not malicious, its potential for misuse in unauthorized scenarios is significant.

The code is designed to exfiltrate sensitive system data to a remote server, which is a significant security risk and indicative of malicious behavior.

The code poses significant security risks due to the execution of shell commands and potential data exfiltration to an external site. The use of 'exec' without input validation and the sending of sensitive data are major concerns.

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

The file contains code that secretly gathers detailed system information, such as hostname, OS type, platform, release, architecture, local IP addresses, public IP address (fetched via an external API), username, and current working directory. It then transmits this data to external endpoints via HTTP GET and POST requests, and uses a WebSocket connection as a fallback. The endpoints are hardcoded, for example, to URLs like http://example.com/jpd3.php, http://example.com/jpd4.php, and wss://example.com/socket, which are not transparent or verified services. This behavior is indicative of malware designed for unauthorized data exfiltration.

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

The code is highly suspicious due to its collection and transmission of system information to external servers without user consent. The use of hardcoded IP addresses and fallback mechanisms for data transmission indicates potential malicious intent.

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

The analyzed source code is malicious and performs unauthorized data exfiltration of sensitive system and user information to a suspicious external server. This constitutes a critical supply chain security risk and privacy violation. The code should be considered malware with high confidence, and the package containing it should be avoided or removed immediately.

Live on npm for 53 days, 16 hours and 55 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 21 minutes before removal. Socket users were protected even while the package was live.

The code is performing unauthorized data exfiltration by sending system information to a remote server. This is a clear indication of malicious behavior, posing a significant security risk.

Live on npm for 1 hour and 47 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 11 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.

The script is designed to send sensitive system information to an external server, which poses a significant security risk and is indicative of malicious behavior.

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

The script collects sensitive user information from the Discord API, including usernames, emails, and IDs, and saves it to a file without user consent. It automates interactions with Discord, including sending unsolicited messages to channels (spamming), and uses a captcha solving service to bypass security measures. The script contains hardcoded API keys and tokens, posing significant security risks if shared or leaked. Additionally, it includes obfuscated JavaScript code to manipulate local storage tokens, suggesting attempts to hijack or misuse user accounts.

The code is designed to send sensitive system information to a remote server, which is a significant security risk. This behavior is consistent with malicious activity, specifically data exfiltration.

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

The code contains several concerning elements, including the installation of packages without user consent and the caching of sensitive user data. These behaviors suggest potential malicious intent and warrant a moderate to high risk assessment.

While the script itself is not necessarily malicious, it is performing a network operation by pinging a hostname. This behavior could be used for reconnaissance or to establish a connection with a potentially malicious server.

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

The code collects and sends potentially sensitive system information to a remote server without user consent. This behavior is indicative of malicious intent and poses a significant security risk.

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

The code is part of a tool that provides extensive system-level access and manipulation capabilities. While it is not inherently malicious, its functionalities can be used for both legitimate and malicious purposes, depending on the context and user intent.

The code exhibits malicious behavior by intercepting network requests and sending data to an external server without user consent.

The script attempts to run a JSON file called 'index.json' using Node.js. This behavior is considered suspicious and could potentially execute malicious code.

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

The script collects hostname, home directory, current directory, and IP addresses, then encodes the data and sends it as DNS queries to a hardcoded DNS server. Additionally, it sends an HTTP request to a hardcoded URL.

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

This file executes shell commands (e.g., hostname, pwd, whoami) and retrieves the public IP address, then exfiltrates the collected data to 1wy3rk316x8qqy4fyxtvcs4kkbq2es2h[.]oastify[.]com using curl. This unauthorized data exfiltration poses a severe security risk.

This script is designed to exfiltrate sensitive information from the user's machine to an external server, indicating malicious behavior.

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

This file defines a function that sends potentially sensitive data (via the 'key' parameter) to basseqwevewcewcewecwcw[.]xyz, a suspicious domain. The request includes a hardcoded cookie and embeds unvalidated user input in both the URL and POST body, indicating potential data exfiltration or unauthorized data transmission.

This script is designed to exfiltrate potentially sensitive information to a remote server, indicating malicious behavior.

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

The code exhibits behavior consistent with malware by collecting and transmitting sensitive system data to an external server. This poses a significant security risk due to the potential misuse of the data.

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

The code is part of a C2 framework used for remote control, which can be misused if deployed in unauthorized contexts. The insecure TLS configuration is a notable security risk. While the code itself is not malicious, its potential for misuse in unauthorized scenarios is significant.

The code is designed to exfiltrate sensitive system data to a remote server, which is a significant security risk and indicative of malicious behavior.

The code poses significant security risks due to the execution of shell commands and potential data exfiltration to an external site. The use of 'exec' without input validation and the sending of sensitive data are major concerns.

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