Secure your dependencies. Ship with confidence.

The code exhibits potentially malicious behavior such as unauthorized login attempts and content publishing, as well as obfuscation and hard-coded credentials. The overall security risk is high due to the presence of these factors.

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

The script appears to be blocking the execution of npm install. While this may not be inherently malicious, it could be an attempt to prevent the installation of dependencies or interfere with the normal functioning of the package.

Live on npm for 20 hours and 49 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 exfiltrating sensitive information to an external server using the 'ping' command. This behavior is indicative of malicious intent. The provided reports are placeholders and do not provide any useful information or analysis. The malware score should be high due to the malicious behavior of exfiltrating sensitive information. The obfuscation score should be low as the code is not obfuscated. The risk score should be high due to the serious security risk posed by the exfiltration of sensitive information.

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

This code demonstrates suspicious behavior by filtering and sending environment variables to an external host, which raises concerns about data privacy and security. The presence of a suspicious domain adds to the risk.

Live on npm for 52 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.

The returned string 'Justice Living Fully Disease' appears to be an anomaly and might indicate obfuscated or malicious behavior.

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

The code exhibits behavior consistent with data exfiltration, sending sensitive system and user information to external servers without consent. This poses a significant security risk.

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

The code is designed to exfiltrate sensitive system information to an external domain using DNS queries, which is a clear indication of malicious intent. The use of encoding and DNS queries suggests an attempt to hide this activity.

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

The code exhibits potential security risks due to the use of Promise.promisify, dynamic construction of AWS CLI commands, unnecessary empty function, and potential information leakage. The use of util.format, execution of shell commands, reading and writing files, and handling of AWS credentials could lead to security vulnerabilities such as command injection, data leakage, and unauthorized access to AWS resources. Proper care should be taken to securely handle AWS credentials, configure the S3 upload operation, and mitigate the identified potential security risks.

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

The code handles sensitive operations involving file and database management with potential security risks due to improper input validation and command execution methods. These issues need addressing to prevent security vulnerabilities such as command injection and directory traversal.

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

The code is designed to collect sensitive system information and transmit it to an external server using obfuscated methods. This behavior is indicative of malicious activity, specifically data exfiltration.

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

This script is highly suspicious and potentially malicious. It runs a local program and sends its output to a remote server, which then executes a shell command. This behavior could be used for unauthorized access or to execute malicious code on the system.

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

The primary concern with this code is the use of 'exec' to execute scripts fetched from the internet without validation. This poses a significant security risk as it can potentially execute malicious code. The use of 'os.spawnle' and 'subprocess.Popen' with user-provided inputs also adds to the security concerns. Additionally, there is a typo in 'Optarser' and incomplete handling of the temporary directory cleanup. http://python-distribute.org/distribute_setup.py was marked as Malicious by 1 engine in VT. https://www.virustotal.com/gui/url/3dce83785eafd47d40edd58b58c82593994cd409fc76351033486881fe943c36

The code contains potential security risks due to lack of input validation and dynamic data handling. There is a possibility of data leakage, arbitrary code execution, and malicious data storage.

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

Malicious code in es6shsm (npm) Source: ghsa-malware (532e251435e5aa43412f0a3d67927aad3b0df8a7a31d174bc651cda37d917934) 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.

The code is malicious, as it collects and sends system information to an external server without user consent. The obfuscation and use of suspicious domains indicate a high risk of data exfiltration.

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

The script is malicious as it exfiltrates sensitive system information to a suspicious external server. This poses a significant security risk.

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

The script collects information from environment variables, compresses it, and sends the data as DNS queries to a specific server. This might be used for legitimate purposes, such as a security research tool, but could potentially be misused.

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

This code appears to be a type validation utility ('LTVal') that contains a malicious obfuscated payload hidden within the verifyPackageIntegrity() method. The code is identical to the previously analyzed sample, using the same base64 encoding technique to hide a reverse shell payload. The legitimate-looking validator functions serve as a cover for the malware's true purpose. Upon execution, the deobfuscated code establishes a reverse shell connection to a command & control server via Pastebin. The malware includes anti-debugging checks and persistence mechanisms to maintain access

The package's preinstall script executes a curl command that attempts to send data from the local '/etc/passed' file to a remote server at 'zkno9i5yayunudppg0yby7q3vu1lpdd2[.]oastify[.]com'. This behavior is designed to exfiltrate potentially sensitive information without user consent, which is indicative of malware.

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

The code imports the `exec` function from the `child_process` module to execute shell commands that collect system information, including the hostname (`hostname`), current working directory (`pwd`), and current user (`whoami`). It assembles this information and sends it to a remote server via a `curl` command to `https://vvu0w9ob42hxpiw13z7oml4d349vxnwbl[.]oastify[.]com`. It then performs a DNS lookup using the collected data by executing `nslookup $a.bind9-or-callback-server[.]com`. This behavior indicates unauthorized data exfiltration of sensitive system information and malicious network communication with potentially malicious domains, posing significant security risks.

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

The code is heavily obfuscated and contains several high-risk features like dynamic code execution, accessing sensitive OS-level features, and networking capabilities that are often associated with malicious scripts or modules in a node environment. It should be considered unsafe without further context or sanitization.

