Malicious code in wrld-dev (npm)
The npm package wrld-dev contained malicious code that silently relayed user authentication credentials (email and password) to an attacker-controlled Supabase tenant. The package also shipped hardcoded Supabase service_role JWT tokens that grant full database admin access to two Supabase projects.
- Disclosed
- Last updated
- Blast radius
- All consumers of wrld-dev package who use its authentication functionality; any user credentials submitted to the package are exfiltrated to attacker-controlled Supabase tenant.
- Ecosystems
- Attack vectors
- Affected entities
- wrld-devnpm package containing malicious authentication code that exfiltrates user credentials to attacker-controlled Supabase instance
The npm package wrld-dev was published with intentional malicious code designed to exfiltrate user authentication credentials. The package exposes a public authentication API (auth.user.login, auth.user.register, auth.user.get, auth.user.delete, and auth.system RPC surface) that is wired to a Supabase client constructed from hardcoded credentials in the package's .env file.\n\nWhen consumers integrate wrld-dev to authenticate their own users, the package unconditionally transmits end-user email addresses and passwords to the attacker's Supabase tenant at xyxkteprdjiyctrpbaym.supabase.co on every login or registration call. This is a canonical silent-relay attack where the package's advertised functionality masks credential exfiltration.\n\nCompounding the impact, the published tarball also contains two hardcoded Supabase service_role JWT tokens with full database admin privileges for projects xyxkteprdjiyctrpbaym and ylznhlroyioyxpasyahm. These tokens bypass row-level security and grant read/write/delete access to all tables and the ability to delete arbitrary auth users. Any user who installed the package could extract these tokens from the tarball and gain admin access to those Supabase projects.\n\nThe incident was identified and reported via Amazon Inspector, with the advisory published on 2026-07-27.
Indicators of compromise
- Packages
- wrld-dev
- Domains
- xyxkteprdjiyctrpbaym.supabase.co
Remediation
- Immediately uninstall wrld-dev from all projects and dependencies
- Audit all user credentials (email/password combinations) that may have been submitted through wrld-dev authentication calls and assume they are compromised
- Force password resets for all users who may have used wrld-dev for authentication
- If you operate the affected Supabase projects, rotate the leaked service_role JWT tokens immediately
- Review npm audit logs and package.json lock files to identify all installations of wrld-dev
- Replace wrld-dev with a legitimate, audited authentication library
- Monitor the attacker-controlled Supabase projects for unauthorized access attempts
Sources
- GitHub Advisory GHSA-c4wx-mhpg-qpf5 · GitHub Advisory Database
Cite this entry
"Malicious code in wrld-dev (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 27, 2026; last updated July 27, 2026. https://supplychainattack.org/incident/malicious-code-in-wrld-dev-npm-1rw3rk
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in fetch-runtime
Malware was discovered in the npm package fetch-runtime. Any system with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malicious code in ghazaly (npm)
The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.
npmCompromised packageDependency confusion - containedcritical
Malicious code in base65-13x (npm)
base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.
npmCompromised package - containedcritical
Malicious code in kit-vim-map (npm)
The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.
npmCompromised packageMalicious commit