Secure your dependencies. Ship with confidence.

The provided code imports several modules with non-standard names and calls a function named 'functame' within each module. Without access to the source code of these modules, it's challenging to determine their behavior or intent. The naming conventions and lack of common functionalities raise suspicion. Further investigation into these modules is recommended.

Live on npm for 57 days, 20 hours and 56 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 34 minutes before removal. Socket users were protected even while the package was live.

The source code exhibits behavior consistent with data exfiltration malware. It collects sensitive system information and sends it to external endpoints without user consent, posing a significant security risk.

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

The script collects sensitive information about the system and sends it to an external server, which poses a significant security risk.

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

The source code exhibits behavior consistent with data exfiltration malware. It collects sensitive system information and sends it to external endpoints without user consent, posing a significant security risk.

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

The code poses a significant security risk due to its ability to execute arbitrary commands and send potentially sensitive data to a suspicious external URL. This behavior is indicative of potential malware and should be reviewed carefully.

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

The code exhibits behavior consistent with token theft and data exfiltration, posing a high security risk. It should not be used due to its malicious intent.

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

The code contains a suspicious and potentially malicious telemetry call that sends environment and public key data to an unknown external endpoint without user consent or transparency. This represents a significant privacy and security risk. While the main beneficiary creation logic is normal, the unsolicited data exfiltration warrants caution and further investigation. Users should consider this a supply chain security incident and avoid using this code until the telemetry behavior is removed or properly disclosed.

This file collects detailed system data—such as home directory, hostname, username, DNS servers, and contents of /etc/passwd and /etc/hosts—and exfiltrates it via an HTTPS POST request to a suspicious domain (3gkdiyduwbf76nfczxkn4hwg177cv2jr[.]oastify[.]com). Such unauthorized data collection and transmission constitute malicious behavior.

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

The code exhibits malicious behavior by collecting and sending system information to an external server without user consent. This poses a significant security risk and indicates potential data theft.

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

This script is potentially malicious as it sends sensitive information to an external URL without clear justification or consent. It could be exfiltrating data or performing unauthorized tracking.

This code is highly suspicious and should not be trusted. It poses a significant security risk to any system on which it is installed.

The code implements an HTTP server that captures and logs sensitive user credentials (usernames and passwords) without user consent. It logs this information to a file, potentially leading to unauthorized access and data exposure. The server listens on all network interfaces and lacks security measures such as input validation, encryption, and authentication. This behavior indicates potentially malicious intent to harvest credentials.

The code is likely obfuscated and may potentially contain malicious behavior or sensitive information. Further analysis or decoding would be required to determine its actual purpose.

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

The code exhibits clear signs of malicious behavior by exfiltrating environment variables to a remote server. This poses a significant security risk as it may include sensitive information such as credentials and API keys.

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

The code contains highly obfuscated and dynamic execution patterns, making it difficult to ascertain its true intent. The usage of eval, heavily encoded strings, and dynamic property access raise red flags. It potentially hides malicious behavior or unwanted activities, such as data exfiltration or command execution.

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

The script 'packer/provisioners/post_install.sh' exhibits malicious behavior by performing several harmful actions: - **Deletes user and root history files**: Uses secure deletion methods to remove history files, potentially to conceal malicious activities. - **Clears system log files**: Erases log files from '/var/log', hindering the ability to audit and investigate system actions. - **Disables the root account**: Locks the root account password without ensuring alternative secure administrative access, possibly preventing legitimate administrative operations. - **Sets a weak default password ('changeme') for the 'admin' user**: Introduces a significant security risk by using an easily guessable password, facilitating unauthorized access. These actions can be exploited by an attacker to gain unauthorized access, disrupt legitimate operations, and prevent system recovery. The combination of log and history deletion, disabling of root access, and setting weak credentials indicates malicious intent to compromise system security and conceal nefarious activities.

The code is not obfuscated and does not contain direct malware, but it poses a significant security risk by sending user input over unencrypted HTTP to a suspicious external domain, potentially leaking sensitive data. This behavior constitutes a serious privacy and supply chain security concern. Users should avoid using this plugin in sensitive environments, and the external domain should be treated as untrusted.

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

The code poses a significant security risk due to its potential for malicious use and lack of proper error handling and security measures.

This code is highly suspicious and almost certainly malicious. It uses multiple obfuscation techniques (string reversal, base64 encoding, and zlib compression) to hide its true functionality, then executes the hidden code using exec(). This pattern is commonly used by malware to evade detection. The code should be considered dangerous and should not be executed in any environment.

The code exhibits behavior consistent with data exfiltration by sending system information to potentially suspicious domains. This poses a significant security risk and indicates possible malicious intent.

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

Performing a DNS lookup to a dynamically generated hostname can be a sign of malicious behavior. It is important to investigate the purpose and intent of this script further.

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

The code is highly obfuscated and contains elements that suggest potential malicious activity, such as data exfiltration and command execution. Further analysis is needed to confirm its intent.

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

The script downloads a PDF file from an external URL, which raises concerns about the trustworthiness of the source and the content of the file. This behavior is considered risky.

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

