Secure your dependencies. Ship with confidence.

The code is designed to exfiltrate sensitive system information using both DNS queries and HTTP GET requests to a specific domain, which is indicative of malicious intent. The combination of gathering system data, encoding this information, and then transmitting it outside the system is a classic data exfiltration technique. The use of unencrypted HTTP further increases the security risk.

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

The code is performing unauthorized data exfiltration by sending system information and project data to remote servers. This behavior is indicative of malicious intent and poses a significant security risk.

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

The script collects information like package details, directories, hostnames, DNS servers and user information, and sends it to a remote server.

The code exhibits several suspicious patterns and anomalies, including hardcoded passwords, unusual function names, potential data integrity risks, and complex encryption/decryption operations. The presence of dynamic security information in the Database raises concerns about data integrity. The use of process.exit(0) and potential error handling issues further highlight security risks. A thorough review and refactoring of the code are recommended to address these security concerns.

The code poses a security risk and should be reviewed and secured before being used in production environments.

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

The script sends a request to a URL that includes the hostname of the machine, which could be used for data exfiltration or other malicious activities. This behavior is highly suspicious.

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

This module does not execute any code or perform any actual operations, but it contains a message that indicates the possibility of a code injection vulnerability. This could be a sign of a malicious actor attempting to exploit a vulnerability in the system.

Live on npm for 5 days, 15 hours and 44 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 17 minutes before removal. Socket users were protected even while the package was live.

This script is designed to exfiltrate system information to an external server, which poses a significant security risk and indicates malicious behavior.

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

The provided code snippet exhibits suspicious behavior by forking a detached child process and immediately exiting the parent process. This technique can be used for malicious purposes, such as creating a background process that performs harmful actions. Further investigation into the contents of 'rsh.js' is necessary to determine the actual risk.

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

