Highcharts Core versions 10.3.2 through 11.4.8, 12.0.0 through 12.6.1, and 13.0.0 through 13.1.0 contain a vulnerability where the `xlink:href` attribute in SVG anchors can include `javascript:` URLs that bypass text filtering. This allows malicious script execution when exported charts or their serialized markup are parsed and the link is activated by a user. The issue is fixed in versions 11.4.9, 12.6.2, and 13.1.1.
mcp-sanitizer version 1.3.3 contains a Server-Side Request Forgery (SSRF) vulnerability that allows bypassing localhost and IPv6 loopback address restrictions when URLs include explicit ports or use bracketed IPv6 notation. This flaw enables attacker-controlled URLs to reach internal services, potentially exposing sensitive data. The issue arises from improper hostname checks that fail to block localhost URLs with ports and bracketed IPv6 addresses. A fix is available in version 1.4.0.
mcp-sanitizer version 1.3.3 contains a file path validation vulnerability that permits absolute paths under user home directories such as /home/ and /Users/. This allows an attacker to access sensitive files like SSH private keys and AWS credentials by bypassing the sanitizer's checks. The sanitizer incorrectly treats these paths as safe, leading to potential unauthorized file reads when the sanitized path is used by the application. A patch is available in version 1.4.0 that removes these directories from the allowed absolute path whitelist and adds checks for sensitive home directory fragments.
The npm package itsa-utils version 1.4.2 contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, trusted computer. Removal of the package alone may not fully eliminate the malicious presence, as the attacker may have established persistent control over the system.
The npm package 'itsa-react-checkbox' version 16.0.5 contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected machine should be rotated immediately from a different, uncompromised device. Removal of the package alone may not eliminate all malicious software introduced by it.
The npm package 'mock-transactions-sdk' contains malicious code that fully compromises any computer on which it is installed or running. The compromise includes potential unauthorized access to all secrets and keys stored on the affected system. Immediate removal of the package is advised, but due to the extent of the compromise, complete remediation may require rotating all secrets and keys from a separate, uncompromised machine.
The npm package 'transaction-info-generate-sdk' contains malicious code that fully compromises any computer on which it is installed or running. The compromise includes potential unauthorized access to all secrets and keys stored on the affected machine. Removal of the package alone does not guarantee elimination of the malicious software, as full control may have been granted to an external attacker.
The npm package 'black-spindle' version 999.0.0 has been identified as malicious by the OpenSSF Package Analysis project. It exhibits malicious behavior by communicating with a domain linked to malicious activity and executing commands associated with harmful actions. This package poses a security risk to users who install or use it.
The npm package @zmtcdn/components version 9999.0.0 is a malicious dependency-confusion package. Its postinstall script collects system information including hostname, username, platform, working directory, and environment variable names, then sends this data to an external logging service. This reconnaissance can expose sensitive environment variables such as CI or secret tokens, potentially leading to credential theft. The package was published by the npm account kill_shs, which also published a similar malicious package @zmtcdn/ui.
The npm packages @zmtcdn/ui versions 9999.0.0 and 9999.0.7 are malicious dependency-confusion packages that execute a postinstall script sending system environment details to an external server without user consent. The postinstall script collects hostname, username, platform, working directory, environment variable names, and a timestamp, then sends this data to https://www.hinny.shop/api. These packages were published by a suspicious npm account and have no legitimate functional purpose for this data transmission.
The npm package identity-two-factor@999.0.0 is a malicious dependency-confusion package targeting Coinbase. It contains no functional code but executes a postinstall script that collects system metadata and exfiltrates it to a third-party webhook URL. This unsolicited data exfiltration occurs automatically upon installation without user authorization.
The npm package spectral-net-probe contains malicious code in versions 1.0.1, 1.0.4, and 1.0.10. These versions execute code during installation or loading that contacts remote servers to exfiltrate local files specified by the attacker. This behavior constitutes a supply-chain attack leveraging npm package distribution to steal arbitrary files from users' systems.
The glyphmatrix-fixture npm package versions 1.0.0 and 1.0.1 contain malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected machine should be rotated immediately from a different, secure computer. Removal of the package alone may not eliminate the malicious software, as the attacker may have gained full control of the system.
The npm package 'csec-form-validatorr' contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected machine should be rotated immediately from a different, trusted computer. Removal of the package alone does not guarantee elimination of all malicious software introduced by it.
The ccsseecc-form-validator npm package contains malicious code that compromises any computer on which it is installed or running. This compromise potentially grants full control to an outside entity, risking exposure of all secrets and keys stored on the affected system. Immediate removal of the package and rotation of all secrets from a different computer are strongly advised.
The ccsseecc-crypto-toolkit npm package contains malicious code that fully compromises any computer on which it is installed or running. It can lead to complete control by an outside entity, risking all secrets and keys stored on the affected system. Immediate removal of the package and rotation of all secrets from a different computer are strongly advised.
The npm package ccsec-form-validator contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, trusted machine. Removal of the package alone does not guarantee eradication of the malicious software or attacker control.
The ccsec-crypto-toolkit npm package contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, trusted computer. Removing the package alone may not fully remediate the infection, as the attacker may have established persistent control over the system.
The csec-form-validator npm package contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, trusted computer. Removing the package alone does not guarantee removal of all malicious software, as the attacker may have gained full control of the system.
The csec-crypto-toolkit npm package contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, trusted machine. Removal of the package alone may not eliminate all malicious software introduced by it, as the attacker may have gained full control of the system.