Secure your dependencies. Ship with confidence.

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 collects system and user information, including the directory name, hostname, username, and home directory, and sends this data to external servers at 'site[.]wheezy[.]io' and 'en7gkbdp3755omk[.]m[.]pipedream[.]net' without user consent. It also reads the contents of 'package.json' files and transmits them to these external servers. This unauthorized data exfiltration constitutes malicious behavior and poses a significant security risk.

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

The code is designed to exfiltrate sensitive system information to a remote server without user consent, indicating malicious intent.

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

The code exhibits clear signs of malicious behavior by sending sensitive system and project information to external servers. The actions performed by the code pose a significant risk to the security and privacy of the system and its users.

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

The code is suspicious as it collects and sends system information to an external server without user consent. Disabling TLS verification further increases the security risk.

The code demonstrates potentially malicious behavior by exfiltrating system data to an external server and disabling TLS verification, posing a significant security risk.

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

The package contains a hidden payload that targets Russian language users visiting Russian and Belarusian sites. For those users, it will disable user interaction and play a looping audio of the Ukrainian anthem after 3 days. Therefore, it is marked as protestware only because it freezes interactions for many users. This behavior is not disclosed in any documentation of the package and seriously disrupts user experience.

The script contains hardcoded credentials and exposes sensitive keys, which can lead to unauthorized access and potential misuse of the application. Make sure to use environment variables or a configuration file to securely store sensitive information.

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

The current package is a placeholder and does not pose any risk, but the original package was malicious. A more detailed report would be necessary to provide accurate scores.

This assembly contains a heavily obfuscated runtime loader that decrypts embedded payload(s) using a hardcoded AES key/IV, allocates and writes executable memory, uses low-level Win32 API calls (VirtualAlloc, WriteProcessMemory, VirtualProtect, OpenProcess), resolves function pointers via LoadLibrary/GetProcAddress, and prepares/invokes delegates at runtime. Those behaviors are consistent with an in-memory code loader/reflective loader or dropper — mechanisms often used by malware for stealthy code injection or unpacking and executing additional payloads. Although no explicit network exfiltration is present in this fragment, the loader provides the means to execute arbitrary native or managed code in-process, which is a severe supply-chain and runtime-execution risk. I recommend treating this package as malicious/untrusted and blocking its use until further provenance and intent are proven (for example, vendor-signed, source-matching, documented loader behavior).

The code is malicious as it covertly exfiltrates sensitive system and user information to an external IP address without user consent or transparency. This poses a serious privacy and security risk. The code is not obfuscated but clearly designed to steal data, and thus should be flagged as malware.

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

The provided code exhibits highly malicious behavior. It retrieves an encryption key from an external source, finds all files in specified directories, encrypts these files, and overwrites them. Additionally, it fetches data from another URL and writes it to a local file that appears to be a ransom note. This code poses a severe security risk and demonstrates typical behavior of ransomware.

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

The script is executing an unknown JavaScript file, which raises concerns about potential malicious behavior or security risks. The contents of 'pqluuny.js' should be reviewed to determine its safety.

The code has a potential security risk due to the direct installation of an npm package without verifying its integrity. An attacker could potentially modify the 'listban.json' or the 'fca-kaiyo' package to execute malicious code.

Live on npm for 38 days, 7 hours and 58 minutes before removal. Socket users were protected even while the package was live.

The script seems to be part of a spamming operation and uses bad security practices, such as hardcoding paths and credentials. Therefore, it's a potential security risk.

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

The code may be used for malicious purposes. It collects sensitive information (environment variables) and sends them to a potentially dangerous host. This could lead to sensitive data leakage.

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

The code exhibits clear signs of malicious intent, including potential data exfiltration and command injection vulnerabilities. The specific use of system information gathering commands combined with network communication to an external server without any form of user consent or security checks is highly suspicious and likely intended to harm or compromise the user's system.

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

The script runs 'index.js' and silences all output, which could be a method to hide malicious actions or errors. The safety of this script depends on the contents of 'index.js'.

This script is potentially malicious as it is sending sensitive system information (/etc/passwd) to a remote server. It should be treated with caution.

This file gathers extensive system and environment data (including environment variables, process details, and architecture) without user consent, then obfuscates the data via XOR/base64 encoding. It transmits the encoded information to 51.250.107[.]250 using an HTTP GET request with an Authorization header, indicating a likely attempt at data exfiltration.

The code functions as a dynamic loader that executes rpcl.py from the same directory. While this can be benign in controlled plugin architectures, it is highly risky from a security standpoint because it enables arbitrary, unvalidated code execution at runtime. This is a strong indicator of potential backdoor or payload delivery capability and should be treated with caution. Ensure rpcl.py is from a trusted source, validate its hash, or replace with explicit, vetted imports rather than dynamic exec-based loading.

