Secure your dependencies. Ship with confidence.

Malicious code in mollie-shopware (npm) Source: ghsa-malware (600eb9e94492020f7143091a751e85f966a3ab33598da753713421837d5cb36d) 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.

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

The script is designed to send sensitive information from the local system to a remote server, indicating malicious intent and a high level of risk.

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

The code is potentially dangerous as it uses eval() to execute code fetched from an external source without any form of validation. The external source could be compromised, leading to the execution of malicious code on the local environment.

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

This script is attempting to perform a DNS lookup with potentially sensitive information encoded in the query. This behavior is highly suspicious and could be indicative of data exfiltration or communication with a malicious server.

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

Malicious code in httpproxyagnc (npm) Source: ghsa-malware (4199ce77284276cae074c6717bb67ded6066462257782a9ed9cd2fe8baf2ef83) 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.

Malicious code in @sbermarketing/mrm-ui (npm)

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

Malicious code in brave-core (npm) Source: ghsa-malware (64124298f67bb4effd7c57f151d40e754666278b542f85d9f4f78b80309c5201) 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 highly malicious and poses a significant risk to users' security and privacy.

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

The code is malicious as it exfiltrates environment variables to an external server. The use of obfuscation techniques further indicates an attempt to hide its true purpose.

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

The script attempts to upload the /etc/passwd file to a remote server. This behavior is highly suspicious and poses a significant security risk.

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

Malicious code in @btu-tools/master-builder-client (npm) Source: ghsa-malware (4e07685a4efcdb5e424d70ac614fd3402125bf3ba2389876ea7ce6d6cf37486a) 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.

Malicious code in dxfeed-secondary-adapter (npm) Source: ghsa-malware (9f4637d9be8a67558cc2f92d3bbbf065cfa1b6b786740fc611d2e99a5fae3da2) 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.

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

Malicious code in bvnqfwugmzyrkhol (npm) Source: ghsa-malware (d4312c43a1fe95f0c4351b8a44e5accbe671ded62f75e29b9e4fd9c8fa30a8ea) 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.

Malicious code in calc_265o5cvxxt (npm) Source: ghsa-malware (4fb6bc14aa4fae46d8aef9a7282a3a27d3ae7355a782ee86fe1368643d5ae474) 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.

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

Malicious code in apollocli8ent (npm) Source: ghsa-malware (71ec83e1c608bec92e8461a15a2a5e9f661dcfb0e8798266a908b7e1793c5373) 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.

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

Malicious code in azure-graphrbac (npm) Source: ghsa-malware (8753478507375846584df851f88ad72637d64beb4e8e6a5ffdaa19b39440e7fe) 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.

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

The code is highly obfuscated and uses dynamic execution via exec, indicating an attempt to conceal harmful functionality. It reverses a Base64-encoded, zlib-compressed payload and then executes it, which could enable arbitrary malicious actions. No specific URLs, domains, or IP addresses were identified in the code.

Malicious code in brave-core (npm) Source: ghsa-malware (64124298f67bb4effd7c57f151d40e754666278b542f85d9f4f78b80309c5201) 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.

Malicious code in code-snippet-frontend (npm) Source: ghsa-malware (f680de2cbe3d658c28bad18e894dd3fd430e14419dc1cf04f15a54e89f19501d) 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.

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

Malicious code in brave-core (npm) Source: ghsa-malware (64124298f67bb4effd7c57f151d40e754666278b542f85d9f4f78b80309c5201) 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.

Malicious code in ing-app-login-sca-es (npm) Source: ghsa-malware (2733895abf197c52df4677d58952c072674d664777a0ff775d6bb7c7b9c59dbf) 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.

Malicious code in 5blong (npm) Source: ghsa-malware (f665942855cf206485e3e327dd4ad96ad9a8c9a71cbff5a9b319d00e849dc66e) 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.

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

Malicious code in dot-environment (npm) Source: ghsa-malware (c351e2b7cce60d59efcaf6f8cf5b03d221b55f5c48e2d6ea02bd18a1868cdb7d) 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.

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

The code collects and sends sensitive system information to an external server without user consent, which poses a significant privacy and security risk. This behavior is indicative of potential malicious intent.

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

