Which versions of @0xlr/clerk-auth are malicious?

The following npm versions of @0xlr/clerk-auth are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate @0xlr/clerk-auth if I installed it?

Remove @0xlr/clerk-auth from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is @0xlr/clerk-auth part of a known attack campaign?

Yes — @0xlr/clerk-auth is associated with the IN-MAL-2026-004977, IN-MAL-2026-004978 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect @0xlr/clerk-auth in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking @0xlr/clerk-auth and packages like it before any post-install script runs.

Malicious package

@0xlr/clerk-authnpm

Malicious code in @0xlr/clerk-auth (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5385

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @0xlr/clerk-auth

What this malware does

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.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

2ff421a5ccb412fd8455e89a1b9875b427ed34af12fa4b188ed4418cd8f52a74

f75b5cbd68fb15cdb11785a7a8c83cefd8ad2bb6cf7ed6692f120a5bd8f4f135

Frequently asked questions

No. @0xlr/clerk-auth on npm has been identified as a malicious package (version 999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004977IN-MAL-2026-004978

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection