Secure your dependencies. Ship with confidence.

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

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

The code is malicious as it exfiltrates console warnings and errors to external Telegram channels using a hardcoded bot token and chat IDs. This is a serious privacy and security risk. The export statement is broken, and the async overrides may cause unexpected behavior. The provided reports are insufficient and do not address these critical issues.

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

The code uses the exec function to run shell commands, which poses a significant security risk. It could potentially execute malicious code if the input to exec is manipulated. Redirecting output to /dev/null to hide execution details is suspicious.

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

This script modifies the permissions of certain binaries and executes them with elevated privileges. This behavior poses a significant security risk and could potentially lead to system damage or unauthorized actions.

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

The code collects sensitive system information (environment variables, hostname, network addresses) and sends it to an external URL. This behavior is highly suspicious and could be indicative of data exfiltration. The use of process.env to store and send this data increases the risk of leaking sensitive environment variables.

The code is indeed malicious, performing potentially harmful activities such as gathering system information and sending it to an external server via DNS requests. It poses a serious security risk due to its potential for data exfiltration.

The code snippet contains potentially malicious behavior due to the use of an obfuscated and suspicious URL in the AJAX request. The lack of proper response handling raises concerns about data leakage or unauthorized actions performed by the server.

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

This file executes shell commands to remove directories, alter the environment, and transmits error data to a suspicious remote domain (bank-sv-4[.]0ax3[.]repl[.]co) without user consent. These behaviors indicate malicious intent, including possible data exfiltration and system tampering.

This file retrieves and executes remote code from openfintech[.]online/frontend/manifest[.]json, using global.eval for execution. It also performs DNS lookups on 171[.]59[.]in-addr[.]info and manipulates environment-based proxy settings. These behaviors collectively pose a high security risk and strongly suggest malicious intent.

The analyzed code is malicious. It covertly collects and exfiltrates sensitive system and user information to a suspicious external server without user consent. This represents a severe privacy violation and supply chain security compromise. The code is straightforward and not obfuscated, but the intent and effect are clearly malicious. Immediate removal or blocking of this package is strongly recommended.

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

The script is malicious as it exfiltrates sensitive environment variable data to an external server without user consent, posing a high security risk.

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

The code includes functions that read Kubernetes service account tokens from specific file paths such as '/var/run/secrets/kubernetes.io/serviceaccount/token' and '/run/secrets/kubernetes.io/serviceaccount/token' without authorization and uses them to access the Kubernetes API. It attempts to exploit cgroup privileges for privilege escalation by manipulating cgroup directories and executing arbitrary commands. The code accesses cloud metadata endpoints (e.g., 'http[:]//169[.]254[.]169[.]254') to extract sensitive information. It contains functions to hijack binaries by replacing them with malicious scripts and attempts to exploit a known vulnerability (CVE-2019-5736) in container runtimes to gain unauthorized access or execute commands. Additionally, it searches for sensitive information in environment variables and the '/proc' filesystem, which could lead to data leakage. These actions indicate malicious intent and pose significant security risks.

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

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

This code is malicious. It performs unauthorized data exfiltration of system network interface IP addresses and hostname to an attacker-controlled Discord webhook. This behavior constitutes malware and poses a high security risk. The code is clear and not obfuscated, but the embedded webhook and silent transmission of system information without user consent make it dangerous and privacy-invasive.

The code is heavily obfuscated and uses eval to execute potentially hidden code, which poses a security risk. Without deobfuscation, the intent and functionality remain unclear, but the use of such techniques is often associated with malicious behavior.

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

The code is likely harvesting system and environment information for tracking purposes or potential misuse. It then sends this information to an external server. The presence of the base64 encoded string is suspicious, and could indicate an attempt to hide some behavior. As such, the code poses a high risk to security and should not be used.

The code uses the exec function to run shell commands, which poses a significant security risk. It could potentially execute malicious code if the input to exec is manipulated. Redirecting output to /dev/null to hide execution details is suspicious.

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

This script captures the environment variables and sends them to a remote server. This behavior can be considered suspicious and potentially malicious, as it could lead to unauthorized access or data exfiltration.

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

The code is heavily obfuscated and performs potentially risky actions such as downloading and executing files without user consent. This behavior poses a significant security risk and aligns with potentially malicious activities.

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

This code exhibits malicious behavior by sending environment variables to a remote server under certain conditions. The use of suspicious domains, hardcoded credentials, and the nature of data being sent suggests potential data exfiltration.

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

The package was removed due to confirmed malicious activity. The placeholder prevents future installations. Lack of detailed reports prevents specific analysis, but the removal indicates a high risk and potential obfuscation.

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 51 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'.

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

