The npm package 'sol-wallet-adapter' versions 1.0.0, 1.0.1, and 1.0.7 are malicious. These versions contain no functional code but execute a preinstall script that sends the machine's hostname, OS username, and local time to a Discord webhook, potentially leaking sensitive environment information. The package was published by suspicious accounts and communicates with a domain linked to malicious activity.
Metalama is a Roslyn-based open-source patterns and architecture toolkit for C#. Prior to 2025.1.18, 2026.0.25 and 2026.1.19, Metalama.Framework and Metalama.Tool load and execute compile-time assemblies, auxiliary executable tools and embedded helper assemblies from predictable temporary directories. On `Linux` and `macOS`, the default `Path.GetTempPath()` location is world-writable, and existing artifacts are trusted based on sentinel or `.completed` marker files rather than integrity verification. A local unprivileged user on a shared machine or CI/build agent can pre-create the deterministic directory structure and plant a malicious DLL with the matching sentinel. When a higher-privileged developer or build account subsequently builds, Metalama skips regeneration and executes the planted artifact in the compiler, IDE or MSBuild process as the building user. This permits cross-user privilege escalation, reading source and secrets, supply-chain tampering with build output, or disrupting builds. Default Windows per-user temporary directories are protected by ACLs and are not affected. Deployer-selected insecure cache locations are outside the vulnerability's scope. This issue is fixed in versions 2025.1.18, 2026.0.25 and 2026.1.19.
A vulnerability in filelock's ReadWriteLock and AsyncReadWriteLock components allows a local user who can place or overwrite the SQLite lock database file to cause every acquire operation to stall or hang indefinitely, ignoring timeout and blocking settings. This results in a denial of service affecting availability only, with no confidentiality or integrity impact. The issue affects filelock versions 3.20.4 through 4.2.0 and requires the attacker to have write access to the lock file path or directory. The vulnerability is rated medium severity with a CVSS score of 5.5.
A symlink swap vulnerability in filelock's SoftFileLock writability check allows a local user to leak one bit of information about whether a path exists and is writable by the lock user. This occurs because the check uses os.lstat followed by os.access, which follows symlinks, enabling a time-of-check to time-of-use (TOCTOU) leak. The vulnerability affects filelock versions 3.32.6 through 4.2.0 and is mitigated on Linux by the fs.protected_symlinks kernel setting in common sticky world-writable directories like /tmp. The impact is limited to leaking a single bit per acquire attempt, with no integrity or availability impact. The vulnerability requires local access, the ability to create entries in the lock directory, and high timing precision to exploit.
A vulnerability in filelock versions 4.1.0 through 4.2.0 allows a local unprivileged user to evict a fresh lock file owned by another user by exploiting inode reuse and coarse clock timestamp manipulation on ext4 or overlayfs filesystems. This causes two processes of the lock owner to enter a critical section simultaneously, violating lock integrity without affecting confidentiality or availability. The attack requires specific timing conditions and filesystem behavior, making it complex to exploit.
A vulnerability in filelock versions 3.22.0 through 4.2.0 allows a local unprivileged user to cause two processes of the lock owner to hold the same lock simultaneously. This occurs due to a race condition in the stale-lock break mechanism that relies on inode numbers and modification times. On filesystems like ext4 and xfs that reuse inode numbers immediately, an attacker who can create files in the lock directory (e.g., /tmp with sticky bit) can manipulate lock files to cause overlapping lock holders without detection. The integrity of the lock is compromised, but confidentiality and availability are not affected.
A vulnerability in filelock's SoftReadWriteLock and AsyncSoftReadWriteLock components allows a local user who owns the lock's .rw directory tree to cause the lock holder's refresh operation to hang or overwrite files. This occurs because the holder refresh writes to a file descriptor opened with O_NOFOLLOW, which does not prevent opening hard links or FIFOs (named pipes). On default Linux systems, a malicious local user can rename a FIFO into the holders directory, causing the lock holder's write or read lock operation to hang indefinitely, bypassing timeout and leaving heartbeat threads asleep. Additionally, if the kernel permits hard links to files not owned by the user (e.g., Linux with fs.protected_hardlinks=0), the attacker can cause the lock user to overwrite the first ~135 bytes of one of its own private files. The issue affects filelock versions >=4.0.0 and <=4.2.0 and has a CVSS score of 6.1 (medium severity).