Secure your dependencies. Ship with confidence.

The code contains sensitive hardcoded credentials, posing a significant security risk if the information is valid. There is no evidence of malware or intentional obfuscation.

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

The code exhibits clear signs of malicious behavior by exfiltrating system information and file contents to external servers. This poses a significant security risk and indicates potential data theft.

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

The code exhibits behavior consistent with a supply chain attack, collecting and exfiltrating sensitive user and system information to a remote server without consent. The incorrect hostname format and the presence of 'pipedream' suggest potential ineptitude or an attempt to conceal the code's true intent. The code's functionality is not aligned with legitimate package operations and poses a significant security risk.

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

The script is not inherently malicious but poses a high security risk due to its ability to alter disk partitions without user interaction. This can lead to data loss or system damage if executed unintentionally.

The code is designed to collect and send sensitive information to a remote server without the user's knowledge or consent. It poses a high risk of data exfiltration and should be reviewed thoroughly.

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

This file contains obfuscated malicious code designed to exfiltrate environment variables to an external server. When executed, the code checks environment variables against predefined filters (including npm_config_registry and USERNAME), and if conditions are met, sends the complete environment data to daasadmin.m.pipedream[.]net via HTTP POST. The data is JSON-serialized and Base64-encoded before transmission. The code is deliberately obfuscated using ASCII decimal encoding to hide its true purpose, which is to steal potentially sensitive information from the user's environment.

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

The code imports the 'https' and 'child_process' modules, collects environment variables using 'process.env', retrieves the hostname via 'require('os').hostname()', and executes the 'whoami' command to obtain the current user's username. It compiles all this information into a JSON object and sends it via an HTTPS POST request to 'r1tdo58ec4p1por9zr4me8kbx23trmfb[.]oastify[.]com'. This behavior exfiltrates sensitive system information (environment variables, user identity, hostname) to an external server without user consent, posing a significant security risk and indicating malicious intent.

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

The code poses a security risk due to downloading and executing a file from an external source without verification. Disabling SSL verification further increases the risk of man-in-the-middle attacks. The potential for executing malicious code warrants a high security risk score.

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

Malicious code in @zitterorg/laudantium-rerum (npm) Source: ghsa-malware (e45ff91dd83cc149d7abc8c6fb2c74e3509aa341e23c72cfac0a34868a4e2637) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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

This code uses multiple obfuscation techniques to hide and execute arbitrary code. The pattern of reversing, base64 encoding, and compressing code before execution is a classic malware technique. Without safely analyzing the decompressed payload, we must consider this highly suspicious and potentially malicious. This pattern is not used for legitimate purposes in open-source packages.

Malicious code in ect-mnotion (npm) Source: ghsa-malware (6cfd30a37e499cbbd889bb3fac228dcf2544a493cb6e55a4b38aeee1ae93916f) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This script has the potential to exfiltrate sensitive information by reading the /etc/hosts file and sending it to a remote server. This behavior is highly suspicious and poses a significant security risk.

The code exhibits behaviors that could be considered malicious, particularly in terms of user privacy and data collection. It lacks explicit user consent mechanisms for the data being collected and sent to external servers. The reports provided were not informative, returning only '[object Promise]', which does not allow for a proper assessment of the security implications of the code.

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 10 days, 5 hours and 53 minutes before removal. Socket users were protected even while the package was live.

Malicious code in batch_rails2 (RubyGems)

The code is part of a tool that provides extensive system-level access and manipulation capabilities. While it is not inherently malicious, its functionalities can be used for both legitimate and malicious purposes, depending on the context and user intent.

This code poses a serious security risk and should not be used.

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

The code is designed to exfiltrate system information by sending it to an external domain via DNS queries. This is a clear indication of malicious behavior, as it involves unauthorized data transmission without user consent.

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

The code is intended for legitimate cryptographic purposes, but it contains several security risks related to the use of `eval()`, unsanitized DOM manipulation, and extensive global variables. The risk of malicious activity is not evident from the code snippet provided, but the potential for exploitation of security vulnerabilities is significant. Refactoring to remove the use of `eval()`, properly sanitizing all inputs, and restructuring the code to avoid global namespace pollution are recommended to improve security.

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

This package was removed from the npm registry for security reasons.

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

The code contains an obfuscated function that constructs and executes a shell command. The command is built through array concatenation to hide its true purpose and is executed using '/bin/sh -c'. The malicious command is triggered automatically through global variable initialization (var YQxcHwq = FkzcSBMf()). This pattern indicates a backdoor or remote command execution capability disguised within legitimate graph processing functionality and poses a critical security risk.

This file collects system information (e.g., hostname, platform, architecture, home directory, current working directory) and sends it to webhook[.]site via an HTTPS POST request without any user interaction or consent, constituting unauthorized data exfiltration with malicious intent.

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

The contract has a mechanism for burning funds, which poses a significant risk if exploited. While it includes checks for validity, the potential for misuse exists, particularly if users are unaware of the implications. Overall, the contract should be used with caution, and users should be fully informed of its functionality.

The code is a clear example of a reverse shell, which poses a significant security risk by allowing unauthorized remote access and command execution on the system. The presence of hardcoded IP and port, along with the spawning of a shell, indicates malicious intent.

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

The code contains sensitive hardcoded credentials, posing a significant security risk if the information is valid. There is no evidence of malware or intentional obfuscation.

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

The code exhibits clear signs of malicious behavior by exfiltrating system information and file contents to external servers. This poses a significant security risk and indicates potential data theft.

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

The code exhibits behavior consistent with a supply chain attack, collecting and exfiltrating sensitive user and system information to a remote server without consent. The incorrect hostname format and the presence of 'pipedream' suggest potential ineptitude or an attempt to conceal the code's true intent. The code's functionality is not aligned with legitimate package operations and poses a significant security risk.

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

The script is not inherently malicious but poses a high security risk due to its ability to alter disk partitions without user interaction. This can lead to data loss or system damage if executed unintentionally.

The code is designed to collect and send sensitive information to a remote server without the user's knowledge or consent. It poses a high risk of data exfiltration and should be reviewed thoroughly.

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

This file contains obfuscated malicious code designed to exfiltrate environment variables to an external server. When executed, the code checks environment variables against predefined filters (including npm_config_registry and USERNAME), and if conditions are met, sends the complete environment data to daasadmin.m.pipedream[.]net via HTTP POST. The data is JSON-serialized and Base64-encoded before transmission. The code is deliberately obfuscated using ASCII decimal encoding to hide its true purpose, which is to steal potentially sensitive information from the user's environment.

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

The code imports the 'https' and 'child_process' modules, collects environment variables using 'process.env', retrieves the hostname via 'require('os').hostname()', and executes the 'whoami' command to obtain the current user's username. It compiles all this information into a JSON object and sends it via an HTTPS POST request to 'r1tdo58ec4p1por9zr4me8kbx23trmfb[.]oastify[.]com'. This behavior exfiltrates sensitive system information (environment variables, user identity, hostname) to an external server without user consent, posing a significant security risk and indicating malicious intent.

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

The code poses a security risk due to downloading and executing a file from an external source without verification. Disabling SSL verification further increases the risk of man-in-the-middle attacks. The potential for executing malicious code warrants a high security risk score.

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

Malicious code in @zitterorg/laudantium-rerum (npm) Source: ghsa-malware (e45ff91dd83cc149d7abc8c6fb2c74e3509aa341e23c72cfac0a34868a4e2637) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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

This code uses multiple obfuscation techniques to hide and execute arbitrary code. The pattern of reversing, base64 encoding, and compressing code before execution is a classic malware technique. Without safely analyzing the decompressed payload, we must consider this highly suspicious and potentially malicious. This pattern is not used for legitimate purposes in open-source packages.

Malicious code in ect-mnotion (npm) Source: ghsa-malware (6cfd30a37e499cbbd889bb3fac228dcf2544a493cb6e55a4b38aeee1ae93916f) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This script has the potential to exfiltrate sensitive information by reading the /etc/hosts file and sending it to a remote server. This behavior is highly suspicious and poses a significant security risk.

The code exhibits behaviors that could be considered malicious, particularly in terms of user privacy and data collection. It lacks explicit user consent mechanisms for the data being collected and sent to external servers. The reports provided were not informative, returning only '[object Promise]', which does not allow for a proper assessment of the security implications of the code.

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 10 days, 5 hours and 53 minutes before removal. Socket users were protected even while the package was live.

Malicious code in batch_rails2 (RubyGems)

The code is part of a tool that provides extensive system-level access and manipulation capabilities. While it is not inherently malicious, its functionalities can be used for both legitimate and malicious purposes, depending on the context and user intent.

This code poses a serious security risk and should not be used.

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

The code is designed to exfiltrate system information by sending it to an external domain via DNS queries. This is a clear indication of malicious behavior, as it involves unauthorized data transmission without user consent.

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

The code is intended for legitimate cryptographic purposes, but it contains several security risks related to the use of `eval()`, unsanitized DOM manipulation, and extensive global variables. The risk of malicious activity is not evident from the code snippet provided, but the potential for exploitation of security vulnerabilities is significant. Refactoring to remove the use of `eval()`, properly sanitizing all inputs, and restructuring the code to avoid global namespace pollution are recommended to improve security.

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

This package was removed from the npm registry for security reasons.

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

The code contains an obfuscated function that constructs and executes a shell command. The command is built through array concatenation to hide its true purpose and is executed using '/bin/sh -c'. The malicious command is triggered automatically through global variable initialization (var YQxcHwq = FkzcSBMf()). This pattern indicates a backdoor or remote command execution capability disguised within legitimate graph processing functionality and poses a critical security risk.

This file collects system information (e.g., hostname, platform, architecture, home directory, current working directory) and sends it to webhook[.]site via an HTTPS POST request without any user interaction or consent, constituting unauthorized data exfiltration with malicious intent.

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

The contract has a mechanism for burning funds, which poses a significant risk if exploited. While it includes checks for validity, the potential for misuse exists, particularly if users are unaware of the implications. Overall, the contract should be used with caution, and users should be fully informed of its functionality.

The code is a clear example of a reverse shell, which poses a significant security risk by allowing unauthorized remote access and command execution on the system. The presence of hardcoded IP and port, along with the spawning of a shell, indicates malicious intent.

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