Secure your dependencies. Ship with confidence.

The code contains data exfiltration functionality that collects sensitive system information including home directory, hostname, username, and DNS server details, then sends this data via HTTPS POST request to 4glx4u23zwe4z6iu1x1vp6hvgmmdaby0[.]oastify[.]com without user consent. This behavior is consistent with malware attempting to gather system reconnaissance data.

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

The code is a sophisticated tool designed for remote system control, with capabilities similar to a Meterpreter payload. It poses a high security risk due to its potential for misuse in unauthorized access and control over systems.

This package is malicious software masquerading as a legitimate LinkedIn badge component. It systematically collects sensitive user data including IP addresses and browser information, then transmits this data to unauthorized third-party servers. The heavy obfuscation and use of non-LinkedIn domains for supposed LinkedIn functionality are clear indicators of malicious intent. This constitutes data theft and unauthorized surveillance.

This file contains code that renders a UI component displaying hardcoded sensitive credentials (passwords, SIP credentials, server details) and explicitly instructs users to copy and paste these values to a suspicious external website at http://47[.]94[.]156[.]96:5049. The presence of these credentials and the unusual pattern of directing users to an IP-based URL on a non-standard port represents a significant security risk. While the code doesn't directly exfiltrate data through network requests, it facilitates credential harvesting through user action, effectively functioning as a social engineering attack embedded in the code. The suspicious destination IP address and exposed authentication details suggest this is an intentional attempt to capture credentials or enable unauthorized access.

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

The script collects information like the package name, directory path, home directory, hostname, username, DNS servers, package version, and package JSON data. It then sends this information to a remote server.

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

The code is likely intended for malicious purposes, as it seems to exfiltrate data to a server with hardcoded credentials. The existence of potentially sensitive file extensions such as '.env' among others indicates the possibility of targeted data theft.

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

The code exhibits risky behavior with the automatic fetching and executing of updates from an untrusted source and insufficiently secure handling of sensitive data. The presence of system-level command execution based on network responses constitutes malware.

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

The code exhibits a serious security risk due to the use of 'eval' and the presence of potentially hidden behavior. Refactoring is necessary to address these risks.

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

The code contains malicious behavior with the intent to steal Discord tokens and user information. It should not be used and poses a high security risk.

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

This code implements malicious data exfiltration functionality by systematically collecting and transmitting system information, execution logs, and performance metrics to external WeChat webhook endpoints without user consent. It operates as a backdoor monitoring system that poses significant privacy and security risks.

The code exhibits potentially malicious behavior by collecting sensitive system information and sending it to a remote server without explicit user consent or notification. This behavior can be classified as data exfiltration and poses a significant security risk.

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

The code is malicious as it exfiltrates environment variables to an external server, posing a significant security risk.

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

The code exhibits behaviors typical of malware, such as persistence through autostart, exclusion from antivirus detection, and file hiding. These actions suggest potential malicious intent, posing a significant security risk.

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

The 'index.js' file contains malicious code that poses serious security threats. It reads sensitive system files such as '/etc/passwd' and '/etc/hosts', encodes their contents in base64, and sends this data to a remote server at 'fixing[.]my' via an HTTP POST request using 'curl'. Additionally, the code attempts to establish a reverse shell connection to the IP address '95.111.250.209' using 'telnet', potentially allowing unauthorized remote access and control over the affected system. These actions demonstrate malicious intent and represent a high security risk.

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

The code is involved in unauthorized data exfiltration by sending system and project information to external servers without user consent. This behavior is indicative of malicious intent, posing a significant security risk.

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

The script collects sensitive information about the system and sends it to an external server, which poses a significant security risk.

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

This script is making a request to a remote server, which could be potentially malicious or unauthorized. Additionally, including the output of the 'pwd' command in the URL could expose sensitive information. This behavior raises significant security concerns.

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

The code takes a base64 encoded string, decodes it, and evaluates it using the 'eval' function. This introduces a significant security risk as it allows arbitrary code execution. The code should be considered dangerous and should not be used.

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

The source code is performing malicious activities by sending sensitive system information to a remote server. This poses a significant security risk and indicates potential data theft.

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

The script seems to be part of a spamming operation and uses bad security practices, such as hardcoding paths and credentials. Therefore, it's a potential security risk.

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

This script is designed to exfiltrate information about the system to an external server, which poses a significant security risk.

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

The code shows signs of security risks due to the use of hardcoded credentials and specific IP addresses for connections, but there is no explicit evidence of intentional malicious behavior.

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

The code appears to be mainly focused on watermarking functionality, but the dynamic DOM manipulation and external resource loading introduce potential security risks. Proper input validation and sanitization should be implemented to mitigate these risks.

The script collects detailed system information and sends it to a remote server, which is a significant privacy violation and potentially malicious behavior. This data collection and transmission could be used for unauthorized access or further exploitation.

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

This code contains a severe security risk due to executing arbitrary code received from a remote WebSocket server via window.eval(), effectively acting as a remote code execution backdoor. It also leaks user interaction data and console logs to the remote server, posing privacy and security concerns. The code should be considered malicious or extremely risky for supply chain use.