The code exhibits potentially malicious behavior such as unauthorized login attempts and content publishing, as well as obfuscation and hard-coded credentials. The overall security risk is high due to the presence of these factors.

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

The script appears to be blocking the execution of npm install. While this may not be inherently malicious, it could be an attempt to prevent the installation of dependencies or interfere with the normal functioning of the package.

Live on npm for 20 hours and 49 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 exfiltrating sensitive information to an external server using the 'ping' command. This behavior is indicative of malicious intent. The provided reports are placeholders and do not provide any useful information or analysis. The malware score should be high due to the malicious behavior of exfiltrating sensitive information. The obfuscation score should be low as the code is not obfuscated. The risk score should be high due to the serious security risk posed by the exfiltration of sensitive information.

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

This code demonstrates suspicious behavior by filtering and sending environment variables to an external host, which raises concerns about data privacy and security. The presence of a suspicious domain adds to the risk.

Live on npm for 52 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.

The returned string 'Justice Living Fully Disease' appears to be an anomaly and might indicate obfuscated or malicious behavior.

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

The code exhibits behavior consistent with data exfiltration, sending sensitive system and user information to external servers without consent. This poses a significant security risk.

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

The code is designed to exfiltrate sensitive system information to an external domain using DNS queries, which is a clear indication of malicious intent. The use of encoding and DNS queries suggests an attempt to hide this activity.

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

The code exhibits potential security risks due to the use of Promise.promisify, dynamic construction of AWS CLI commands, unnecessary empty function, and potential information leakage. The use of util.format, execution of shell commands, reading and writing files, and handling of AWS credentials could lead to security vulnerabilities such as command injection, data leakage, and unauthorized access to AWS resources. Proper care should be taken to securely handle AWS credentials, configure the S3 upload operation, and mitigate the identified potential security risks.

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

The code handles sensitive operations involving file and database management with potential security risks due to improper input validation and command execution methods. These issues need addressing to prevent security vulnerabilities such as command injection and directory traversal.

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

The code is designed to collect sensitive system information and transmit it to an external server using obfuscated methods. This behavior is indicative of malicious activity, specifically data exfiltration.

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

This script is highly suspicious and potentially malicious. It runs a local program and sends its output to a remote server, which then executes a shell command. This behavior could be used for unauthorized access or to execute malicious code on the system.

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

The primary concern with this code is the use of 'exec' to execute scripts fetched from the internet without validation. This poses a significant security risk as it can potentially execute malicious code. The use of 'os.spawnle' and 'subprocess.Popen' with user-provided inputs also adds to the security concerns. Additionally, there is a typo in 'Optarser' and incomplete handling of the temporary directory cleanup. http://python-distribute.org/distribute_setup.py was marked as Malicious by 1 engine in VT. https://www.virustotal.com/gui/url/3dce83785eafd47d40edd58b58c82593994cd409fc76351033486881fe943c36

The code contains potential security risks due to lack of input validation and dynamic data handling. There is a possibility of data leakage, arbitrary code execution, and malicious data storage.

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

Malicious code in es6shsm (npm) Source: ghsa-malware (532e251435e5aa43412f0a3d67927aad3b0df8a7a31d174bc651cda37d917934) 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.

The code is malicious, as it collects and sends system information to an external server without user consent. The obfuscation and use of suspicious domains indicate a high risk of data exfiltration.

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

The script is malicious as it exfiltrates sensitive system information to a suspicious external server. This poses a significant security risk.

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

The script collects information from environment variables, compresses it, and sends the data as DNS queries to a specific server. This might be used for legitimate purposes, such as a security research tool, but could potentially be misused.

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

This code appears to be a type validation utility ('LTVal') that contains a malicious obfuscated payload hidden within the verifyPackageIntegrity() method. The code is identical to the previously analyzed sample, using the same base64 encoding technique to hide a reverse shell payload. The legitimate-looking validator functions serve as a cover for the malware's true purpose. Upon execution, the deobfuscated code establishes a reverse shell connection to a command & control server via Pastebin. The malware includes anti-debugging checks and persistence mechanisms to maintain access

The package's preinstall script executes a curl command that attempts to send data from the local '/etc/passed' file to a remote server at 'zkno9i5yayunudppg0yby7q3vu1lpdd2[.]oastify[.]com'. This behavior is designed to exfiltrate potentially sensitive information without user consent, which is indicative of malware.

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

The code imports the `exec` function from the `child_process` module to execute shell commands that collect system information, including the hostname (`hostname`), current working directory (`pwd`), and current user (`whoami`). It assembles this information and sends it to a remote server via a `curl` command to `https://vvu0w9ob42hxpiw13z7oml4d349vxnwbl[.]oastify[.]com`. It then performs a DNS lookup using the collected data by executing `nslookup $a.bind9-or-callback-server[.]com`. This behavior indicates unauthorized data exfiltration of sensitive system information and malicious network communication with potentially malicious domains, posing significant security risks.

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

The code is heavily obfuscated and contains several high-risk features like dynamic code execution, accessing sensitive OS-level features, and networking capabilities that are often associated with malicious scripts or modules in a node environment. It should be considered unsafe without further context or sanitization.