The 'Artemis' campaign, conducted by APT37, utilizes malicious HWP documents with embedded OLE objects to initiate attacks. The threat actor impersonates legitimate entities to gain trust before delivering the payload. The attack chain combines HWP execution with DLL side-loading techniques to evade detection. Steganography is employed to conceal malicious code, and legitimate processes are abused to load malicious DLLs. The campaign targets South Korean organizations, exploiting the widespread use of the HWP format. Multiple stages of encryption and decryption are used to obfuscate the final RoKRAT payload. The threat actor leverages cloud services like Yandex and pCloud for command and control infrastructure, complicating detection and attribution efforts.
ChurchCRM is an open-source church management system. A privilege escalation vulnerability exists in ChurchCRM prior to version 6.5.3. An authenticated user with specific mid-level permissions ("Edit Records" and "Manage Properties and Classifications") can inject a persistent Cross-Site Scripting (XSS) payload into an administrator's profile. The payload executes when the administrator views their own profile page, allowing the attacker to hijack the administrator's session, perform administrative actions, and achieve a full account takeover. This vulnerability is a combination of two separate flaws: an Insecure Direct Object Reference (IDOR) that allows any user to view any other user's profile, and a Broken Access Control vulnerability that allows a user with general edit permissions to modify any other user's record properties. Version 6.5.3 fixes the issue.
A Buffer overflow vulnerability in function fromAdvSetMacMtuWan of bin httpd in Tenda AC10V4.0 V16.03.10.20 allows remote attackers to cause denial of service and possibly code execution by sending a post request with a crafted payload (field `serverName`) to /goform/AdvSetMacMtuWan.
A Buffer overflow vulnerability in function fromAdvSetMacMtuWan of bin httpd in Tenda AC10V4.0 V16.03.10.20 allows remote attackers to cause denial of service and possibly code execution by sending a post request with a crafted payload (field `serviceName`) to /goform/AdvSetMacMtuWan.
CVE-2025-68206 addresses a vulnerability in the Linux kernel's netfilter nft_ct module related to sequence adjustment for NATed FTP connections. The issue affects FTP traffic using PASV/EPSV modes, where packet payload rewriting requires adjustments to TCP sequence and acknowledgment numbers. Without the fix, FTP NAT changes may fail, causing connection closures and kernel warnings. The vulnerability has been resolved by adding the required sequence adjustment extension when a conntrack helper is assigned to a connection with NAT bindings.
ALTCHA is privacy-first software for captcha and bot protection. A cryptographic semantic binding flaw in ALTCHA libraries allows challenge payload splicing, which may enable replay attacks. The HMAC signature does not unambiguously bind challenge parameters to the nonce, allowing an attacker to reinterpret a valid proof-of-work submission with a modified expiration value. This may allow previously solved challenges to be reused beyond their intended lifetime, depending on server-side replay handling and deployment assumptions. The vulnerability primarily impacts abuse-prevention mechanisms such as rate limiting and bot mitigation. It does not directly affect data confidentiality or integrity. This issue has been addressed by enforcing explicit semantic separation between challenge parameters and the nonce during HMAC computation. Users are advised to upgrade to patched versions, which include version 1.0.0 of the altcha Golang package, version 1.0.0 of the altcha Rubygem, version 1.0.0 of the altcha pip package, version 1.0.0 of the altcha Erlang package, version 1.4.1 of the altcha-lib npm package, version 1.3.1 of the altcha-org/altcha Composer package, and version 1.3.0 of the org.altcha:altcha Maven package. As a mitigation, implementations may append a delimiter to the end of the `salt` value prior to HMAC computation (for example, `<salt>?expires=<time>&`). This prevents ambiguity between parameters and the nonce and is backward-compatible with existing implementations, as the delimiter is treated as a standard URL parameter separator.
A hybrid phishing threat combining Salty2FA and Tycoon2FA phishing kits has emerged, leveraging code and infrastructure from both frameworks. This hybridization appears driven by Salty2FA infrastructure failures, causing fallback to Tycoon2FA hosting and payload delivery. The overlap complicates attribution and weakens detection rules tailored to either kit alone. The threat is linked to the Storm-1747 adversary group, known for Tycoon2FA operations. Indicators include multiple suspicious domains used for hosting phishing pages. Defenders should update detection logic to address cross-kit overlaps and prepare for more resilient phishing campaigns that can adapt to infrastructure disruptions. The threat is rated medium severity and does not require exploits in the wild or CVSS scoring. European organizations should be vigilant due to the widespread use of 2FA and phishing susceptibility. Mitigation requires tailored detection updates, domain monitoring, and user awareness enhancements.
The npm package @postman/pm-bin-windows-x64 versions 1.24.3, 1.24.4, and 1.24.5 was found to contain malicious code. This malicious payload, associated with the Sha1-Hulud: The Second Coming NPM worm, steals tokens and credentials, publishes them to GitHub, propagates itself to other NPM packages owned by the user, and establishes persistence via a GitHub action. Additionally, it may destroy the user's home directory.
The npm package @postman/pm-bin-macos-arm64 versions 1.24.3, 1.24.4, and 1.24.5 was found to contain malicious code. This malicious payload, associated with the Sha1-Hulud: The Second Coming NPM worm, steals tokens and credentials, publishes them to GitHub, propagates itself to other NPM packages owned by the user, and establishes persistence via a GitHub action. Additionally, it may destroy the user's home directory.
The npm package @postman/pm-bin-linux-x64 versions 1.24.3, 1.24.4, and 1.24.5 was found to contain malicious code. This malicious payload, associated with the Sha1-Hulud: The Second Coming NPM worm, steals tokens and credentials, publishes them to GitHub, propagates itself to other NPM packages owned by the user, and establishes persistence via a GitHub action. Additionally, the malware may destroy the user's home directory.
The mitok-doni-olialobina npm package is part of a malicious campaign linked to tea.xyz token rewards. It contains autopublish scripts that automatically generate and publish derivative packages with randomized names to inflate developer reputation scores. The payload modifies package.json files to remove private flags, changes version numbers, and continuously republishes variants, polluting the npm registry.
The npm package avangs-olium-nilvabint is part of a malicious campaign linked to the tea.xyz token reward scheme. It contains autopublish scripts that automatically generate and publish derivative packages with randomized names to inflate developer reputation scores. The payload modifies package.json files to remove private flags, alters version numbers, and continuously republishes variants, polluting the npm registry.
The npm package avangs-olium-niluvabint is part of a malicious campaign linked to tea.xyz token rewards. It contains autopublish scripts that automatically generate and publish derivative packages with randomized names to inflate developer reputation scores. The payload modifies package.json files to remove private flags, alters version numbers, and continuously republishes variants, polluting the npm registry.
The disturbing_felidae_z3n npm package is part of a malicious campaign linked to tea.xyz token rewards. It contains autopublish scripts that automatically generate and publish derivative packages with randomized names to inflate developer reputation scores. The payload modifies package.json files to remove private flags, alters version numbers, and continuously republishes variants, polluting the npm registry.
The disturbing_dog_z3n npm package is part of a malicious campaign linked to tea.xyz token rewards. It contains autopublish scripts that automatically generate and publish derivative packages with randomized names to inflate developer reputation scores. The malicious payload modifies package.json files to remove private flags, alter version numbers, and continuously republish variants, polluting the npm registry.
The combined_bobcat_z3n npm package is part of a malicious campaign linked to tea.xyz token rewards. It contains autopublish scripts that automatically generate and publish derivative packages with randomized names to inflate developer reputation scores. The payload modifies package.json files to remove private flags, changes version numbers, and continuously republishes variants, polluting the npm registry.
The combined_bass_z3n npm package is part of a malicious campaign linked to tea.xyz token rewards. It contains autopublish scripts that automatically generate and publish derivative packages with randomized names to inflate developer reputation scores. The payload modifies package.json files to remove private flags, alters version numbers, and continuously republishes variants, polluting the npm registry.
The binding_iguana_z3n npm package is part of a malicious campaign linked to tea.xyz token rewards. It contains autopublish scripts that automatically generate and publish derivative packages with randomized names to inflate developer reputation scores. The payload modifies package.json files to remove private flags, changes version numbers, and creates Indonesian-themed or English package variants, continuously republishing to pollute the npm registry.
A privilege escalation vulnerability was identified in GitHub Enterprise Server that allowed an authenticated Enterprise admin to gain root SSH access to the appliance by exploiting a symlink escape in pre-receive hook environments. By crafting a malicious repository and environment, an attacker could replace system binaries during hook cleanup and execute a payload that adds their own SSH key to the root user’s authorized keys—thereby granting themselves root SSH access to the server. To exploit this vulnerability, the attacker needed to have enterprise admin privileges. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.19, and was fixed in versions 3.14.20, 3.15.15, 3.16.11, 3.17.8, 3.18.2. This vulnerability was reported via the GitHub Bug Bounty program.
The disturbing_weasel_z3n npm package is part of a malicious campaign linked to tea.xyz token rewards. It contains autopublish scripts that automatically generate and publish derivative packages with randomized Indonesian-themed names. The payload modifies package.json files to remove private flags and change version numbers, enabling continuous republishing of variants. This activity pollutes the npm registry and inflates developer reputation scores fraudulently.