Which versions of @quantixfinance/supabase are malicious?

The following npm versions of @quantixfinance/supabase are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @quantixfinance/supabase if I installed it?

@quantixfinance/supabase 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 @quantixfinance/supabase — how do I know if it already compromised me?

If @quantixfinance/supabase 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 @quantixfinance/supabase part of a known attack campaign?

Yes — @quantixfinance/supabase is associated with the IN-MAL-2026-019365 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 @quantixfinance/supabase 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 @quantixfinance/supabase (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @quantixfinance/supabase across your stack and pipelines.

Malicious package

@quantixfinance/supabasenpm

@quantixfinance/supabase is a confirmed malicious npm package (MAL-2026-15853) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @quantixfinance/supabase (npm)

MAL-2026-15853

Immediate action

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

npm uninstall @quantixfinance/supabase

What this malware does

The package's preinstall lifecycle script enumerates process.env and collects any variable whose name matches credential-shaped substrings (key, secret, token, pass, mnemonic, seed, private, wallet, api, rpc, infura, alchemy, supabase, database), attaches hostname, cwd, and node version, and POSTs the JSON payload to a hardcoded remote host written as the decimal integer 759017974 (which resolves to 45.63.10.182) on port 61289. The integer form of the destination host defeats plain-text IOC scanning. The package's index.js is a non-functional stub that exports a no-op createClient returning empty results, confirming the library body is cover and the package exists solely to run the install-time credential stealer. The scoped name resembles a private/internal organization scope, consistent with a dependency-confusion delivery shape.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

957f7218e15bdaaead1d170d28c2b67949c808b52985e36ec2f993573af1312f

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 @quantixfinance/supabase (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @quantixfinance/supabase across your stack and pipelines.
If you installed it — respond
@quantixfinance/supabase 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 @quantixfinance/supabase 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 @quantixfinance/supabase 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. @quantixfinance/supabase on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019365

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @quantixfinance/supabase-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

Explore

All malware advisories How O3 detects malware Vulnerability database