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?

Remove @0xlr/supabase-db 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/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.

Can O3 Security detect @0xlr/supabase-db 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/supabase-db and packages like it before any post-install script runs.

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

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

Scan your dependencies

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

Supply-chain protection