Which versions of @0xlr/supabase-db are malicious?

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

How do I remediate @0xlr/supabase-db if I installed it?

@0xlr/supabase-db is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @0xlr/supabase-db — how do I know if it already compromised me?

If @0xlr/supabase-db was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @0xlr/supabase-db part of a known attack campaign?

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

How do I find @0xlr/supabase-db across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @0xlr/supabase-db (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @0xlr/supabase-db across your stack and pipelines.

Malicious package

@0xlr/supabase-dbnpm

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

MAL-2026-5390

Immediate action

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

npm uninstall @0xlr/supabase-db

What this malware does

On npm install, the package's postinstall.js script enumerates all of process.env and collects host identifiers (os.hostname(), username, homedir, cwd, argv, platform), then POSTs the JSON payload over HTTPS to rytxau88zxh61dw6qz4yn19naeg54vsk.oastify.com (a Burp Collaborator out-of-band domain). Because this fires automatically during install, any CI tokens, npm tokens, cloud credentials (AWS_*, GCP, Azure), and other secrets present in the installer's environment are exfiltrated to an attacker-controlled host. The package also exhibits a dependency-confusion / namespace-squat shape: it self-describes as 'Placeholder reservation - company should register supabase-db' and is published at version 999.0.0 under the @0xlr scope, designed to win resolution against an internally-named supabase-db dependency.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

0feb7f8ea3069b0e830043fea195c088ea28709cc18a32676f389c61a15fc84c

53be32c0aa3aa96a1a587e4ff7f380c2b030d3bba6bcbdf1100876ccda7da24a

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @0xlr/supabase-db (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @0xlr/supabase-db across your stack and pipelines.
If you installed it — respond
@0xlr/supabase-db is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @0xlr/supabase-db was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @0xlr/supabase-db before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @0xlr/supabase-db 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-004967IN-MAL-2026-004968

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @0xlr/supabase-db-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring