Secure your dependencies. Ship with confidence.

The code reads sensitive system information, including the '/etc/passwd' file, and sends it over the network to a dynamically generated external domain that is likely used for collecting data from compromised systems. The use of insecure HTTPS settings and the nature of the transmitted data suggest a high probability of malicious behavior and a 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 28 minutes before removal. Socket users were protected even while the package was live.

The code is designed to exfiltrate the username of the current user by encoding it and sending it to an external domain. This behavior is indicative of malicious intent, as it involves unauthorized data transmission.

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

This file is encrypted with PyArmor

The script sends HTTP requests to an unspecified address, which could lead to data exfiltration or other malicious behavior.

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

This file is encrypted with PyArmor

This script is likely being used to collect sensitive data from the user's system and send it to a remote server. This represents a breach of privacy and can be seen as a form of malware.

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

The code snippet shows several potential anomalies: unusual module names that might indicate typo or unfamiliar libraries, and the usage of a `functame` method whose behavior is not defined in this snippet. This raises suspicion about the origin and intent of these modules, suggesting the need for further review of these dependencies. Without more information on these modules, it's difficult to assess the full scope of potential security risks.

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

The code sends tracking data to an external server without user consent, posing a privacy violation and potential security risk. The code should be removed or modified to obtain user consent and disclose the data being collected and transmitted.

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

This file is encrypted with PyArmor

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 3 days, 10 hours and 11 minutes before removal. Socket users were protected even while the package was live.

The code is malicious as it collects sensitive system information and exfiltrates it to an external server without user consent. This behavior is typical of data theft and unauthorized data transmission.

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

This file is encrypted with PyArmor

This file is encrypted with PyArmor

The provided source code exhibits clear signs of malicious behavior, including data exfiltration and connecting to suspicious domains. The actions taken by the code pose a significant security risk.

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

The code exhibits potential security risks such as data leakage through manual token management, hard-coded credentials, and the use of 'localStorage' without proper protection. These issues could lead to unauthorized access to sensitive information and data exposure. Therefore, a thorough security review and refactoring of the code are recommended to address these concerns.

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

This file is encrypted with PyArmor

The code exhibits behavior consistent with a backdoor designed for unauthorized data collection and exfiltration. The collection of sensitive data and its transmission to a suspicious domain without user consent suggests malicious intent. The package should be considered compromised and not used in any production environment.

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

This file is encrypted with PyArmor

The code is designed to collect sensitive system information and transmit it to an external server using obfuscated methods. This behavior is indicative of malicious activity, specifically data exfiltration.

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

The code is intentionally designed to exfiltrate sensitive data to a remote server with a suspicious and obfuscated domain name, indicative of a supply chain attack. The lack of user consent and the nature of the data collected suggest malicious intent.

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

This script is highly suspicious and indicates a malicious intent. It attempts to establish a reverse shell connection, which can be used for unauthorized access and control of the system.

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

The code reads sensitive system information, including the '/etc/passwd' file, and sends it over the network to a dynamically generated external domain that is likely used for collecting data from compromised systems. The use of insecure HTTPS settings and the nature of the transmitted data suggest a high probability of malicious behavior and a 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 28 minutes before removal. Socket users were protected even while the package was live.

The code is designed to exfiltrate the username of the current user by encoding it and sending it to an external domain. This behavior is indicative of malicious intent, as it involves unauthorized data transmission.

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

This file is encrypted with PyArmor

The script sends HTTP requests to an unspecified address, which could lead to data exfiltration or other malicious behavior.

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

This file is encrypted with PyArmor

This script is likely being used to collect sensitive data from the user's system and send it to a remote server. This represents a breach of privacy and can be seen as a form of malware.

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

The code snippet shows several potential anomalies: unusual module names that might indicate typo or unfamiliar libraries, and the usage of a `functame` method whose behavior is not defined in this snippet. This raises suspicion about the origin and intent of these modules, suggesting the need for further review of these dependencies. Without more information on these modules, it's difficult to assess the full scope of potential security risks.

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

The code sends tracking data to an external server without user consent, posing a privacy violation and potential security risk. The code should be removed or modified to obtain user consent and disclose the data being collected and transmitted.

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

This file is encrypted with PyArmor

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 3 days, 10 hours and 11 minutes before removal. Socket users were protected even while the package was live.

The code is malicious as it collects sensitive system information and exfiltrates it to an external server without user consent. This behavior is typical of data theft and unauthorized data transmission.

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

This file is encrypted with PyArmor

This file is encrypted with PyArmor

The provided source code exhibits clear signs of malicious behavior, including data exfiltration and connecting to suspicious domains. The actions taken by the code pose a significant security risk.

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

The code exhibits potential security risks such as data leakage through manual token management, hard-coded credentials, and the use of 'localStorage' without proper protection. These issues could lead to unauthorized access to sensitive information and data exposure. Therefore, a thorough security review and refactoring of the code are recommended to address these concerns.

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

This file is encrypted with PyArmor

The code exhibits behavior consistent with a backdoor designed for unauthorized data collection and exfiltration. The collection of sensitive data and its transmission to a suspicious domain without user consent suggests malicious intent. The package should be considered compromised and not used in any production environment.

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

This file is encrypted with PyArmor

The code is designed to collect sensitive system information and transmit it to an external server using obfuscated methods. This behavior is indicative of malicious activity, specifically data exfiltration.

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

The code is intentionally designed to exfiltrate sensitive data to a remote server with a suspicious and obfuscated domain name, indicative of a supply chain attack. The lack of user consent and the nature of the data collected suggest malicious intent.

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

This script is highly suspicious and indicates a malicious intent. It attempts to establish a reverse shell connection, which can be used for unauthorized access and control of the system.

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