The npm package 'nottuff10' 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. Removing the package alone does not guarantee removal of all malicious software introduced by it.
The npm package 'sixseven5' 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 removal of all malicious software introduced by it.
The npm package 'backup1-gg' 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. Removing the package alone may not eliminate all malicious software introduced by its installation.
The npm package 'captainindia' was found to contain malicious code or dependencies with malicious code. Systems with this package installed should be considered fully compromised. Immediate removal of the package and rotation of all secrets and keys from a different, uncompromised computer is strongly advised. Due to the potential full control gained by attackers, removing the package may not fully eradicate the malicious presence.
The npm package '@gt-test-exp/profiler-exp-00000006' contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, necessitating immediate rotation of all secrets and keys from a different, secure machine. Simply removing the package does not guarantee removal of all malicious artifacts or backdoors introduced by the package.
The npm package '@gt-test-exp/profiler-exp-00000002' contains malicious code that fully compromises any computer on which it is installed or running. The presence of this package indicates a complete security breach, and all secrets and keys stored on the affected system should be rotated immediately from a separate, secure device. Simply removing the package does not guarantee the removal of all malicious software or backdoors introduced by it.
The npm package 'gpapps' 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 different, trusted machine. Removing the package alone does not guarantee removal of all malicious software introduced by it.
The npm package 'apps-gpt' contains malicious code that fully compromises any computer on which it is installed or running. The presence of this package implies that all secrets and keys stored on the affected system should be considered compromised and must be rotated immediately from a different, secure machine. Removing the package alone does not guarantee removal of all malicious software introduced by it, as the attacker may have gained full control of the system.
A malicious file identified by the SHA-256 hash 578bfa5ed439f9d83b8197f4cf55c893c9f6447929c8df72c696fa9177213d3f was observed twice on July 12, 2026, by OffSeq Mirage honeypot sensors. The file is associated with attacker activity involving the MITRE 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 the United States. No known exploits in the wild or affected software versions are reported. This indicator can be used to detect the presence of this malicious file in environments via file hash matching in EDR, AV, or threat intelligence feeds.
A weakness has been identified in apidevtools json-schema-ref-parser. This impacts the function Refs.set/Pointer.set in the library lib/pointer.ts. Executing a manipulation can lead to improperly controlled modification of object prototype attributes. The attack can be launched remotely. Upgrading to version 15.3.6 will fix this issue. This patch is called a786bc6afc3674f650496472ee93d5cf74c4bd84. It is suggested to upgrade the affected component. The project maintainer confirms: "I reproduced prototype pollution through the public $Refs.set() API in published versions 7.1.4, 9.0.0, 11.0.0, 14.0.0, 14.2.1, 15.3.0, and 15.3.5. The same pointer is rejected by 15.3.6 without modifying Object.prototype. This reported path requires an application to pass an attacker-controlled pointer to $Refs.set(); dependency presence alone does not establish exploitability."
Multiple official .gov domains, including Woodway, TX and NYC Council, have been found to have pornographic PDF files indexed by Google. These PDFs contain titles referencing adult content and are publicly accessible via search engines, suggesting possible SEO spam or unauthorized uploads. The main websites appear to function normally, but the presence of these indexed PDFs indicates a potential compromise or misuse of the hosting infrastructure. Similar issues have been observed on other government domains such as louisiana.gov and lacity.gov, implying a broader problem affecting multiple government sites.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (c7d5453a0b1576ed8880071cda901607e79f25378700d3f999ab2c9715e00635)
searchresults@999.0.0 is a high-version dependency-confusion squat on the generic name 'searchresults'. package.json declares preinstall and postinstall = 'node callback.js', so on npm install callback.js executes automatically and collects installer identity (username, uid/gid, homedir, shell, os.hostname(), platform, cwd, local IP, external IP fetched from api.ipify.org) plus CI context (GITHUB_REPOSITORY, GITHUB_ACTOR, JENKINS_URL, BUILD_NUMBER) and POSTs it to a hardcoded Discord webhook and a callback URL. It additionally fingerprints which installers hold monetizable CI credentials by probing for presence of AWS_ACCESS_KEY_ID, GITHUB_TOKEN, NPM_TOKEN, and DOCKER_PASSWORD in the environment and reporting the result to the same webhook. A DNS-based fallback channel base64-encodes the collected info and issues a DNS lookup of that value as a subdomain of the callback host, bypassing HTTP egress filtering. The 999.0.0 version and generic name are engineered to win npm semver resolution against internally-named private packages, giving install-time code execution on arbitrary organizations. Self-labeling as 'security research PoC' does not constitute installer consent.
## Source: ghsa-malware (c2bf6ed6443578713721cde803bd5f2376cd93913392387e3b342796878e53ff)
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 ts-await package on npm 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. Removing the package alone does not guarantee removal of all malicious components introduced by its installation.
The npm package @whs4/whs4_npm 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 separate, trusted device. Removing the package alone does not guarantee removal of all malicious software introduced by it.
The wsh4_npm package on the npm ecosystem 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 machine. Removing the package alone does not guarantee eradication of all malicious software introduced by it.
The load-nuxt package on npm 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 software introduced by it.
The npm package 'shopify-internel' 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 different, trusted machine. Removing the package alone does not guarantee removal of all malicious software introduced by it.
Improper Check for Unusual or Exceptional Conditions vulnerability in phoenixframework phoenix (Presence JavaScript client) allows an attacker with ordinary channel access to cause a persistent client-side denial of service against every viewer of a presence channel topic.
This vulnerability is associated with program files assets/js/phoenix/presence.js and program routines Presence.syncState and Presence.syncDiff.
The Phoenix JavaScript presence client checks whether a presence already exists with a bare truthiness test (state[key]) instead of an own-property check. Presence keys can be attacker-controlled, because applications track presences under a username or id supplied by the client. A user who joins a channel choosing a key that is an Object.prototype member name (__proto__, constructor, toString, hasOwnProperty, and similar) makes that lookup return JavaScript's built-in Object.prototype instead of undefined. Because the prototype is truthy, the code treats it as an existing presence and reads .metas.map(...) off it, which throws an uncaught TypeError.
The exception propagates out of the presence message handler, so the local state is never updated and onSync() never fires. Because the malicious key is tracked on the server, it is re-pushed on every presence update and keeps re-throwing, so presence sync stays broken for every viewer of that channel topic until the attacker leaves. Both syncState and syncDiff use the same unsafe existence-check pattern. The impact is limited to the affected topic and is a read-time confusion of the prototype object, not a mutation of Object.prototype (it is not prototype pollution).
This issue affects phoenix: from 1.2.0-rc.0 before 1.5.15, from 1.6.0-rc.0 before 1.6.17, from 1.7.0-rc.0 before 1.7.24, and from 1.8.0-rc.0 before 1.8.9; phoenix: from 1.2.0-rc.0 before 1.5.15, from 1.6.0-rc.0 before 1.6.17, from 1.7.0-rc.0 before 1.7.24, and from 1.8.0-rc.0 before 1.8.9.
The RubyGems package 'wmwk2ab' version 0.0.1 contains malicious code as identified by the OpenSSF malicious packages project. This package is flagged as a security threat due to the presence of malicious content. No CVSS score or detailed technical exploit information is provided.
The RubyGems package 'wandczvof2git' version 0.0.1 contains malicious code as identified by the OpenSSF malicious packages database. This package is flagged as a malicious package with no known exploits in the wild and no CVSS score assigned. The threat involves the presence of malicious code within the package itself rather than a traditional software vulnerability.