clsx-js
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-8jmh-pvvx-wjrf
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in clsx-js (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (23e4e85f63d161234d84c774fdff696827934a27282be2ce9ff362a756246ee6)
On npm install, dist/postinstall.js base64-decodes the URL https://api.npoint.io/984b75c022a70cf00c39, fetches JSON from this anonymous mutable JSON-hosting service via axios, and pipes the response's data.content into a detached node child process's stdin for execution. The fetch has no version pin, no hash/signature verification, and the source is operator-mutable — the attacker can swap the executed payload at any time. The package additionally typosquats the widely-used clsx utility (by Luke Edwards): name is a one-token edit, and the description, author name, email, and homepage are copied verbatim from the legitimate clsx to impersonate the upstream maintainer. The genuine clsx ships no postinstall; this fork adds one whose only purpose is the remote-code dropper. A malformed Dependencies (capital-D) field also lists child_process, a known squat name. Installing this package on any machine results in arbitrary attacker-controlled code execution under the installer's user account.
Source: ghsa-malware (64650ce568f6dcb32276c86bc8e12ed0ea072a19425670e47310e7f4b3b01715)
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.
Not rated by the source.
0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0