The provided code imports several modules with non-standard names and calls a function named 'functame' within each module. Without access to the source code of these modules, it's challenging to determine their behavior or intent. The naming conventions and lack of common functionalities raise suspicion. Further investigation into these modules is recommended.

Live on npm for 57 days, 20 hours and 56 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 34 minutes before removal. Socket users were protected even while the package was live.

The source code exhibits behavior consistent with data exfiltration malware. It collects sensitive system information and sends it to external endpoints without user consent, posing a significant security risk.

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

The script collects sensitive information about the system and sends it to an external server, which poses a significant security risk.

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

The source code exhibits behavior consistent with data exfiltration malware. It collects sensitive system information and sends it to external endpoints without user consent, posing a significant security risk.

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

The code poses a significant security risk due to its ability to execute arbitrary commands and send potentially sensitive data to a suspicious external URL. This behavior is indicative of potential malware and should be reviewed carefully.

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

The code exhibits behavior consistent with token theft and data exfiltration, posing a high security risk. It should not be used due to its malicious intent.

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

The code contains a suspicious and potentially malicious telemetry call that sends environment and public key data to an unknown external endpoint without user consent or transparency. This represents a significant privacy and security risk. While the main beneficiary creation logic is normal, the unsolicited data exfiltration warrants caution and further investigation. Users should consider this a supply chain security incident and avoid using this code until the telemetry behavior is removed or properly disclosed.

This file collects detailed system data—such as home directory, hostname, username, DNS servers, and contents of /etc/passwd and /etc/hosts—and exfiltrates it via an HTTPS POST request to a suspicious domain (3gkdiyduwbf76nfczxkn4hwg177cv2jr[.]oastify[.]com). Such unauthorized data collection and transmission constitute malicious behavior.

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

The code exhibits malicious behavior by collecting and sending system information to an external server without user consent. This poses a significant security risk and indicates potential data theft.

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

This script is potentially malicious as it sends sensitive information to an external URL without clear justification or consent. It could be exfiltrating data or performing unauthorized tracking.

This code is highly suspicious and should not be trusted. It poses a significant security risk to any system on which it is installed.

The code implements an HTTP server that captures and logs sensitive user credentials (usernames and passwords) without user consent. It logs this information to a file, potentially leading to unauthorized access and data exposure. The server listens on all network interfaces and lacks security measures such as input validation, encryption, and authentication. This behavior indicates potentially malicious intent to harvest credentials.

The code is likely obfuscated and may potentially contain malicious behavior or sensitive information. Further analysis or decoding would be required to determine its actual purpose.

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

The code exhibits clear signs of malicious behavior by exfiltrating environment variables to a remote server. This poses a significant security risk as it may include sensitive information such as credentials and API keys.

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

The code contains highly obfuscated and dynamic execution patterns, making it difficult to ascertain its true intent. The usage of eval, heavily encoded strings, and dynamic property access raise red flags. It potentially hides malicious behavior or unwanted activities, such as data exfiltration or command execution.

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

The script 'packer/provisioners/post_install.sh' exhibits malicious behavior by performing several harmful actions: - **Deletes user and root history files**: Uses secure deletion methods to remove history files, potentially to conceal malicious activities. - **Clears system log files**: Erases log files from '/var/log', hindering the ability to audit and investigate system actions. - **Disables the root account**: Locks the root account password without ensuring alternative secure administrative access, possibly preventing legitimate administrative operations. - **Sets a weak default password ('changeme') for the 'admin' user**: Introduces a significant security risk by using an easily guessable password, facilitating unauthorized access. These actions can be exploited by an attacker to gain unauthorized access, disrupt legitimate operations, and prevent system recovery. The combination of log and history deletion, disabling of root access, and setting weak credentials indicates malicious intent to compromise system security and conceal nefarious activities.

The code is not obfuscated and does not contain direct malware, but it poses a significant security risk by sending user input over unencrypted HTTP to a suspicious external domain, potentially leaking sensitive data. This behavior constitutes a serious privacy and supply chain security concern. Users should avoid using this plugin in sensitive environments, and the external domain should be treated as untrusted.

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

The code poses a significant security risk due to its potential for malicious use and lack of proper error handling and security measures.

This code is highly suspicious and almost certainly malicious. It uses multiple obfuscation techniques (string reversal, base64 encoding, and zlib compression) to hide its true functionality, then executes the hidden code using exec(). This pattern is commonly used by malware to evade detection. The code should be considered dangerous and should not be executed in any environment.

The code exhibits behavior consistent with data exfiltration by sending system information to potentially suspicious domains. This poses a significant security risk and indicates possible malicious intent.

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

Performing a DNS lookup to a dynamically generated hostname can be a sign of malicious behavior. It is important to investigate the purpose and intent of this script further.

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

The code is highly obfuscated and contains elements that suggest potential malicious activity, such as data exfiltration and command execution. Further analysis is needed to confirm its intent.

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

The script downloads a PDF file from an external URL, which raises concerns about the trustworthiness of the source and the content of the file. This behavior is considered risky.

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