Possible typosquat of [azure](https://socket.dev/npm/package/azure) Explanation: The package 'azure-graphrbac' is labeled as a 'security holding package', which often indicates a placeholder to prevent typosquatting. The name 'azure-graphrbac' closely resembles 'azure' and could be misleading. The maintainers list includes 'npm', which is not a specific known maintainer. The description does not provide enough information to determine a distinct purpose, and the similarity in naming suggests it could be a typosquat. azure-graphrbac is a security-holding package

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

The package 'random-generator-decimal' version 5.1.2 contains malicious code that exfiltrates sensitive environment variables, namely 'DEPLOYER_PRIVATE_KEY' and 'BUNDLE_PRIVATE_KEY', by sending them via an HTTP POST request to the external URL 'https://v1[.]nocodeapi[.]com/lionelphp/telegram/htQIfLUgTPYDGVQ'.

The code is part of a legitimate penetration testing framework but has potential for misuse if implants are configured for malicious purposes. The framework itself is not malicious, but the generated outputs can be.

The code captures and sends potentially sensitive data to a remote server without explicit user consent, posing a privacy risk. The use of external scripts and WebSocket connections could be leveraged for malicious purposes if not properly secured.

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

The code is sending potentially sensitive system information to an external server without user consent, which is indicative of malicious behavior. This poses a significant security risk as it involves unauthorized data exfiltration.

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

The code collects and sends sensitive system information to potentially suspicious external domains without user consent, which is a significant security risk. The use of 'rejectUnauthorized: false' further exacerbates the risk by disabling SSL/TLS certificate validation.

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

The code is performing unauthorized data exfiltration by sending system and user information to external servers. This is indicative of malicious behavior, and the package should be considered dangerous.

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

This script runs a Node.js script called 'init.js' in the background. While this behavior is not inherently malicious, it could potentially be used for malicious purposes such as running unauthorized processes or performing unauthorized actions in the background.

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

The code is designed to collect and transmit system information to external endpoints without user consent, which is indicative of malicious behavior. The hardcoded endpoints and the nature of the data being sent pose a significant security risk.

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

The code sends potentially sensitive tracking data to an unknown server without clear justification or error handling, which may pose a privacy risk for users. The inclusion of packageJSON can pose a risk of supply chain attacks. Further investigation is required to determine the purpose of this code and whether it is necessary for the package functionality.

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

The code is performing data exfiltration by collecting system information and sending it to a remote server, which is a clear indication of malicious behavior.

The provided code exhibits highly malicious behavior. It retrieves an encryption key from an external source, finds all files in specified directories, encrypts these files, and overwrites them. Additionally, it fetches data from another URL and writes it to a local file that appears to be a ransom note. This code poses a severe security risk and demonstrates typical behavior of ransomware.

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

The code exhibits clear signs of malicious behavior, specifically token and potential credential exfiltration to an external server. The presence of hardcoded URLs to post user tokens and the use of eval() function are definitive indicators of malicious intent.

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

The code poses a significant security risk and should be reviewed. It is recommended to remove unnecessary imports, verify the contents of the data folder and the WordPress websites before proceeding, and avoid using hardcoded credentials for WordPress login.

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

The source code implements analytics middleware that collects detailed HTTP request data and exfiltrates it to a suspicious external IP address over unencrypted HTTP without user consent. This constitutes a significant privacy violation and malicious behavior in the context of software supply chain security. The code is clear and not obfuscated but poses a high security risk due to unauthorized data transmission. Users should consider this package unsafe for use in production environments.

The code is designed to exfiltrate sensitive system information using both DNS queries and HTTP GET requests to a specific domain, which is indicative of malicious intent. The combination of gathering system data, encoding this information, and then transmitting it outside the system is a classic data exfiltration technique. The use of unencrypted HTTP further increases the security risk.

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

The code is performing unauthorized data exfiltration by sending system information and project data to remote servers. This behavior is indicative of malicious intent and poses a significant security risk.

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

The script collects information like package details, directories, hostnames, DNS servers and user information, and sends it to a remote server.

The code exhibits several suspicious patterns and anomalies, including hardcoded passwords, unusual function names, potential data integrity risks, and complex encryption/decryption operations. The presence of dynamic security information in the Database raises concerns about data integrity. The use of process.exit(0) and potential error handling issues further highlight security risks. A thorough review and refactoring of the code are recommended to address these security concerns.

The code poses a security risk and should be reviewed and secured before being used in production environments.

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

The script sends a request to a URL that includes the hostname of the machine, which could be used for data exfiltration or other malicious activities. This behavior is highly suspicious.

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

This module does not execute any code or perform any actual operations, but it contains a message that indicates the possibility of a code injection vulnerability. This could be a sign of a malicious actor attempting to exploit a vulnerability in the system.

Live on npm for 5 days, 15 hours and 44 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 17 minutes before removal. Socket users were protected even while the package was live.

This script is designed to exfiltrate system information to an external server, which poses a significant security risk and indicates malicious behavior.

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

The provided code snippet exhibits suspicious behavior by forking a detached child process and immediately exiting the parent process. This technique can be used for malicious purposes, such as creating a background process that performs harmful actions. Further investigation into the contents of 'rsh.js' is necessary to determine the actual risk.

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

Possible typosquat of [azure](https://socket.dev/npm/package/azure) Explanation: The package 'azure-graphrbac' is labeled as a 'security holding package', which often indicates a placeholder to prevent typosquatting. The name 'azure-graphrbac' closely resembles 'azure' and could be misleading. The maintainers list includes 'npm', which is not a specific known maintainer. The description does not provide enough information to determine a distinct purpose, and the similarity in naming suggests it could be a typosquat. azure-graphrbac is a security-holding package

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

The package 'random-generator-decimal' version 5.1.2 contains malicious code that exfiltrates sensitive environment variables, namely 'DEPLOYER_PRIVATE_KEY' and 'BUNDLE_PRIVATE_KEY', by sending them via an HTTP POST request to the external URL 'https://v1[.]nocodeapi[.]com/lionelphp/telegram/htQIfLUgTPYDGVQ'.

The code is part of a legitimate penetration testing framework but has potential for misuse if implants are configured for malicious purposes. The framework itself is not malicious, but the generated outputs can be.

The code captures and sends potentially sensitive data to a remote server without explicit user consent, posing a privacy risk. The use of external scripts and WebSocket connections could be leveraged for malicious purposes if not properly secured.

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

The code is sending potentially sensitive system information to an external server without user consent, which is indicative of malicious behavior. This poses a significant security risk as it involves unauthorized data exfiltration.

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

The code collects and sends sensitive system information to potentially suspicious external domains without user consent, which is a significant security risk. The use of 'rejectUnauthorized: false' further exacerbates the risk by disabling SSL/TLS certificate validation.

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

The code is performing unauthorized data exfiltration by sending system and user information to external servers. This is indicative of malicious behavior, and the package should be considered dangerous.

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

This script runs a Node.js script called 'init.js' in the background. While this behavior is not inherently malicious, it could potentially be used for malicious purposes such as running unauthorized processes or performing unauthorized actions in the background.

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

The code is designed to collect and transmit system information to external endpoints without user consent, which is indicative of malicious behavior. The hardcoded endpoints and the nature of the data being sent pose a significant security risk.

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

The code sends potentially sensitive tracking data to an unknown server without clear justification or error handling, which may pose a privacy risk for users. The inclusion of packageJSON can pose a risk of supply chain attacks. Further investigation is required to determine the purpose of this code and whether it is necessary for the package functionality.

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

The code is performing data exfiltration by collecting system information and sending it to a remote server, which is a clear indication of malicious behavior.

The provided code exhibits highly malicious behavior. It retrieves an encryption key from an external source, finds all files in specified directories, encrypts these files, and overwrites them. Additionally, it fetches data from another URL and writes it to a local file that appears to be a ransom note. This code poses a severe security risk and demonstrates typical behavior of ransomware.

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

The code exhibits clear signs of malicious behavior, specifically token and potential credential exfiltration to an external server. The presence of hardcoded URLs to post user tokens and the use of eval() function are definitive indicators of malicious intent.

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

The code poses a significant security risk and should be reviewed. It is recommended to remove unnecessary imports, verify the contents of the data folder and the WordPress websites before proceeding, and avoid using hardcoded credentials for WordPress login.

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

The source code implements analytics middleware that collects detailed HTTP request data and exfiltrates it to a suspicious external IP address over unencrypted HTTP without user consent. This constitutes a significant privacy violation and malicious behavior in the context of software supply chain security. The code is clear and not obfuscated but poses a high security risk due to unauthorized data transmission. Users should consider this package unsafe for use in production environments.