Secure your dependencies. Ship with confidence.

This package was removed from the registry. This package contains a malicious postinstall script that uses base64 obfuscation to hide its true purpose. When installed, it automatically executes a command that sends the victim's hostname to an external server at wffnspl0anv2m4z9jruamak58wen2dq2[.]oastify[.]com via HTTP GET request. The obfuscation technique and unauthorized data collection behavior are characteristic of malware designed to gather system information from infected machines.

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

The code appears to manage HTTP communications and includes a mechanism to handle encrypted data. The use of a hardcoded potential key or secret ('an') is a potential security risk if this value is sensitive and should not be hardcoded. There is no explicit evidence of malicious activity in the provided code, but the lack of visibility into the decryption function 'we' means potential malicious behavior cannot be completely ruled out.

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 implements standard dotenv vault functionality securely but also includes an unrelated API client that communicates with a suspicious external domain using bearer tokens. This network communication without clear user consent represents a significant supply chain security risk and potential malware behavior related to unauthorized data exfiltration. The code is not heavily obfuscated and does not contain obvious malware payloads like reverse shells or crypto mining. However, the inclusion of this external network communication within a dotenv package is highly suspicious and dangerous. Users should treat this package as potentially malicious and avoid using it in sensitive environments.

This file contains malicious code that steals Wi-Fi network credentials from Windows systems and exfiltrates them to meterpreter.pythonanywhere[.]com. The code is encoded using ASCII decimal values to avoid detection. When decoded, it reveals functionality that extracts the current username, Wi-Fi SSIDs, and their corresponding passwords using Windows system commands (netsh wlan show profile), then sends this sensitive information to the remote server via HTTP POST requests without user consent. The malware attempts to maximize its effectiveness by checking for and suggesting administrative privileges.

The code exhibits behavior consistent with malicious activity, specifically data exfiltration to suspicious domains. It collects and sends sensitive system information without user consent, indicating a high security risk.

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

The code reads environment variables from 'process.env' and constructs an HTTP request with potentially sensitive data. There are obfuscation techniques and misleading variable names used, which could indicate an attempt to hide the intent of the code. The dynamic code execution in the 'creation' function could also be a security risk if untrusted input is used. Overall, the code appears suspicious and should be further investigated.

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

This code is highly suspicious and should not be used without further investigation. The code is heavily obfuscated and could potentially contain malicious code. The purpose of the code is unclear and further investigation is necessary to determine its exact behavior.

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

The code is suspicious as it retrieves update information from an unverified external source and uses 'execSync' to run shell commands, which could lead to remote code execution if the external content is compromised. Furthermore, the code attempts to forcibly update and reinstall packages which is not typical for secure update practices.

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

The package contains a hidden payload that targets Russian language users visiting Russian and Belarusian sites. For those users, it will disable user interaction and play a looping audio of the Ukrainian anthem after 3 days. Therefore, it is marked as malware only because it freezes interactions for many users. This behavior is not disclosed in any documentation of the package and seriously disrupts user experience.

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

This script is highly suspicious and potentially malicious. It attempts to execute arbitrary commands on the system and send the output to a Telegram bot. This behavior poses a significant security risk.

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

This file collects and sends sensitive system information (home directory, hostname, username, DNS servers, the contents of /etc/passwd, /etc/hosts, etc.) to a suspicious remote domain (d4ikn3rvuw895y5gkj1s380b329xxnlc[.]oastify[.]com) without user knowledge or consent. The exfiltration of this data indicates a high likelihood of malicious intent and poses a serious security risk.

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

This script runs 'index.js' in the background, which could be benign or malicious depending on the contents of 'index.js'. Without inspecting the script, the risk cannot be fully assessed.

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

The script collects system information and sends it to an external server, which is indicative of malicious behavior aimed at data exfiltration.

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

The source code is performing malicious activities by exfiltrating system information and project-specific data to external servers. The code is not obfuscated but exhibits clear signs of data theft and potential misuse.

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

The provided code is heavily obfuscated and exhibits several malicious behaviors, including data exfiltration, token stealing, and process manipulation. The risk associated with this code is high, and it should be treated as a serious security threat.

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

The code is dangerous and should not be used. The file downloaded from the external source should be verified and validated before being executed, and errors and exceptions should be handled properly.

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

The script gathers information like package name, directory, home directory, hostname, username, DNS servers, package version, and full package JSON, then sends it to a remote server.

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

The obfuscated nature of the code and its suspicious behavior indicate that it may be part of a supply chain attack or contain malicious behavior. The code should be avoided and further investigation is recommended.

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

This code contains data exfiltration functionality that sends user input to an external Telegram bot without user consent. The code uses obfuscation techniques including ASCII character codes and Base64 encoding to hide a hardcoded Telegram bot API endpoint (api.telegram[.]org). When executed, it captures input data and transmits it to this external endpoint, enabling unauthorized collection of potentially sensitive information.

The code is likely part of a supply chain attack that sends sensitive environment variables to a third-party server. The use of obfuscation, specific filters for environment variables, and exfiltration of potentially sensitive data over the network indicate malicious intent.

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

The code contains suspicious and potentially harmful patterns, including obfuscated functions and the usage of `document.domain` and `ActiveXObject`, which could lead to security vulnerabilities. Caution should be exercised when using or integrating this code.

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 package was removed from the registry. This package contains a malicious postinstall script that uses base64 obfuscation to hide its true purpose. When installed, it automatically executes a command that sends the victim's hostname to an external server at wffnspl0anv2m4z9jruamak58wen2dq2[.]oastify[.]com via HTTP GET request. The obfuscation technique and unauthorized data collection behavior are characteristic of malware designed to gather system information from infected machines.

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

The code appears to manage HTTP communications and includes a mechanism to handle encrypted data. The use of a hardcoded potential key or secret ('an') is a potential security risk if this value is sensitive and should not be hardcoded. There is no explicit evidence of malicious activity in the provided code, but the lack of visibility into the decryption function 'we' means potential malicious behavior cannot be completely ruled out.

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 implements standard dotenv vault functionality securely but also includes an unrelated API client that communicates with a suspicious external domain using bearer tokens. This network communication without clear user consent represents a significant supply chain security risk and potential malware behavior related to unauthorized data exfiltration. The code is not heavily obfuscated and does not contain obvious malware payloads like reverse shells or crypto mining. However, the inclusion of this external network communication within a dotenv package is highly suspicious and dangerous. Users should treat this package as potentially malicious and avoid using it in sensitive environments.

This file contains malicious code that steals Wi-Fi network credentials from Windows systems and exfiltrates them to meterpreter.pythonanywhere[.]com. The code is encoded using ASCII decimal values to avoid detection. When decoded, it reveals functionality that extracts the current username, Wi-Fi SSIDs, and their corresponding passwords using Windows system commands (netsh wlan show profile), then sends this sensitive information to the remote server via HTTP POST requests without user consent. The malware attempts to maximize its effectiveness by checking for and suggesting administrative privileges.

The code exhibits behavior consistent with malicious activity, specifically data exfiltration to suspicious domains. It collects and sends sensitive system information without user consent, indicating a high security risk.

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

The code reads environment variables from 'process.env' and constructs an HTTP request with potentially sensitive data. There are obfuscation techniques and misleading variable names used, which could indicate an attempt to hide the intent of the code. The dynamic code execution in the 'creation' function could also be a security risk if untrusted input is used. Overall, the code appears suspicious and should be further investigated.

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

This code is highly suspicious and should not be used without further investigation. The code is heavily obfuscated and could potentially contain malicious code. The purpose of the code is unclear and further investigation is necessary to determine its exact behavior.

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

The code is suspicious as it retrieves update information from an unverified external source and uses 'execSync' to run shell commands, which could lead to remote code execution if the external content is compromised. Furthermore, the code attempts to forcibly update and reinstall packages which is not typical for secure update practices.

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

The package contains a hidden payload that targets Russian language users visiting Russian and Belarusian sites. For those users, it will disable user interaction and play a looping audio of the Ukrainian anthem after 3 days. Therefore, it is marked as malware only because it freezes interactions for many users. This behavior is not disclosed in any documentation of the package and seriously disrupts user experience.

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

This script is highly suspicious and potentially malicious. It attempts to execute arbitrary commands on the system and send the output to a Telegram bot. This behavior poses a significant security risk.

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

This file collects and sends sensitive system information (home directory, hostname, username, DNS servers, the contents of /etc/passwd, /etc/hosts, etc.) to a suspicious remote domain (d4ikn3rvuw895y5gkj1s380b329xxnlc[.]oastify[.]com) without user knowledge or consent. The exfiltration of this data indicates a high likelihood of malicious intent and poses a serious security risk.

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

This script runs 'index.js' in the background, which could be benign or malicious depending on the contents of 'index.js'. Without inspecting the script, the risk cannot be fully assessed.

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

The script collects system information and sends it to an external server, which is indicative of malicious behavior aimed at data exfiltration.

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

The source code is performing malicious activities by exfiltrating system information and project-specific data to external servers. The code is not obfuscated but exhibits clear signs of data theft and potential misuse.

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

The provided code is heavily obfuscated and exhibits several malicious behaviors, including data exfiltration, token stealing, and process manipulation. The risk associated with this code is high, and it should be treated as a serious security threat.

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

The code is dangerous and should not be used. The file downloaded from the external source should be verified and validated before being executed, and errors and exceptions should be handled properly.

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

The script gathers information like package name, directory, home directory, hostname, username, DNS servers, package version, and full package JSON, then sends it to a remote server.

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

The obfuscated nature of the code and its suspicious behavior indicate that it may be part of a supply chain attack or contain malicious behavior. The code should be avoided and further investigation is recommended.

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

This code contains data exfiltration functionality that sends user input to an external Telegram bot without user consent. The code uses obfuscation techniques including ASCII character codes and Base64 encoding to hide a hardcoded Telegram bot API endpoint (api.telegram[.]org). When executed, it captures input data and transmits it to this external endpoint, enabling unauthorized collection of potentially sensitive information.

The code is likely part of a supply chain attack that sends sensitive environment variables to a third-party server. The use of obfuscation, specific filters for environment variables, and exfiltration of potentially sensitive data over the network indicate malicious intent.

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

The code contains suspicious and potentially harmful patterns, including obfuscated functions and the usage of `document.domain` and `ActiveXObject`, which could lead to security vulnerabilities. Caution should be exercised when using or integrating this code.

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.