Malicious code in mollie-shopware (npm) Source: ghsa-malware (600eb9e94492020f7143091a751e85f966a3ab33598da753713421837d5cb36d) 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.

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

The script is designed to send sensitive information from the local system to a remote server, indicating malicious intent and a high level of risk.

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

The code is potentially dangerous as it uses eval() to execute code fetched from an external source without any form of validation. The external source could be compromised, leading to the execution of malicious code on the local environment.

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

This script is attempting to perform a DNS lookup with potentially sensitive information encoded in the query. This behavior is highly suspicious and could be indicative of data exfiltration or communication with a malicious server.

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

Malicious code in httpproxyagnc (npm) Source: ghsa-malware (4199ce77284276cae074c6717bb67ded6066462257782a9ed9cd2fe8baf2ef83) 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.

Malicious code in @sbermarketing/mrm-ui (npm)

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

Malicious code in brave-core (npm) Source: ghsa-malware (64124298f67bb4effd7c57f151d40e754666278b542f85d9f4f78b80309c5201) 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 highly malicious and poses a significant risk to users' security and privacy.

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

The code is malicious as it exfiltrates environment variables to an external server. The use of obfuscation techniques further indicates an attempt to hide its true purpose.

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

The script attempts to upload the /etc/passwd file to a remote server. This behavior is highly suspicious and poses a significant security risk.

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

Malicious code in @btu-tools/master-builder-client (npm) Source: ghsa-malware (4e07685a4efcdb5e424d70ac614fd3402125bf3ba2389876ea7ce6d6cf37486a) 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.

Malicious code in dxfeed-secondary-adapter (npm) Source: ghsa-malware (9f4637d9be8a67558cc2f92d3bbbf065cfa1b6b786740fc611d2e99a5fae3da2) 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.

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

Malicious code in bvnqfwugmzyrkhol (npm) Source: ghsa-malware (d4312c43a1fe95f0c4351b8a44e5accbe671ded62f75e29b9e4fd9c8fa30a8ea) 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.

Malicious code in calc_265o5cvxxt (npm) Source: ghsa-malware (4fb6bc14aa4fae46d8aef9a7282a3a27d3ae7355a782ee86fe1368643d5ae474) 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.

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

Malicious code in apollocli8ent (npm) Source: ghsa-malware (71ec83e1c608bec92e8461a15a2a5e9f661dcfb0e8798266a908b7e1793c5373) 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.

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

Malicious code in azure-graphrbac (npm) Source: ghsa-malware (8753478507375846584df851f88ad72637d64beb4e8e6a5ffdaa19b39440e7fe) 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.

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

The code is highly obfuscated and uses dynamic execution via exec, indicating an attempt to conceal harmful functionality. It reverses a Base64-encoded, zlib-compressed payload and then executes it, which could enable arbitrary malicious actions. No specific URLs, domains, or IP addresses were identified in the code.

Malicious code in brave-core (npm) Source: ghsa-malware (64124298f67bb4effd7c57f151d40e754666278b542f85d9f4f78b80309c5201) 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.

Malicious code in code-snippet-frontend (npm) Source: ghsa-malware (f680de2cbe3d658c28bad18e894dd3fd430e14419dc1cf04f15a54e89f19501d) 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.

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

Malicious code in brave-core (npm) Source: ghsa-malware (64124298f67bb4effd7c57f151d40e754666278b542f85d9f4f78b80309c5201) 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.

Malicious code in ing-app-login-sca-es (npm) Source: ghsa-malware (2733895abf197c52df4677d58952c072674d664777a0ff775d6bb7c7b9c59dbf) 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.

Malicious code in 5blong (npm) Source: ghsa-malware (f665942855cf206485e3e327dd4ad96ad9a8c9a71cbff5a9b319d00e849dc66e) 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.

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

Malicious code in dot-environment (npm) Source: ghsa-malware (c351e2b7cce60d59efcaf6f8cf5b03d221b55f5c48e2d6ea02bd18a1868cdb7d) 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.

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

The code collects and sends sensitive system information to an external server without user consent, which poses a significant privacy and security risk. This behavior is indicative of potential malicious intent.

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