The npm package '@smwebserver/static' version 99.9.1 has been identified as malicious by the OpenSSF Package Analysis project. The package is flagged because it communicates with a domain known for malicious activity. There is no CVSS score available, and no known exploits in the wild have been reported. No official patch or remediation information is provided.
Red Hat OpenShift Container Platform 4.12.99 includes updates addressing multiple security vulnerabilities primarily related to denial of service and privilege escalation issues in underlying Golang components. The update fixes several CVEs involving excessive processing, recursion, and incorrect input handling. Red Hat rates the security impact of this update as Low. Users of OpenShift Container Platform 4.12 are advised to upgrade to these updated packages and images when available.
Red Hat OpenShift Container Platform 4.12.99 includes bug fixes and security updates addressing two vulnerabilities: an off-by-one error in glib's g_key_file_get_locale_string_list function (CVE-2026-58014) and a path traversal issue in glib's gdbusauthmechanismsha1.c (CVE-2026-58015). The update is rated with a low security impact by Red Hat Product Security. Users of OpenShift Container Platform 4.12 are advised to upgrade to the updated packages and images when available.
Red Hat OpenShift Container Platform 4.12.99 includes a security update addressing multiple bugs and enhancements. This update is rated by Red Hat Product Security as having a low security impact. The advisory provides updated container images and references RPM package updates in a separate advisory. Users are advised to upgrade to these updated packages and images via the official release channels.
The npm package @hrmony/benefit-essenszuschuss (version 3.99.0) contains malicious code that, upon import, harvests cloud and container secrets from the host environment. It retrieves AWS IAM role credentials via the Instance Metadata Service (IMDSv2), collects environment variables, and reads Kubernetes secrets from the filesystem. This sensitive data is then exfiltrated to a hardcoded attacker-controlled endpoint. The package mimics an internal HR utility and includes an unpinned dependency, facilitating a dependency confusion attack. Systems with this package installed should be considered fully compromised.
The npm package @hrmony/benefit-internetzuschuss (version 1.99.0) contains malicious code that, upon import, sends AWS instance metadata, environment variables, Kubernetes secrets, and IAM credentials to a hardcoded external attacker-controlled server. This package masquerades as a German social-benefits helper but performs unauthorized credential harvesting. Systems with this package installed should be considered fully compromised.
The npm package @hrmony/benefit-mobilitaet version 1.99.0 contains malicious code that, upon loading, contacts the EC2 Instance Metadata Service to retrieve sensitive instance identity and IAM role credentials. It also enumerates environment variables and Kubernetes secrets, then exfiltrates all collected data to a hardcoded attacker-controlled endpoint. This behavior indicates a dependency-confusion attack pattern and results in full compromise of any system running this package.
The npm package @hrmony/benefit-sachbezug (version 1.99.0) contains malicious code that executes upon import or require. It collects sensitive AWS EC2 instance metadata, IAM role credentials, environment variables, Kubernetes secrets, and user data, then sends this information to a hardcoded attacker-controlled endpoint. This behavior effectively compromises any system running the package, risking exposure of all stored secrets and keys.
The npm package @hrmony/benefitverwaltung version 1.99.0 contains malicious code that exfiltrates sensitive data from the host system. Upon import, it sends identifying information to a suspicious external domain and harvests AWS instance metadata, environment variables, and Kubernetes secrets. This activity compromises the security of any system running the package, potentially exposing all stored secrets and credentials.
The npm package @hrmony/component-library (version 28.99.0) contains malicious code that exfiltrates sensitive data from infected systems. Upon import, it performs unauthorized data collection and sends it to a hardcoded attacker endpoint. This includes AWS EC2 metadata, IAM credentials, Kubernetes secrets, and environment variables. The package appears to be a typosquat of a legitimate package and does not provide any legitimate functionality. Systems with this package installed should be considered fully compromised.
The npm package @hrmony/api-gateway-service-config (version 0.99.0) contains malicious code that, upon import, steals cloud IAM credentials and Kubernetes secrets from the host. It fetches AWS IMDSv2 tokens, instance metadata, environment variables, and secrets, then exfiltrates this data to a hardcoded attacker endpoint. The package also depends on an unpublished scoped package, indicating a dependency confusion attack. Installing or running this package compromises the host, requiring immediate secret rotation and package removal.
The npm package @hrmony/belegerfassung-pladddform (version 1.99.0) contains malicious code that executes immediately upon import. It sends a beacon to a hardcoded attacker-controlled endpoint, then collects sensitive AWS EC2 instance metadata, IAM role credentials, environment variables, and Kubernetes secrets, exfiltrating all this data to the same endpoint. The package uses a typosquatting name resembling a legitimate package and includes a transitive dependency from the same attacker-controlled scope, increasing the attack surface. Systems with this package installed should be considered fully compromised.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (8f03abfe6149423144b6d3143a66cbca7925bb6eb736b1ece350d5a344684eb9)
@hrmony/pladddform-frontend@48.99.0 ships an index.js whose top-level code, executed on require/import, POSTs to the hardcoded attacker host https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_pladddform-frontend and then invokes two harvesters. aws_get() queries the AWS EC2 Instance Metadata Service at 169.254.169.254 using IMDSv2 (PUT /latest/api/token) and sweeps /latest/meta-data/iam/security-credentials/ to collect instance identity, IAM role names, and temporary IAM security credentials. local_get() enumerates every entry of process.env and recursively reads /var/run/secrets/, capturing Kubernetes-mounted service-account tokens and secret files. Both payloads are POSTed to the same hardcoded hrnmn.dd.h4x.tv endpoint. The package has an empty description, no functional code beyond the stealer, an intentionally misspelled scope and name mimicking an internal 'harmony/platform-frontend', and declares a dependency on the similarly look-alike '@hrmony/kit-5', consistent with a dependency-confusion typosquat targeting an internal package name.
## Source: ghsa-malware (37ed7f1bf9d1ce61730644e3ac7eaf7f1525da3d26b9f9ba1f171d2ff2b72ae6)
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.
In the Linux kernel, the following vulnerability has been resolved: bpf: Reject key-less BTF for hash maps map_check_btf() allows a key-less BTF (btf_key_type_id == 0) only for maps that have a ->map_check_btf callback, and leaves the actual decision to that callback. Hash maps used to have no ->map_check_btf, so a key-less BTF was rejected outright. That changed when htab and rhtab gained a ->map_check_btf to register a dtor - htab in commit 1df97a7453ee ("bpf: Register dtor for freeing special fields") and rhtab in commit 6905f8601298 ("bpf: Allow special fields in resizable hashtab"). Neither looks at the key, so a key-less hash map now passes map_check_btf() and gets created. Reading it back through bpffs feeds the key type_id 0 into btf_type_seq_show(); btf_type_by_id() returns the void type, kind_ops[BTF_KIND_UNKN] is NULL, and btf_type_show() dereferences it: RIP: 0010:btf_type_show+0x223/0x2e0 kernel/bpf/btf.c:8232 RSP: 0018:ffffc9000399f868 EFLAGS: 00010206 RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000000005 RSI: 0000000000000000 RDI: 0000000000000028 RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 R10: ffffc9000399f970 R11: 0000000000000001 R12: ffffffff9b96b140 R13: ffffc9000399f8e0 R14: ffff88803d393c00 R15: 0000000000000003 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000200000000000 CR3: 000000003d213000 CR4: 0000000000352ef0 DR0: 0000000039ae8f55 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Call Trace: <TASK> btf_type_seq_show_flags+0xca/0x120 kernel/bpf/btf.c:8250 htab_map_seq_show_elem+0x12e/0x350 kernel/bpf/hashtab.c:1669 map_seq_show+0x13d/0x1e0 kernel/bpf/inode.c:293 traverse.part.0.constprop.0+0x107/0x650 fs/seq_file.c:112 traverse fs/seq_file.c:99 [inline] seq_read_iter+0x93f/0x1270 fs/seq_file.c:196 seq_read+0x344/0x4d0 fs/seq_file.c:163 vfs_read+0x1e4/0xb40 fs/read_write.c:572 ksys_pread64 fs/read_write.c:764 [inline] __do_sys_pread64 fs/read_write.c:772 [inline] __se_sys_pread64 fs/read_write.c:769 [inline] __x64_sys_pread64+0x1eb/0x250 fs/read_write.c:769 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe+0x77/0x7f Reject a key-less BTF in htab_map_check_btf() and rhtab_map_check_btf(), restoring the previous behavior.
DBI versions before 1.652 for Perl allow a heap out-of-bounds write via an unvalidated numeric placeholder that sets the binder counter in preparse. preparse reserves seven output bytes per input byte, the width of the longest ':p99999' expansion. The ':N' branch parses the number with `atoi(src)` and assigns it to the binder counter with no range check, so a statement containing ':2147483648' leaves the counter negative (-2147483648 with glibc, where atoi wraps). Each following '?' then expands through `sprintf(start, ":p%d", idx++)` to ':p-2147483648', 14 bytes with the terminating NUL where the buffer budgets 7. The placeholder limit added in 1.650 tests the counter against 99,999, which a negative counter passes. Any caller that preparses an untrusted statement into ':pN' style placeholders gets a heap out-of-bounds write that grows with the number of '?' marks following the poisoned placeholder. The '?' and '%s' return styles compare the parsed number against the expected sequence and error out, and are unaffected.
Moquette is a lightweight Java MQTT broker. Prior to 0.18.1, H2PersistentQueue derives a session's message-map name as queue_ plus the client ID and its metadata-map name as queue_ plus the client ID plus _meta. A durable session whose client ID ends in _meta can therefore make its message map collide with another client's metadata map. The colliding sessions read and write the same H2 MVStore map with incompatible value types, which can corrupt queue head and tail data and cause message loss, misdelivery, failed queue reloads, or exposure of queued content across sessions. This issue is fixed in version 0.18.1.
The npm package 'some-tool-package' version 99.0.0 contains malicious code or depends on a malicious package. Installing or running this package can result in full compromise of the affected computer. Secrets and keys stored on the compromised system should be rotated immediately from a different, secure machine. Removing the package alone may not eliminate all malicious software introduced by it.
The npm package bnppf-flag-icons version 99.99.99 contains malicious code that executes automatically during installation. It collects the host's hostname and OS username and sends this information to an attacker-controlled endpoint. This behavior indicates a dependency confusion attack, as the version number is unusually high and the package name suggests a benign flag-icons library. Installing this package compromises the host, potentially exposing all stored secrets and keys.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (c1ac938360c682e2489d11de9278697e7e2e85d73c612d2ab60ed28553bb5573)
The package's preinstall script (scripts.preinstall = 'node index.js') runs automatically on npm install and collects os.userInfo().username and os.hostname(), then issues a dns.lookup against a subdomain of 31ee29fe-db68-4fd3-86a2-2b707b9e95f0.dnshook.site with the username and hostname embedded in the queried label. This is a DNS-based exfiltration beacon: installing the package transmits installer host identifiers to a non-first-party canary domain over DNS resolution at install time. The version number 99.99.99 and package name shape are consistent with a dependency-confusion lure targeting an internal package name.
A vulnerability in the Linux kernel's nfsd_direct_write function causes improper detection of partial writes. The flaw allows the write loop to continue after a short write that completes between 50% and 99% of a segment, resulting in subsequent data being written at incorrect file offsets and over-reporting of bytes written to the NFS client. This issue has been fixed by correctly snapshotting the segment's byte count before the write and comparing the write result against that snapshot.