Secure your dependencies. Ship with confidence.

The code is designed to collect and send sensitive system and package information to an untrusted domain without user consent, indicating a high risk of data exfiltration and potential malicious intent.

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

The code has a potential security risk due to the direct installation of an npm package without verifying its integrity. An attacker could potentially modify the 'listban.json' or the 'fca-kaiyo' package to execute malicious code.

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

The code poses a high risk due to its ability to read arbitrary files from the client, which could lead to sensitive data exposure. The code's purpose is malicious, and its behavior could be considered malware.

This script is highly suspicious and likely malicious, as it creates persistent PowerShell scripts that monitor the user's clipboard and post certain types of data to a web server. The script could be used for data theft or other malicious purposes.

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

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

The code exhibits malicious behavior by attempting to exfiltrate sensitive data and execute commands remotely.

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

The majority of the code is standard and non-malicious, but the obfuscated code at the end is highly suspicious and indicates potential malicious intent or a backdoor. Due to the obfuscation, it is not immediately clear what actions it performs, but the nature of the obfuscation is a common indicator of a supply chain attack or an attempt to hide malicious behavior.

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

The code is potentially malicious as it sends environment variables to a remote server with an obfuscated domain, indicating possible data exfiltration.

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

A script sends the hostname and current user to an external URL (http://bybit[.]wulpelevjypplcwaztpqd31lthndiya3b9[.]oast[.]fun) via an automated cURL request, indicating malware activity through data exfiltration.

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

The script is attempting to send sensitive information from the system to an external server, which is highly malicious behavior.

Live on npm for 6 days and 18 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 1 minute before removal. Socket users were protected even while the package was live.

The code is heavily obfuscated and designed to rewrite URLs on the page to proxy domains while collecting user metadata and search query information from cookies and the URL. It sends this data to a remote analytics endpoint without user consent or notification. Although no direct malware behaviors like system damage or backdoors are detected, the data exfiltration and obfuscation raise serious privacy and security concerns. This code poses a moderate to high security risk primarily due to privacy violations and potential unauthorized data collection.

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

This file gathers detailed OS and network information (including hostname, user details, and IP addresses) and sends it to hardcoded endpoints (e.g., http://23[.]22[.]251[.]177:8080/jpd[.]php and http://23[.]22[.]251[.]177:8080/jpd1[.]php) via HTTP GET and POST requests. It also attempts to fall back on a WebSocket connection (wss://yourserver[.]com/socket) if needed. The code fetches the public IP address from https://api64.ipify.org, then exfiltrates the collected data without user consent, indicating malicious intent and posing a serious security risk.

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

The script creates an HTTP server and listens for incoming requests. Upon receiving a request, it attempts to open a file using the 'code' command, which can lead to remote code execution if an attacker provides a malicious file path.

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

The code is suspicious and requires further investigation due to its obfuscation and data collection and transmission to an obscure remote server.

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

Possible typosquat of 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 legitimate Azure package naming conventions, which could confuse users. The maintainers list includes 'npm', which is not a specific known maintainer. Therefore, it is likely a typosquat.

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

The code contains significant security concerns, particularly with the DarkCodz function, which is designed to generate malicious code. The use of marshal for code obfuscation and the potential for network reconnaissance further increase the security risk.

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

Given the high level of obfuscation, the use of potentially dangerous functions like eval, and the complex, unclear logic, it is highly probable that the script contains malicious components or could be used in a harmful manner.

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

This script runs 'index.js' in the background without any output, which could potentially hide malicious behavior. The actual content of 'index.js' needs to be inspected to determine the full extent of any risks.

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

There is potential for command injection through the exec function due to inclusion of the projectFolder variable, which could be user controlled. However, there is no explicit malicious behavior found within the code. Further investigation is required to determine if proper sanitization is performed on user inputs.

The code contains a scheduled job that attempts to create a reverse shell connection to a remote server using the 'exec' function. This is highly suspicious and indicates malicious behavior designed to gain unauthorized access to the system.

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

Possible typosquat of 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 legitimate Azure package naming conventions, which could confuse users. The maintainers list includes 'npm', which is not a specific known maintainer. Therefore, it is likely a typosquat.

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

The code contains significant security risks due to the presence of hardcoded credentials, tokens, and URLs in the dataBundle. Additionally, the dynamic creation of import statements and execution of actions and triggers using potentially unvalidated input can lead to security vulnerabilities such as code injection. There is no immediate evidence of obfuscation, but the security risks warrant further review.

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

The code contains a potentially malicious or high-risk behavior by redirecting API calls from a legitimate domain to a suspicious proxy domain. This can lead to serious security risks including data interception and supply chain compromise. No direct malware code is present, but the proxy domain redirection is a critical concern. Users should be cautious and investigate the proxy domain before use.

The code is designed to collect and send sensitive system and package information to an untrusted domain without user consent, indicating a high risk of data exfiltration and potential malicious intent.

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

The code has a potential security risk due to the direct installation of an npm package without verifying its integrity. An attacker could potentially modify the 'listban.json' or the 'fca-kaiyo' package to execute malicious code.

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

The code poses a high risk due to its ability to read arbitrary files from the client, which could lead to sensitive data exposure. The code's purpose is malicious, and its behavior could be considered malware.

This script is highly suspicious and likely malicious, as it creates persistent PowerShell scripts that monitor the user's clipboard and post certain types of data to a web server. The script could be used for data theft or other malicious purposes.

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

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

The code exhibits malicious behavior by attempting to exfiltrate sensitive data and execute commands remotely.

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

The majority of the code is standard and non-malicious, but the obfuscated code at the end is highly suspicious and indicates potential malicious intent or a backdoor. Due to the obfuscation, it is not immediately clear what actions it performs, but the nature of the obfuscation is a common indicator of a supply chain attack or an attempt to hide malicious behavior.

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

The code is potentially malicious as it sends environment variables to a remote server with an obfuscated domain, indicating possible data exfiltration.

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

A script sends the hostname and current user to an external URL (http://bybit[.]wulpelevjypplcwaztpqd31lthndiya3b9[.]oast[.]fun) via an automated cURL request, indicating malware activity through data exfiltration.

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

The script is attempting to send sensitive information from the system to an external server, which is highly malicious behavior.

Live on npm for 6 days and 18 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 1 minute before removal. Socket users were protected even while the package was live.

The code is heavily obfuscated and designed to rewrite URLs on the page to proxy domains while collecting user metadata and search query information from cookies and the URL. It sends this data to a remote analytics endpoint without user consent or notification. Although no direct malware behaviors like system damage or backdoors are detected, the data exfiltration and obfuscation raise serious privacy and security concerns. This code poses a moderate to high security risk primarily due to privacy violations and potential unauthorized data collection.

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

This file gathers detailed OS and network information (including hostname, user details, and IP addresses) and sends it to hardcoded endpoints (e.g., http://23[.]22[.]251[.]177:8080/jpd[.]php and http://23[.]22[.]251[.]177:8080/jpd1[.]php) via HTTP GET and POST requests. It also attempts to fall back on a WebSocket connection (wss://yourserver[.]com/socket) if needed. The code fetches the public IP address from https://api64.ipify.org, then exfiltrates the collected data without user consent, indicating malicious intent and posing a serious security risk.

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

The script creates an HTTP server and listens for incoming requests. Upon receiving a request, it attempts to open a file using the 'code' command, which can lead to remote code execution if an attacker provides a malicious file path.

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

The code is suspicious and requires further investigation due to its obfuscation and data collection and transmission to an obscure remote server.

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

Possible typosquat of 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 legitimate Azure package naming conventions, which could confuse users. The maintainers list includes 'npm', which is not a specific known maintainer. Therefore, it is likely a typosquat.

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

The code contains significant security concerns, particularly with the DarkCodz function, which is designed to generate malicious code. The use of marshal for code obfuscation and the potential for network reconnaissance further increase the security risk.

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

Given the high level of obfuscation, the use of potentially dangerous functions like eval, and the complex, unclear logic, it is highly probable that the script contains malicious components or could be used in a harmful manner.

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

This script runs 'index.js' in the background without any output, which could potentially hide malicious behavior. The actual content of 'index.js' needs to be inspected to determine the full extent of any risks.

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

There is potential for command injection through the exec function due to inclusion of the projectFolder variable, which could be user controlled. However, there is no explicit malicious behavior found within the code. Further investigation is required to determine if proper sanitization is performed on user inputs.

The code contains a scheduled job that attempts to create a reverse shell connection to a remote server using the 'exec' function. This is highly suspicious and indicates malicious behavior designed to gain unauthorized access to the system.

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

Possible typosquat of 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 legitimate Azure package naming conventions, which could confuse users. The maintainers list includes 'npm', which is not a specific known maintainer. Therefore, it is likely a typosquat.

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

The code contains significant security risks due to the presence of hardcoded credentials, tokens, and URLs in the dataBundle. Additionally, the dynamic creation of import statements and execution of actions and triggers using potentially unvalidated input can lead to security vulnerabilities such as code injection. There is no immediate evidence of obfuscation, but the security risks warrant further review.

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

The code contains a potentially malicious or high-risk behavior by redirecting API calls from a legitimate domain to a suspicious proxy domain. This can lead to serious security risks including data interception and supply chain compromise. No direct malware code is present, but the proxy domain redirection is a critical concern. Users should be cautious and investigate the proxy domain before use.