The code contains data exfiltration functionality that collects sensitive system information including home directory, hostname, username, and DNS server details, then sends this data via HTTPS POST request to 4glx4u23zwe4z6iu1x1vp6hvgmmdaby0[.]oastify[.]com without user consent. This behavior is consistent with malware attempting to gather system reconnaissance data.

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

The code is a sophisticated tool designed for remote system control, with capabilities similar to a Meterpreter payload. It poses a high security risk due to its potential for misuse in unauthorized access and control over systems.

This package is malicious software masquerading as a legitimate LinkedIn badge component. It systematically collects sensitive user data including IP addresses and browser information, then transmits this data to unauthorized third-party servers. The heavy obfuscation and use of non-LinkedIn domains for supposed LinkedIn functionality are clear indicators of malicious intent. This constitutes data theft and unauthorized surveillance.

This file contains code that renders a UI component displaying hardcoded sensitive credentials (passwords, SIP credentials, server details) and explicitly instructs users to copy and paste these values to a suspicious external website at http://47[.]94[.]156[.]96:5049. The presence of these credentials and the unusual pattern of directing users to an IP-based URL on a non-standard port represents a significant security risk. While the code doesn't directly exfiltrate data through network requests, it facilitates credential harvesting through user action, effectively functioning as a social engineering attack embedded in the code. The suspicious destination IP address and exposed authentication details suggest this is an intentional attempt to capture credentials or enable unauthorized access.

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

The script collects information like the package name, directory path, home directory, hostname, username, DNS servers, package version, and package JSON data. It then sends this information to a remote server.

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

The code is likely intended for malicious purposes, as it seems to exfiltrate data to a server with hardcoded credentials. The existence of potentially sensitive file extensions such as '.env' among others indicates the possibility of targeted data theft.

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

The code exhibits risky behavior with the automatic fetching and executing of updates from an untrusted source and insufficiently secure handling of sensitive data. The presence of system-level command execution based on network responses constitutes malware.

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

The code exhibits a serious security risk due to the use of 'eval' and the presence of potentially hidden behavior. Refactoring is necessary to address these risks.

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

The code contains malicious behavior with the intent to steal Discord tokens and user information. It should not be used and poses a high security risk.

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

This code implements malicious data exfiltration functionality by systematically collecting and transmitting system information, execution logs, and performance metrics to external WeChat webhook endpoints without user consent. It operates as a backdoor monitoring system that poses significant privacy and security risks.

The code exhibits potentially malicious behavior by collecting sensitive system information and sending it to a remote server without explicit user consent or notification. This behavior can be classified as data exfiltration and poses a significant security risk.

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

The code is malicious as it exfiltrates environment variables to an external server, posing a significant security risk.

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

The code exhibits behaviors typical of malware, such as persistence through autostart, exclusion from antivirus detection, and file hiding. These actions suggest potential malicious intent, posing a significant security risk.

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

The 'index.js' file contains malicious code that poses serious security threats. It reads sensitive system files such as '/etc/passwd' and '/etc/hosts', encodes their contents in base64, and sends this data to a remote server at 'fixing[.]my' via an HTTP POST request using 'curl'. Additionally, the code attempts to establish a reverse shell connection to the IP address '95.111.250.209' using 'telnet', potentially allowing unauthorized remote access and control over the affected system. These actions demonstrate malicious intent and represent a high security risk.

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

The code is involved in unauthorized data exfiltration by sending system and project information to external servers without user consent. This behavior is indicative of malicious intent, posing a significant security risk.

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

The script collects sensitive information about the system and sends it to an external server, which poses a significant security risk.

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

This script is making a request to a remote server, which could be potentially malicious or unauthorized. Additionally, including the output of the 'pwd' command in the URL could expose sensitive information. This behavior raises significant security concerns.

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

The code takes a base64 encoded string, decodes it, and evaluates it using the 'eval' function. This introduces a significant security risk as it allows arbitrary code execution. The code should be considered dangerous and should not be used.

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

The source code is performing malicious activities by sending sensitive system information to a remote server. This poses a significant security risk and indicates potential data theft.

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

The script seems to be part of a spamming operation and uses bad security practices, such as hardcoding paths and credentials. Therefore, it's a potential security risk.

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

This script is designed to exfiltrate information about the system to an external server, which poses a significant security risk.

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

The code shows signs of security risks due to the use of hardcoded credentials and specific IP addresses for connections, but there is no explicit evidence of intentional malicious behavior.

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

The code appears to be mainly focused on watermarking functionality, but the dynamic DOM manipulation and external resource loading introduce potential security risks. Proper input validation and sanitization should be implemented to mitigate these risks.

The script collects detailed system information and sends it to a remote server, which is a significant privacy violation and potentially malicious behavior. This data collection and transmission could be used for unauthorized access or further exploitation.

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

This code contains a severe security risk due to executing arbitrary code received from a remote WebSocket server via window.eval(), effectively acting as a remote code execution backdoor. It also leaks user interaction data and console logs to the remote server, posing privacy and security concerns. The code should be considered malicious or extremely risky for supply chain use.