Secure your dependencies. Ship with confidence.

This is not readable source code but appears to be binary or obfuscated data. The file cannot be analyzed in its current form and requires specialized tools for decompilation or decryption. The presence of binary/obfuscated content where source code is expected is highly suspicious and could indicate malicious intent to hide functionality. Do not use this dependency without proper analysis using specialized tools.

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

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

The code engages in potentially malicious behavior by collecting sensitive system information and sending it to a remote server without clear user consent. The hard-coded domain, data obfuscation, and lack of transparency raise significant privacy and security concerns. The risk score is high due to the invasive nature of the code.

Live on npm for 22 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 an external server without user consent. This poses a high security risk and potential for data theft.

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

The code exhibits clear malicious behavior by collecting and transmitting sensitive system information to external servers without consent. The presence of an infinite loop and the sending of the 'package.json' file further indicate potential data exfiltration. This code poses a significant 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.

This script spawns a shell using child_process.exec to run 'whoami' and then posts the retrieved username to t60ykpeg1d97vt3fn6v2o01dd4jv7yvn[.]oastify[.]com, indicating clear malicious intent through data exfiltration.

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

The code defines a custom installation process that conditionally decrypts an encrypted payload using a hardcoded Fernet key on Windows systems. The decrypted content is then executed using exec(), allowing the potential execution of arbitrary code at install time. This dynamic decryption and execution mechanism is commonly used to conceal malicious functionality, such as unauthorized network communication (for example, contacting domains like example[.]com) or data exfiltration. The obfuscated nature of the payload and the conditional import of network libraries raise significant concerns regarding its intent.

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

The code is malicious. It collects sensitive system information (hostname, current user, current working directory, and directory listing) without consent, encodes this information in base64 to obfuscate it, and sends it to an external server. This behavior is characteristic of a malware payload designed for data exfiltration.

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

This code is a malicious payload that collects system data and sends it to a remote server. It also deletes itself after execution.

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

The code is designed to exfiltrate sensitive system and package information to a suspicious domain without user consent, indicating malicious intent. The lack of obfuscation suggests the code is straightforward, but the behavior is clearly malicious.

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

The analyzed code is highly obfuscated and uses dynamic eval to execute concealed code. It collects and processes data, writes files, and sends detailed data chunks and metadata to remote servers. These behaviors strongly indicate malicious intent, specifically data exfiltration. The provided reports are invalid and uninformative. This package poses a high security risk and should be considered malicious.

This code is malicious. It collects sensitive system and environment information and exfiltrates it to a suspicious external domain without user consent. The behavior constitutes a privacy breach and data theft, representing a high security risk. The code is not obfuscated but uses silent error handling to evade detection. It should be considered malware and the package should be removed from any repositories.

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

This code is highly suspicious and likely malicious. It attempts to stealthily exfiltrate user data from incoming requests to an untrusted external IP address without consent or transparency. The malformed fetch options and silent error handling suggest an attempt to evade detection or cause the request to fail silently. This represents a serious security risk and data privacy violation. The code should be considered malicious and untrustworthy.

The provided code imports several modules with unusual names and calls a function from each of them without any clear purpose or data processing. The unconventional naming and lack of apparent functionality raise concerns. However, without additional context or the actual implementation of the imported modules, it is challenging to definitively identify malicious behavior.

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

This is clear malware designed for data theft. The code systematically exfiltrates sensitive system information including directory paths, hostname, username, and home directory to an external attacker-controlled domain. Despite deceptive comments claiming legitimacy, this represents a serious security threat and should be treated as malicious software.

The code is malicious. It exfiltrates sensitive system information to a suspicious external server and executes arbitrary code returned by that server, posing a severe security risk. The obfuscation and silent error handling are additional red flags. This package should be considered compromised and unsafe for use.

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

The code appears to be sending system data over the network without any security checks. The hardcoded URL and lack of input validation raise security concerns.

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

The code is indicative of data exfiltration, sending sensitive system information to an external server without user consent. This poses a significant security risk and aligns with malicious behavior.

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

The code appears to be a self-update script with several red flags that indicate possible malicious intent or at least very unprofessional behavior. The hardcoded URLs, inappropriate contact link, and use of 'execSync' for updating packages without sufficient validation present significant security risks. The intentions of the author are not clear, and the script should not be trusted without further investigation.

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

This code contains a dedicated backdoor functionality through the setUserBackdoor method which allows unauthorized impersonation of any user account by bypassing standard authentication mechanisms. When called, this function sends the specified username to an endpoint '/user/backdoor' with authorization tokens, allowing the attacker to take over any user account. The code also employs sophisticated request interception techniques by overriding XMLHttpRequest.prototype and the fetch API to add potentially malicious headers. This is complemented by extensive URL manipulation capabilities and token management functions that facilitate unauthorized access. The backdoor implementation is not accidental - it's a carefully crafted mechanism designed specifically for account takeover.

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

The code contains potential security vulnerabilities due to the use of the 'stringify' method in the 'JSON' object, which may not handle certain Unicode characters properly, leading to security risks.

Live on npm for 3 days, 21 hours and 12 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 16 hours and 1 minute before removal. Socket users were protected even while the package was live.

The code exhibits several indicators of malicious intent, including stealthy data exfiltration of environment variables and sensitive system files, the construction of suspicious URLs, and an attempt to mask its activity as part of a security test. It is likely part of a dependency confusion attack.

