The npm package 'bytecraft' versions 1.5.0 and 2.0.0 were analyzed for malicious code. No suspicious behavior or indicators of supply-chain attacks were found in these versions. The package does not exhibit install-time network activity, remote code fetching, credential access, environment scraping, or hardcoded exfiltration endpoints. There is no evidence supporting the presence of malicious code in these releases.
A malicious file identified by the SHA-256 hash d8a8cea14b12aa75047979f929bdf10b9003884580398c3c13d2b4fb04209410 was observed by OffSeq Mirage honeypot sensors on July 20, 2026. This file was detected 10 times during attacker activity involving the T1105 technique (Ingress Tool Transfer). The malicious payload could be a dropper, web shell, miner, or post-exploitation tool. The attacker infrastructure was located in Poland and Vietnam. This indicator can be used to detect the presence of this specific malicious file in environments and security tools.
Meshtastic is an open source mesh networking solution. Prior to version 2.7.23.b246bcd, a single node advertising a User.long_name that contains a malformed character encoding can render other radios unusable over BLE when managed through the iOS app. The malformed name does not need to be maliciously crafted — it can arise from ordinary buffer truncation and has been observed occurring naturally in the wild. At least one code path could place a null terminator in the middle of a multibyte sequence, leaving a malformed User.long_name in the node database. The problem surfaced downstream: the iOS app enforced encoding validation and therefore cannot parse a node database once it contains a poisoned entry. This caused BLE sync to enter a fail/retry loop, resulting in loss of control over the affected device. For a typical user managing their radio with the iOS app, the device becomes effectively unusable until the poisoned node ages out of the on-device database, or unless they have an alternate management path (e.g., the Python CLI, which can be used to identify and remove the offending entries manually). Because the malformed name propagates through the mesh, the temporary presence of a single affected node can degrade BLE management for iOS users across a wide geographical area for an extended period. Less technical users have no straightforward recovery path. Starting in version 2.7.23.b246bcd, the firmware has added input sanitization and regression tests demonstrating recovery for already-poisoned devices. The apps have also taken steps to ensure more graceful handling of malformed encoding sequences as well.
A malicious file identified by the SHA-256 hash 31d4181843b1ed10a7e7cb3f108f6d6c50a7a4452ee52ddacabe8ca77260615e was observed by OffSeq Mirage honeypot sensors five times between July 19 and July 30, 2026. The file is associated with attacker activity involving the MITRE ATT&CK technique T1105 (Ingress Tool Transfer). The malicious payload could be 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 specific malicious payload in environments by matching the hash against files in endpoint detection and response (EDR), antivirus (AV), and threat intelligence feeds.
A malicious file identified by the SHA-256 hash a531f3e6224862abd00091c4955d535ace2bb886df53bdcd59c3a32b44c93629 was observed by OffSeq Mirage honeypot sensors during attacker activity between July 19 and July 22, 2026. The file is associated with the MITRE ATT&CK technique T1105 (Ingress Tool Transfer) and may represent 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 against endpoint detection and response (EDR), antivirus (AV), and threat intelligence feeds.
CVE-2026-63992 is a critical vulnerability in the Linux kernel affecting version 5.9. It involves an out-of-bounds access triggered by the function iptunnel_pmtud_check_icmp() when it assumes the presence of a transport header in certain tunneled packets, which may not be set. This flaw can lead to memory access errors and potential denial of service. The issue has been fixed in several Linux kernel commits.
An incomplete fix in Skipper before version 0.27.26 allows an oversized HTTP request body to bypass Open Policy Agent (OPA) deny-on-presence Rego policies. When a request declares a Content-Length larger than the configured max body size, OPA receives an empty parsed body, causing deny policies to fail open while the full payload reaches the upstream service. This can lead to unauthorized requests being allowed based on body content. The issue affects deployments using opaAuthorizeRequestWithBody with deny-on-presence policies. Mitigation involves updating policies to explicitly check the truncated_body attribute to block or deny oversized bodies.
The Bricksforge plugin for WordPress contains a critical privilege escalation vulnerability in all versions up to and including 3.1.8.6. This flaw arises from improper validation of the fieldIds parameter in the Pro Forms registration action, allowing unauthenticated attackers to add arbitrary field IDs to the trusted whitelist. Exploiting this vulnerability enables attackers to register a new administrator account by submitting a crafted request to a publicly accessible Bricksforge Pro Forms registration form. Successful exploitation requires the presence of a public Bricksforge Pro Forms element configured with the User Registration action.
The npm package internallib_v907 contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, and all secrets and keys stored on the affected machine should be rotated immediately from a different, secure device. Simply removing the package does not guarantee the removal of all malicious software introduced by it.
The npm package 'true' versions 0.0.1 through 0.0.4 contains malicious code that compromises any computer on which it is installed. The presence of this package indicates a full system compromise, requiring immediate rotation of all secrets and keys from a separate, secure machine. Removal of the package alone does not guarantee elimination of all malicious software introduced by it.
The npm package @sauruslord/eslint-config contains malicious code that fully compromises any computer on which it is installed or run. The presence of this package indicates a complete system compromise, requiring immediate rotation of all secrets and keys from a separate, trusted machine. Removing the package alone does not guarantee removal of all malicious components introduced by its installation.
The npm package 'zaldy-baileys' contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, requiring immediate rotation of all secrets and keys from a separate, secure machine. Removal of the package alone does not guarantee elimination of all malicious software introduced by it.
A malicious file identified by the SHA-256 hash 40db9279ba409757c074048529be5bf8f141fa022489a965792e7f7de2223b78 was observed by OffSeq Mirage honeypot sensors during attacker activity between July 14 and July 26, 2026. The file is associated with the ATT&CK technique T1105 (Ingress Tool Transfer), indicating it 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 Great Britain. This hash can be used as an indicator of compromise (IOC) to detect the presence of this malicious file in environments and security tools.
The npm package @codex2005/logger-core contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, requiring immediate rotation of all secrets and keys from a separate, trusted machine. Simply removing the package does not guarantee removal of all malicious software introduced by it.
The npm package 'tipsen-poc-again' contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, requiring immediate rotation of all secrets and keys from a separate, uncompromised device. Simply removing the package does not guarantee removal of all malicious software introduced by it.
The npm package 'abuden230' contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, and all secrets and keys stored on the affected machine should be rotated immediately from a different, trusted device. Removing the package alone does not guarantee the removal of all malicious software introduced by it.
The npm package 'abuden210' contains malicious code that can fully compromise any computer on which it is installed or running. The presence of this package indicates a severe security breach, and all secrets and keys stored on the affected system should be rotated immediately from a different, secure machine. Removing the package alone does not guarantee removal of all malicious software introduced by it.
The npm package 'abuden225' contains malicious code that fully compromises any computer on which it is installed or running. The presence of this package indicates a complete system compromise, and all secrets and keys stored on the affected machine should be rotated immediately from a separate, secure device. Removing the package alone does not guarantee removal of all malicious software introduced by it.
The npm package 'nottuff8' contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, and all secrets and keys stored on the affected machine should be rotated immediately from a different, trusted device. Removing the package alone may not eliminate all malicious software introduced by its installation.
The npm package 'nottuff16' contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, requiring immediate rotation of all secrets and keys from a separate, secure machine. Simply removing the package does not guarantee removal of all malicious components introduced by it.