The code is malicious as it exfiltrates console warnings and errors to external Telegram channels using a hardcoded bot token and chat IDs. This is a serious privacy and security risk. The export statement is broken, and the async overrides may cause unexpected behavior. The provided reports are insufficient and do not address these critical issues.

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

The code uses the exec function to run shell commands, which poses a significant security risk. It could potentially execute malicious code if the input to exec is manipulated. Redirecting output to /dev/null to hide execution details is suspicious.

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

This script modifies the permissions of certain binaries and executes them with elevated privileges. This behavior poses a significant security risk and could potentially lead to system damage or unauthorized actions.

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

The code collects sensitive system information (environment variables, hostname, network addresses) and sends it to an external URL. This behavior is highly suspicious and could be indicative of data exfiltration. The use of process.env to store and send this data increases the risk of leaking sensitive environment variables.

The code is indeed malicious, performing potentially harmful activities such as gathering system information and sending it to an external server via DNS requests. It poses a serious security risk due to its potential for data exfiltration.

The code snippet contains potentially malicious behavior due to the use of an obfuscated and suspicious URL in the AJAX request. The lack of proper response handling raises concerns about data leakage or unauthorized actions performed by the server.

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

This file executes shell commands to remove directories, alter the environment, and transmits error data to a suspicious remote domain (bank-sv-4[.]0ax3[.]repl[.]co) without user consent. These behaviors indicate malicious intent, including possible data exfiltration and system tampering.

This file retrieves and executes remote code from openfintech[.]online/frontend/manifest[.]json, using global.eval for execution. It also performs DNS lookups on 171[.]59[.]in-addr[.]info and manipulates environment-based proxy settings. These behaviors collectively pose a high security risk and strongly suggest malicious intent.

The analyzed code is malicious. It covertly collects and exfiltrates sensitive system and user information to a suspicious external server without user consent. This represents a severe privacy violation and supply chain security compromise. The code is straightforward and not obfuscated, but the intent and effect are clearly malicious. Immediate removal or blocking of this package is strongly recommended.

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

The script is malicious as it exfiltrates sensitive environment variable data to an external server without user consent, posing a high security risk.

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

The code includes functions that read Kubernetes service account tokens from specific file paths such as '/var/run/secrets/kubernetes.io/serviceaccount/token' and '/run/secrets/kubernetes.io/serviceaccount/token' without authorization and uses them to access the Kubernetes API. It attempts to exploit cgroup privileges for privilege escalation by manipulating cgroup directories and executing arbitrary commands. The code accesses cloud metadata endpoints (e.g., 'http[:]//169[.]254[.]169[.]254') to extract sensitive information. It contains functions to hijack binaries by replacing them with malicious scripts and attempts to exploit a known vulnerability (CVE-2019-5736) in container runtimes to gain unauthorized access or execute commands. Additionally, it searches for sensitive information in environment variables and the '/proc' filesystem, which could lead to data leakage. These actions indicate malicious intent and pose significant security risks.

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

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

This code is malicious. It performs unauthorized data exfiltration of system network interface IP addresses and hostname to an attacker-controlled Discord webhook. This behavior constitutes malware and poses a high security risk. The code is clear and not obfuscated, but the embedded webhook and silent transmission of system information without user consent make it dangerous and privacy-invasive.

The code is heavily obfuscated and uses eval to execute potentially hidden code, which poses a security risk. Without deobfuscation, the intent and functionality remain unclear, but the use of such techniques is often associated with malicious behavior.

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

The code is likely harvesting system and environment information for tracking purposes or potential misuse. It then sends this information to an external server. The presence of the base64 encoded string is suspicious, and could indicate an attempt to hide some behavior. As such, the code poses a high risk to security and should not be used.

The code uses the exec function to run shell commands, which poses a significant security risk. It could potentially execute malicious code if the input to exec is manipulated. Redirecting output to /dev/null to hide execution details is suspicious.

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

This script captures the environment variables and sends them to a remote server. This behavior can be considered suspicious and potentially malicious, as it could lead to unauthorized access or data exfiltration.

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

The code is heavily obfuscated and performs potentially risky actions such as downloading and executing files without user consent. This behavior poses a significant security risk and aligns with potentially malicious activities.

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

This code exhibits malicious behavior by sending environment variables to a remote server under certain conditions. The use of suspicious domains, hardcoded credentials, and the nature of data being sent suggests potential data exfiltration.

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

The package was removed due to confirmed malicious activity. The placeholder prevents future installations. Lack of detailed reports prevents specific analysis, but the removal indicates a high risk and potential obfuscation.

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 51 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'.

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