This is not readable source code but appears to be binary or obfuscated data. The file cannot be analyzed in its current form and requires specialized tools for decompilation or decryption. The presence of binary/obfuscated content where source code is expected is highly suspicious and could indicate malicious intent to hide functionality. Do not use this dependency without proper analysis using specialized tools.

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

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

The code engages in potentially malicious behavior by collecting sensitive system information and sending it to a remote server without clear user consent. The hard-coded domain, data obfuscation, and lack of transparency raise significant privacy and security concerns. The risk score is high due to the invasive nature of the code.

Live on npm for 22 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 an external server without user consent. This poses a high security risk and potential for data theft.

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

The code exhibits clear malicious behavior by collecting and transmitting sensitive system information to external servers without consent. The presence of an infinite loop and the sending of the 'package.json' file further indicate potential data exfiltration. This code poses a significant 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.

This script spawns a shell using child_process.exec to run 'whoami' and then posts the retrieved username to t60ykpeg1d97vt3fn6v2o01dd4jv7yvn[.]oastify[.]com, indicating clear malicious intent through data exfiltration.

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

The code defines a custom installation process that conditionally decrypts an encrypted payload using a hardcoded Fernet key on Windows systems. The decrypted content is then executed using exec(), allowing the potential execution of arbitrary code at install time. This dynamic decryption and execution mechanism is commonly used to conceal malicious functionality, such as unauthorized network communication (for example, contacting domains like example[.]com) or data exfiltration. The obfuscated nature of the payload and the conditional import of network libraries raise significant concerns regarding its intent.

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

The code is malicious. It collects sensitive system information (hostname, current user, current working directory, and directory listing) without consent, encodes this information in base64 to obfuscate it, and sends it to an external server. This behavior is characteristic of a malware payload designed for data exfiltration.

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

This code is a malicious payload that collects system data and sends it to a remote server. It also deletes itself after execution.

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

The code is designed to exfiltrate sensitive system and package information to a suspicious domain without user consent, indicating malicious intent. The lack of obfuscation suggests the code is straightforward, but the behavior is clearly malicious.

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

The analyzed code is highly obfuscated and uses dynamic eval to execute concealed code. It collects and processes data, writes files, and sends detailed data chunks and metadata to remote servers. These behaviors strongly indicate malicious intent, specifically data exfiltration. The provided reports are invalid and uninformative. This package poses a high security risk and should be considered malicious.

This code is malicious. It collects sensitive system and environment information and exfiltrates it to a suspicious external domain without user consent. The behavior constitutes a privacy breach and data theft, representing a high security risk. The code is not obfuscated but uses silent error handling to evade detection. It should be considered malware and the package should be removed from any repositories.

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

This code is highly suspicious and likely malicious. It attempts to stealthily exfiltrate user data from incoming requests to an untrusted external IP address without consent or transparency. The malformed fetch options and silent error handling suggest an attempt to evade detection or cause the request to fail silently. This represents a serious security risk and data privacy violation. The code should be considered malicious and untrustworthy.

The provided code imports several modules with unusual names and calls a function from each of them without any clear purpose or data processing. The unconventional naming and lack of apparent functionality raise concerns. However, without additional context or the actual implementation of the imported modules, it is challenging to definitively identify malicious behavior.

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

This is clear malware designed for data theft. The code systematically exfiltrates sensitive system information including directory paths, hostname, username, and home directory to an external attacker-controlled domain. Despite deceptive comments claiming legitimacy, this represents a serious security threat and should be treated as malicious software.

The code is malicious. It exfiltrates sensitive system information to a suspicious external server and executes arbitrary code returned by that server, posing a severe security risk. The obfuscation and silent error handling are additional red flags. This package should be considered compromised and unsafe for use.

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

The code appears to be sending system data over the network without any security checks. The hardcoded URL and lack of input validation raise security concerns.

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

The code is indicative of data exfiltration, sending sensitive system information to an external server without user consent. This poses a significant security risk and aligns with malicious behavior.

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

The code appears to be a self-update script with several red flags that indicate possible malicious intent or at least very unprofessional behavior. The hardcoded URLs, inappropriate contact link, and use of 'execSync' for updating packages without sufficient validation present significant security risks. The intentions of the author are not clear, and the script should not be trusted without further investigation.

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

This code contains a dedicated backdoor functionality through the setUserBackdoor method which allows unauthorized impersonation of any user account by bypassing standard authentication mechanisms. When called, this function sends the specified username to an endpoint '/user/backdoor' with authorization tokens, allowing the attacker to take over any user account. The code also employs sophisticated request interception techniques by overriding XMLHttpRequest.prototype and the fetch API to add potentially malicious headers. This is complemented by extensive URL manipulation capabilities and token management functions that facilitate unauthorized access. The backdoor implementation is not accidental - it's a carefully crafted mechanism designed specifically for account takeover.

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

The code contains potential security vulnerabilities due to the use of the 'stringify' method in the 'JSON' object, which may not handle certain Unicode characters properly, leading to security risks.

Live on npm for 3 days, 21 hours and 12 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 16 hours and 1 minute before removal. Socket users were protected even while the package was live.

The code exhibits several indicators of malicious intent, including stealthy data exfiltration of environment variables and sensitive system files, the construction of suspicious URLs, and an attempt to mask its activity as part of a security test. It is likely part of a dependency confusion attack.