The script appears to be gathering system information and sending it to an external server via DNS requests. This is a common tactic used by malware to exfiltrate data and establish command and control channels. It's highly likely that this code is malicious.

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 collects system and user information, including the directory name, hostname, username, and home directory, and sends this data to external servers at 'site[.]wheezy[.]io' and 'en7gkbdp3755omk[.]m[.]pipedream[.]net' without user consent. It also reads the contents of 'package.json' files and transmits them to these external servers. This unauthorized data exfiltration constitutes malicious behavior and poses a significant security risk.

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

The code is designed to exfiltrate sensitive system information to a remote server without user consent, indicating malicious intent.

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

The code exhibits clear signs of malicious behavior by sending sensitive system and project information to external servers. The actions performed by the code pose a significant risk to the security and privacy of the system and its users.

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

The code is suspicious as it collects and sends system information to an external server without user consent. Disabling TLS verification further increases the security risk.

The code demonstrates potentially malicious behavior by exfiltrating system data to an external server and disabling TLS verification, posing a significant security risk.

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

The package contains a hidden payload that targets Russian language users visiting Russian and Belarusian sites. For those users, it will disable user interaction and play a looping audio of the Ukrainian anthem after 3 days. Therefore, it is marked as protestware only because it freezes interactions for many users. This behavior is not disclosed in any documentation of the package and seriously disrupts user experience.

The script contains hardcoded credentials and exposes sensitive keys, which can lead to unauthorized access and potential misuse of the application. Make sure to use environment variables or a configuration file to securely store sensitive information.

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

The current package is a placeholder and does not pose any risk, but the original package was malicious. A more detailed report would be necessary to provide accurate scores.

This assembly contains a heavily obfuscated runtime loader that decrypts embedded payload(s) using a hardcoded AES key/IV, allocates and writes executable memory, uses low-level Win32 API calls (VirtualAlloc, WriteProcessMemory, VirtualProtect, OpenProcess), resolves function pointers via LoadLibrary/GetProcAddress, and prepares/invokes delegates at runtime. Those behaviors are consistent with an in-memory code loader/reflective loader or dropper — mechanisms often used by malware for stealthy code injection or unpacking and executing additional payloads. Although no explicit network exfiltration is present in this fragment, the loader provides the means to execute arbitrary native or managed code in-process, which is a severe supply-chain and runtime-execution risk. I recommend treating this package as malicious/untrusted and blocking its use until further provenance and intent are proven (for example, vendor-signed, source-matching, documented loader behavior).

The code is malicious as it covertly exfiltrates sensitive system and user information to an external IP address without user consent or transparency. This poses a serious privacy and security risk. The code is not obfuscated but clearly designed to steal data, and thus should be flagged as malware.

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

The provided code exhibits highly malicious behavior. It retrieves an encryption key from an external source, finds all files in specified directories, encrypts these files, and overwrites them. Additionally, it fetches data from another URL and writes it to a local file that appears to be a ransom note. This code poses a severe security risk and demonstrates typical behavior of ransomware.

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

The script is executing an unknown JavaScript file, which raises concerns about potential malicious behavior or security risks. The contents of 'pqluuny.js' should be reviewed to determine its safety.

The code has a potential security risk due to the direct installation of an npm package without verifying its integrity. An attacker could potentially modify the 'listban.json' or the 'fca-kaiyo' package to execute malicious code.

Live on npm for 38 days, 7 hours and 58 minutes before removal. Socket users were protected even while the package was live.

The script seems to be part of a spamming operation and uses bad security practices, such as hardcoding paths and credentials. Therefore, it's a potential security risk.

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

The code may be used for malicious purposes. It collects sensitive information (environment variables) and sends them to a potentially dangerous host. This could lead to sensitive data leakage.

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

The code exhibits clear signs of malicious intent, including potential data exfiltration and command injection vulnerabilities. The specific use of system information gathering commands combined with network communication to an external server without any form of user consent or security checks is highly suspicious and likely intended to harm or compromise the user's system.

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

The script runs 'index.js' and silences all output, which could be a method to hide malicious actions or errors. The safety of this script depends on the contents of 'index.js'.

This script is potentially malicious as it is sending sensitive system information (/etc/passwd) to a remote server. It should be treated with caution.

This file gathers extensive system and environment data (including environment variables, process details, and architecture) without user consent, then obfuscates the data via XOR/base64 encoding. It transmits the encoded information to 51.250.107[.]250 using an HTTP GET request with an Authorization header, indicating a likely attempt at data exfiltration.

The code functions as a dynamic loader that executes rpcl.py from the same directory. While this can be benign in controlled plugin architectures, it is highly risky from a security standpoint because it enables arbitrary, unvalidated code execution at runtime. This is a strong indicator of potential backdoor or payload delivery capability and should be treated with caution. Ensure rpcl.py is from a trusted source, validate its hash, or replace with explicit, vetted imports rather than dynamic exec-based loading.

The script appears to be gathering system information and sending it to an external server via DNS requests. This is a common tactic used by malware to exfiltrate data and establish command and control channels. It's highly likely that this code is malicious.