---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (cb3e0cb5c95475ce69c3672be6acfb9283bc6e29a1d7ba7452c922e7dc96a966)
On require()/import, index.js runs an IIFE that POSTs a getAccountInfo RPC call to https://api.devnet.solana.com for Solana account 4WF8QCFEnVD7BLs3QAVe2SjxRZ4n3EboCsdhj363VAqZ, base64-decodes the returned account data, reads a length prefix at offset 32, extracts the payload bytes at offset 36, and passes the resulting UTF-8 source to `new Function('require','module','exports', src)` — executing arbitrary JavaScript with the full privileges of the importing Node.js process. The payload is mutable (the attacker can rewrite the on-chain account data at any time), unpinned, not hash- or signature-verified, and delivered from infrastructure the attacker controls. The use of a public blockchain RPC endpoint as a C2 channel is designed to evade simple domain/IP blocking while remaining fully attacker-rewritable. The package name masquerades as a BigInt/filesystem utility; there is no legitimate reason for such a library to fetch and eval remote code on load.
## Source: ghsa-malware (b67cb388cf855ef52b8e274269861017bb7ce33349b187cd41ba2ff553ecb320)
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.
Red Hat OpenShift Container Platform is Red Hat's cloud computing
Kubernetes application platform solution designed for on-premise or private
cloud deployments.
This advisory contains the container images for Red Hat OpenShift Container
Platform 4.17.47. See the following advisory for the RPM packages for this
release:
https://access.redhat.com/errata/RHSA-2026:0701
Space precludes documenting all of the container images in this advisory.
See the following Release Notes documentation, which will be updated
shortly for this release, for details about these changes:
https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/release_notes/
Security Fix(es):
* bind: Resource exhaustion via malformed DNSKEY handling (CVE-2025-8677)
* bind: Cache poisoning attacks with unsolicited RRs (CVE-2025-40778)
* bind: Cache poisoning due to weak PRNG (CVE-2025-40780)
* expat: libexpat in Expat allows attackers to trigger large dynamic memory
allocations via a small document that is submitted for parsing
(CVE-2025-59375)
* libssh: Invalid return code for chacha20 poly1305 with OpenSSL backend
(CVE-2025-5987)
* openssl: Out-of-bounds read & write in RFC 3211 KEK Unwrap
(CVE-2025-9230)
* libxslt: libxml2: Inifinite recursion at exsltDynMapFunction function in
libexslt/dynamic.c (CVE-2025-9714)
* qemu-kvm: VNC WebSocket handshake use-after-free (CVE-2025-11234)
For more details about the security issue(s), including the impact, a CVSS
score, acknowledgments, and other related information, refer to the CVE
page(s) listed in the References section.
All OpenShift Container Platform 4.17 users are advised to upgrade to these
updated packages and images when they are available in the appropriate
release channel. To check for available updates, use the OpenShift CLI (oc)
or web console. Instructions for upgrading a cluster are available at
https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html-single/updating_clusters/index#updating-cluster-cli.
Red Hat OpenShift Container Platform is Red Hat's cloud computing
Kubernetes application platform solution designed for on-premise or private
cloud deployments.
This advisory contains the container images for Red Hat OpenShift Container
Platform 4.18.31. See the following advisory for the RPM packages for this
release:
https://access.redhat.com/errata/RHSA-2026:0331
Space precludes documenting all of the container images in this advisory.
See the following Release Notes documentation, which will be updated
shortly for this release, for details about these changes:
https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/release_notes/
Security Fix(es):
* bind: Resource exhaustion via malformed DNSKEY handling (CVE-2025-8677)
* bind: Cache poisoning attacks with unsolicited RRs (CVE-2025-40778)
* bind: Cache poisoning due to weak PRNG (CVE-2025-40780)
* expat: libexpat in Expat allows attackers to trigger large dynamic memory
allocations via a small document that is submitted for parsing
(CVE-2025-59375)
* openssl: Out-of-bounds read & write in RFC 3211 KEK Unwrap
(CVE-2025-9230)
* qemu-kvm: VNC WebSocket handshake use-after-free (CVE-2025-11234)
For more details about the security issue(s), including the impact, a CVSS
score, acknowledgments, and other related information, refer to the CVE
page(s) listed in the References section.
All OpenShift Container Platform 4.18 users are advised to upgrade to these
updated packages and images when they are available in the appropriate
release channel. To check for available updates, use the OpenShift CLI (oc)
or web console. Instructions for upgrading a cluster are available at
https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html-single/updating_clusters/index#updating-cluster-cli.
This analysis details a sophisticated DPRK-linked operation called Contagious Interview, which uses a fake job platform to target U.S. AI talent. The campaign mimics legitimate recruitment processes, offering job listings from well-known tech companies to lure victims. The platform, hosted at lenvny[.]com, is designed to appear as a legitimate AI-powered interview tool. It employs various techniques to establish credibility, including professional design, fake testimonials, and comparisons with real companies. The attack culminates in a malware delivery through a clipboard hijacking technique, triggered when victims attempt to record a video introduction. This operation specifically targets high-value professionals in AI and cryptocurrency sectors, aiming to gain access to strategic information and financial assets.
Avnet, a major electronics distributor, has confirmed a security breach involving unauthorized access to its data. Although the company states that the stolen data is unreadable, the breach itself is classified as high severity due to potential risks associated with data exposure. There are no known exploits in the wild related to this incident, and technical details remain limited, with the primary source being a Reddit InfoSec news post linking to a BleepingComputer article. European organizations that rely on Avnet for electronics supply chain services could face indirect impacts, including operational disruptions or risks from compromised supplier data. Mitigation should focus on verifying supply chain integrity, enhancing monitoring for suspicious activity, and ensuring robust encryption and data protection measures. Countries with significant electronics manufacturing and distribution sectors, such as Germany, France, and the Netherlands, are likely to be most affected. Given the lack of detailed technical information and the unreadability of stolen data, the suggested severity is high, reflecting the breach's potential impact on confidentiality and supply chain trust. Defenders should prioritize incident response readiness and supply chain risk assessments related to Avnet services.
New Android Banking Trojan “Klopatra” Uses Hidden VNC to Control Infected Smartphones
Source: https://thehackernews.com/2025/10/new-android-banking-trojan-klopatra.html
In the Linux kernel, the following vulnerability has been resolved: net: stmmac: fix TSO DMA API usage causing oops Commit 66600fac7a98 ("net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data") moved the assignment of tx_skbuff_dma[]'s members to be later in stmmac_tso_xmit(). The buf (dma cookie) and len stored in this structure are passed to dma_unmap_single() by stmmac_tx_clean(). The DMA API requires that the dma cookie passed to dma_unmap_single() is the same as the value returned from dma_map_single(). However, by moving the assignment later, this is not the case when priv->dma_cap.addr64 > 32 as "des" is offset by proto_hdr_len. This causes problems such as: dwc-eth-dwmac 2490000.ethernet eth0: Tx DMA map failed and with DMA_API_DEBUG enabled: DMA-API: dwc-eth-dwmac 2490000.ethernet: device driver tries to +free DMA memory it has not allocated [device address=0x000000ffffcf65c0] [size=66 bytes] Fix this by maintaining "des" as the original DMA cookie, and use tso_des to pass the offset DMA cookie to stmmac_tso_allocator(). Full details of the crashes can be found at: https://lore.kernel.org/all/d8112193-0386-4e14-b516-37c2d838171a@nvidia.com/ https://lore.kernel.org/all/klkzp5yn5kq5efgtrow6wbvnc46bcqfxs65nz3qy77ujr5turc@bwwhelz2l4dw/