MAL-2024-1783 Malicious code in auth0.net (npm)
Malicious package
Published
MAL-2024-1783 is a malicious package: auth0.net (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2024-1783/ (Markdown: https://insights.sbomify.com/MAL-2024-1783/index.md)
- Package
- auth0.net
- Registry
- npm
What is MAL-2024-1783?
MAL-2024-1783 is a malicious package in auth0.net, published on 25 Jun 2024.
Official description
On
npm install, package.json's preinstall (and preupdate/test) hook runs nslookup bkxajsfkvlurhaoeotqbqf3fg2sitbxll.oast.fun. The destination oast.fun is the Project Discovery interactsh out-of-band callback service used to confirm code execution on victim hosts via a unique DNS subdomain. Firing automatically on install leaks the installer's existence and the corporate DNS resolver's egress IP to an attacker-controlled nameserver, with the unique subdomain serving as a per-victim correlation token. The package itself is hollow — index.js is empty, description is the placeholder 'Internal package', and author is 'Team' — and the package name auth0.net impersonates the Auth0 brand, consistent with a dependency-confusion attempt against an internal Auth0/.NET package name. The DNS beacon is the recon stage of that attack: the operator learns which organizations have misconfigured their registry resolution to pull this public package instead of an internal one, enabling targeted follow-on compromise.What should I do about MAL-2024-1783?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.