Secure your dependencies. Ship with confidence.

The code engages in automated package creation and publishing, with the addition of posting content to WordPress sites using hard-coded credentials. This indicates potential spam or automated SEO manipulation behavior. The code also presents significant security risks due to hard-coded paths and credentials.

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

The code seems to be modifying the Yarn package manager's behavior in a way that is not transparent to the user. This could be used to suppress errors and modify command-line options, which might lead to malicious packages being installed without being saved to package.json, creating discrepancies in dependencies.

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

The code is malicious, designed to steal sensitive information from users and transmit it to an external server via Telegram. It poses a high security risk due to unauthorized data access and exfiltration.

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

The code is designed to exfiltrate sensitive system information to a remote server without user consent, indicating malicious intent. The risk and malware scores are high due to the nature of the data being collected and transmitted.

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

The code is highly obfuscated and executes a hidden payload, posing a significant security risk. The use of exec() with obfuscated data suggests potential for malicious activity, though the exact nature of the payload is unknown without further deobfuscation.

Live on PyPI for 2 days, 14 hours and 42 minutes before removal. Socket users were protected even while the package was live.

The code is likely intended for malicious use, specifically data exfiltration. The obfuscation, use of system information gathering, dynamic DNS construction with encoded system data, and sending this data to a remote server via ping command are indicators of malicious intent. The code does not directly damage system files or steal credentials in a traditional sense, but it violates user privacy by leaking system information.

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

The code contains clear indicators of malicious behavior. It collects sensitive information such as tokens, user data, and system information, and sends it to a Discord webhook. The obfuscation techniques used in the code further indicate an intent to hide its true functionality.

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

This code is intentionally obfuscated and uses DNS queries to exfiltrate system information, which could be a significant security risk. The hardcoded domain and the potential data exfiltration raise concerns about privacy violations. This package should be reviewed carefully before being used.

The script is designed to collect sensitive data from the system and send it to an external server, which is a clear indication of malicious behavior.

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

The code fetches JavaScript from an external HTTP URL (http://c[.]jiangwenqiang[.]com/api/juejing_eval.js) and conditionally executes it using eval() when a parameter is truthy. This creates a remotely-controlled backdoor that enables arbitrary code execution, representing a critical supply chain attack vector. The use of unencrypted HTTP makes the connection vulnerable to man-in-the-middle attacks, allowing potential code injection during transit. The code also contains a typo in the module export statement that may hinder detection or usage.

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

This code is intentionally obfuscated and uses DNS queries to exfiltrate system information, which could be a significant security risk. The hardcoded domain and the potential data exfiltration raise concerns about privacy violations. This package should be reviewed carefully before being used.

The code is performing a potentially malicious action by sending sensitive information (environment variables and cookies) to an external server without user consent. This poses a significant security risk.

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

The code demonstrates several security risks, particularly the direct execution of commands based on user input, which can lead to command injection vulnerabilities and unauthorized file manipulation. It also lacks proper sanitization and validation of user input. The overall structure raises significant concerns regarding the potential for malicious behavior, especially if used in an untrusted environment.

The code is collecting sensitive system information and sending it to a remote server. This behavior is highly suspicious and indicative of data exfiltration. The remote server URL is particularly concerning, as it suggests potential unauthorized data collection.

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

The code poses a significant security risk due to the potential for data exfiltration to a suspicious domain and the execution of shell commands without input sanitization. This behavior could be considered malicious.

The script is downloading a file from a remote server. This behavior can be potentially risky as the content of the file is unknown and could be malicious.

The script makes an HTTP request to a remote server, which raises significant security concerns. The URL appears suspicious and could be used for data exfiltration or other malicious purposes.

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

This script contains a command injection vulnerability that could be used to execute arbitrary code on the system. The script contains a base64 encoded shell command that decodes to 'whoami' and could be used to verify the vulnerability.

The code presents significant security concerns due to the presence of hard-coded credentials and an 'exit(0)' statement that terminates the script early, making the subsequent code unreachable. While the overall purpose of the code seems legitimate, the identified anomalies raise significant security concerns.

Live on PyPI for 87 days, 15 hours and 22 minutes before removal. Socket users were protected even while the package was live.

This code is dangerous and suspicious. It retrieves sensitive system information and exfiltrates it to an external server through DNS queries, which can easily bypass standard security measures. The code should not be used and should be flagged as a security risk.

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

The code exhibits malicious behavior by collecting and transmitting sensitive system information to a suspicious domain without user consent. This poses a significant security risk.

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

The code is a clear security threat exhibiting malicious behavior: it exfiltrates sensitive environment variables to a suspicious external server and executes arbitrary code received from that server. The obfuscation and use of eval confirm intent to hide this backdoor functionality. This module should be considered malware and avoided.

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

The code exhibits several concerning behaviors, including the use of hardcoded credentials, subprocess execution with potential for command injection, and interactions with external websites. These activities pose a significant security risk and should be further investigated.

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

While there doesn't appear to be any overtly malicious activity such as data theft or system damage, the code does contain some potential security risks and bad practices, including the use of hard-coded credentials and automated publication of potentially unverified npm packages. The intent of the code is not inherently malicious, but the functionality could potentially be abused.

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

This script is exfiltrating sensitive system information (hostname, current user, current directory) to a remote server without the user's consent. This behavior is highly suspicious and poses a significant security risk.

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

The code engages in automated package creation and publishing, with the addition of posting content to WordPress sites using hard-coded credentials. This indicates potential spam or automated SEO manipulation behavior. The code also presents significant security risks due to hard-coded paths and credentials.

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

The code seems to be modifying the Yarn package manager's behavior in a way that is not transparent to the user. This could be used to suppress errors and modify command-line options, which might lead to malicious packages being installed without being saved to package.json, creating discrepancies in dependencies.

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

The code is malicious, designed to steal sensitive information from users and transmit it to an external server via Telegram. It poses a high security risk due to unauthorized data access and exfiltration.

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

The code is designed to exfiltrate sensitive system information to a remote server without user consent, indicating malicious intent. The risk and malware scores are high due to the nature of the data being collected and transmitted.

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

The code is highly obfuscated and executes a hidden payload, posing a significant security risk. The use of exec() with obfuscated data suggests potential for malicious activity, though the exact nature of the payload is unknown without further deobfuscation.

Live on PyPI for 2 days, 14 hours and 42 minutes before removal. Socket users were protected even while the package was live.

The code is likely intended for malicious use, specifically data exfiltration. The obfuscation, use of system information gathering, dynamic DNS construction with encoded system data, and sending this data to a remote server via ping command are indicators of malicious intent. The code does not directly damage system files or steal credentials in a traditional sense, but it violates user privacy by leaking system information.

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

The code contains clear indicators of malicious behavior. It collects sensitive information such as tokens, user data, and system information, and sends it to a Discord webhook. The obfuscation techniques used in the code further indicate an intent to hide its true functionality.

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

This code is intentionally obfuscated and uses DNS queries to exfiltrate system information, which could be a significant security risk. The hardcoded domain and the potential data exfiltration raise concerns about privacy violations. This package should be reviewed carefully before being used.

The script is designed to collect sensitive data from the system and send it to an external server, which is a clear indication of malicious behavior.

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

The code fetches JavaScript from an external HTTP URL (http://c[.]jiangwenqiang[.]com/api/juejing_eval.js) and conditionally executes it using eval() when a parameter is truthy. This creates a remotely-controlled backdoor that enables arbitrary code execution, representing a critical supply chain attack vector. The use of unencrypted HTTP makes the connection vulnerable to man-in-the-middle attacks, allowing potential code injection during transit. The code also contains a typo in the module export statement that may hinder detection or usage.

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

This code is intentionally obfuscated and uses DNS queries to exfiltrate system information, which could be a significant security risk. The hardcoded domain and the potential data exfiltration raise concerns about privacy violations. This package should be reviewed carefully before being used.

The code is performing a potentially malicious action by sending sensitive information (environment variables and cookies) to an external server without user consent. This poses a significant security risk.

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

The code demonstrates several security risks, particularly the direct execution of commands based on user input, which can lead to command injection vulnerabilities and unauthorized file manipulation. It also lacks proper sanitization and validation of user input. The overall structure raises significant concerns regarding the potential for malicious behavior, especially if used in an untrusted environment.

The code is collecting sensitive system information and sending it to a remote server. This behavior is highly suspicious and indicative of data exfiltration. The remote server URL is particularly concerning, as it suggests potential unauthorized data collection.

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

The code poses a significant security risk due to the potential for data exfiltration to a suspicious domain and the execution of shell commands without input sanitization. This behavior could be considered malicious.

The script is downloading a file from a remote server. This behavior can be potentially risky as the content of the file is unknown and could be malicious.

The script makes an HTTP request to a remote server, which raises significant security concerns. The URL appears suspicious and could be used for data exfiltration or other malicious purposes.

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

This script contains a command injection vulnerability that could be used to execute arbitrary code on the system. The script contains a base64 encoded shell command that decodes to 'whoami' and could be used to verify the vulnerability.

The code presents significant security concerns due to the presence of hard-coded credentials and an 'exit(0)' statement that terminates the script early, making the subsequent code unreachable. While the overall purpose of the code seems legitimate, the identified anomalies raise significant security concerns.

Live on PyPI for 87 days, 15 hours and 22 minutes before removal. Socket users were protected even while the package was live.

This code is dangerous and suspicious. It retrieves sensitive system information and exfiltrates it to an external server through DNS queries, which can easily bypass standard security measures. The code should not be used and should be flagged as a security risk.

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

The code exhibits malicious behavior by collecting and transmitting sensitive system information to a suspicious domain without user consent. This poses a significant security risk.

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

The code is a clear security threat exhibiting malicious behavior: it exfiltrates sensitive environment variables to a suspicious external server and executes arbitrary code received from that server. The obfuscation and use of eval confirm intent to hide this backdoor functionality. This module should be considered malware and avoided.

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

The code exhibits several concerning behaviors, including the use of hardcoded credentials, subprocess execution with potential for command injection, and interactions with external websites. These activities pose a significant security risk and should be further investigated.

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

While there doesn't appear to be any overtly malicious activity such as data theft or system damage, the code does contain some potential security risks and bad practices, including the use of hard-coded credentials and automated publication of potentially unverified npm packages. The intent of the code is not inherently malicious, but the functionality could potentially be abused.

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

This script is exfiltrating sensitive system information (hostname, current user, current directory) to a remote server without the user's consent. This behavior is highly suspicious and poses a significant security risk.

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