A vulnerability in the Erlang HTTP server's handling of HTTP headers allows an attacker to exploit conflicting HTTP framing headers, specifically the co-presence of TE and Content-Length headers, which can lead to HTTP request smuggling. This affects Erlang OTP versions from 17.0 up to but not including fixed versions such as 27.3.4.17 and others. The issue arises because the server rejects duplicate Content-Length headers but does not check for the combination of TE and Content-Length headers as identified by RFC 9112 §6.3. This can cause desynchronization between front-end and back-end HTTP processing, potentially enabling request smuggling attacks.
The npm package @yane88/listary-02 versions 1.0.0 and 1.0.1 contains malicious code or depends on a malicious package. Installing or running this package can lead to full compromise of the affected computer, potentially exposing all stored secrets and keys. Immediate removal of the package and rotation of all secrets from a different, uncompromised machine is strongly advised. However, removal of the package may not fully eliminate the malicious presence due to potential persistent control established by the attacker.
The npm package @yane88/workbuddy-02 versions 1.0.0 through 1.0.3 contains malicious code or depends on a package with malicious code. Installation or use of this package can lead to full compromise of the affected system. Secrets and keys stored on the compromised system should be rotated immediately from a secure environment. Simply removing the package may not fully eliminate the malicious presence due to potential persistent control established by the malware.
A malicious file identified by the SHA-256 hash 8e1a67a5c03b3cd818f046c7a1605afccc0ee5ce437a0d099881f1872b54bc70 was observed by OffSeq Mirage honeypot sensors twice between August 31, 2026, and October 29, 2026. The activity involved the MITRE ATT&CK technique T1105 (Ingress Tool Transfer), indicating the file was used to stage or deliver a malicious payload such as a dropper, web shell, miner, or post-exploitation tool. The attacker infrastructure was located in Germany (DE). This indicator can be used to detect the presence of this malicious file in environments by matching it against files in endpoint detection and response (EDR), antivirus (AV), and threat intelligence feeds.
A malicious file identified by the SHA-256 hash 3f3a11bafabb1a35db913cfe51995f2e357d049e268860175876ae5a93d23892 was observed by OffSeq Mirage honeypot sensors twice between August 31, 2026, and October 29, 2026. The activity involved the MITRE ATT&CK technique T1105 (Ingress Tool Transfer), indicating the file was used to stage or deliver a malicious payload such as a dropper, web shell, miner, or post-exploitation tool. The attacker infrastructure was located in Germany. This indicator can be used to detect the presence of this malicious payload in environments by matching the hash against files in endpoint detection and response (EDR), antivirus (AV), and threat intelligence feeds.
User Profile Builder WordPress plugin versions 3.3.4 and earlier contain a deserialization vulnerability in a free add-on feature that is disabled by default. This flaw allows high privilege users, such as administrators, to perform PHP Object Injection by importing crafted configuration files without proper data type validation. The plugin itself does not include a gadget chain for exploitation, so further impact depends on the presence of suitable gadgets in other installed plugins or components. No official patch or remediation guidance is currently available.
The eip712-lite npm package versions 1.0.1 and 1.0.2 contain malicious code that executes upon requiring the package. This code collects sensitive credential files and environment variables from the user's system, compresses and encodes the data, and exfiltrates it to a GitHub repository using a hardcoded and obfuscated bearer token. After exfiltration, the malicious payload in the package file is overwritten to hide its presence. The package falsely advertises itself as a dependency-free EIP-712 helper. Execution is designed to evade detection by running only once per machine and skipping execution in CI or GitHub Actions environments. Any system with this package installed should be considered fully compromised, and all secrets should be rotated immediately from a different machine.
The npm package '3layerdipstackev4sn5' version 0.1.4 contains malicious code or depends on a malicious package. Installing or running this package can lead to full compromise of the affected computer. Secrets and keys stored on the compromised system should be rotated immediately from a different, secure machine. Removal of the package alone may not fully eliminate the malicious presence due to potential persistent control by attackers.
The npm package '3layerdipstackm7mock' version 0.1.4 contains malicious code or depends on a package with malicious code. Installation or execution of this package can lead to full compromise of the affected system. Secrets and keys stored on the compromised system should be rotated immediately from a different, trusted system. Removal of the package alone may not fully eradicate the malicious presence due to potential persistent control established by the attacker.
The npm package '3layerdipstackt3wr5f' version 0.1.4 contains malicious code or depends on a malicious package. Installing or running this package can lead to full compromise of the affected system. Secrets and keys stored on the compromised system should be rotated immediately from a different machine. Removal of the package alone may not fully eliminate the malicious presence due to potential persistent control by an attacker.
The npm package '3layerdipstackulgnp8' version 0.1.4 contains malicious code or depends on a malicious package. Installation or execution of this package can lead to full compromise of the affected system. Secrets and keys stored on the compromised system should be rotated immediately from a different, trusted machine. Removing the package alone may not fully eliminate the malicious presence due to potential persistent control by attackers.
The npm package '3layerdipstack5zhcdq' version 0.1.4 contains malicious code or depends on a package with malicious code. Installation or execution of this package can lead to full compromise of the affected system. Secrets and keys stored on the compromised system should be rotated immediately from a different, secure machine. Removing the package alone may not fully eliminate the malicious presence due to potential persistent control by an attacker.
The npm package '3layerdipstack74ooau' version 0.1.4 contains malicious code or depends on a malicious package. Installing or running this package can lead to a full compromise of the affected system. Secrets and keys stored on the compromised system should be rotated immediately from a different, secure machine. Removing the package alone may not fully eliminate the malicious presence due to potential persistent control established by the attacker.
The npm package '3layerdipstackbndk47' version 0.1.4 contains malicious code or depends on a package with malicious code. Installing or running this package can lead to a full compromise of the affected computer. It is strongly advised to remove the package and immediately rotate all secrets and keys from a separate, uncompromised system. Removal of the package alone may not fully eliminate the malicious presence due to potential persistent control by an attacker.
The npm package '3layerdipstackhcymwm' version 0.1.4 contains malicious code or depends on a malicious package. Installation or execution of this package can lead to full compromise of the affected system. Secrets and keys stored on the compromised system should be rotated immediately from a different, secure machine. Removing the package alone may not fully eliminate the malicious presence due to potential persistent control established by the attacker.
The npm package '3layerdipstackl52afz' version 0.1.4 contains malicious code or depends on a package with malicious code. Installation or use of this package can lead to full compromise of the affected system. Secrets and keys stored on the compromised system should be rotated immediately from a different, trusted machine. Removing the package alone may not fully eliminate the malicious presence due to potential persistent control by attackers.
The npm package '3layerdipstacklgszmx' version 0.1.4 contains malicious code or depends on a malicious package. Installation or execution of this package can lead to full compromise of the affected system. Immediate removal of the package is advised, and all secrets and keys stored on the compromised system should be rotated from a different, secure device. However, removal of the package may not fully eliminate the malicious presence due to potential persistent control by an attacker.
The npm package '3layerdipstackqokw95' version 0.1.4 contains malicious code or depends on a package that does. Installing or running this package can lead to a full compromise of the affected system. Secrets and keys stored on the compromised system should be rotated immediately from a different, secure machine. Removal of the package alone may not fully eliminate the malicious presence due to potential persistent control by an attacker.
The npm package '3layerdipstackr5ga2v' version 0.1.4 contains malicious code or depends on a package with malicious code. Installing or running this package can lead to a full compromise of the affected system. Secrets and keys stored on the compromised system should be rotated immediately from a different, secure machine. Removing the package alone may not fully eliminate the malicious presence due to potential persistent control by attackers.
The npm package '3layerdipstackbopqb8' version 0.1.4 contains malicious code or depends on a package with malicious code. Installation or execution of this package can lead to full compromise of the affected system. Secrets and keys stored on the compromised system should be rotated immediately from a secure environment. Removal of the package alone may not fully eliminate the malicious presence due to potential persistent control by an attacker.