@0xlr/clerk-auth
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-57r8-xw4c-5j59
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in @0xlr/clerk-auth (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (2ff421a5ccb412fd8455e89a1b9875b427ed34af12fa4b188ed4418cd8f52a74)
On npm install, postinstall.js enumerates the entire process environment (Object.keys(process.env).sort().forEach) along with hostname, username, home directory, cwd, argv, and OS metadata, then POSTs the JSON payload over HTTPS to rytxau88zxh61dw6qz4yn19naeg54vsk.oastify.com (a Burp Collaborator subdomain controlled by the attacker). Any secrets present in the installer's environment at install time — CI tokens, NPM_TOKEN, AWS_*, GitHub tokens, etc. — are leaked to the operator of that Collaborator instance. The package itself is hollow: name @0xlr/clerk-auth with version 999.0.0 and a description reading 'Placeholder reservation - company should register clerk-auth' is a dependency-confusion lure aimed at organizations that internally reference an unregistered clerk-auth package.
Source: ghsa-malware (072d9c29e38d3418b3b53542e0d9bac6de02e95946737f9f3f0378f29534d314)
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