Which versions of supabase-js are malicious?

The following npm versions of supabase-js are flagged malicious: 1.0.0, 1.0.2, 1.0.4, 213.21.24. Treat any of these as compromised.

How do I remediate supabase-js if I installed it?

Remove supabase-js 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 activity or persistence.

I already installed supabase-js — how do I know if it already compromised me?

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

Yes — supabase-js is associated with the RLMA-2024-07380, GHSA-4rwr-4jcc-7p2f, RLUA-2026-01599 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 supabase-js 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 supabase-js (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging supabase-js across your stack and pipelines.

Malicious package

supabase-jsnpm

supabase-js is a confirmed malicious npm package (MAL-2024-9871) that executes malicious code on install (malicious versions 1.0.0, 1.0.2, 1.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in supabase-js (npm)

MAL-2024-9871

Immediate action

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

npm uninstall supabase-js

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

4 flagged

1.0.01.0.21.0.4213.21.24

Indicators of compromise (SHA-256)

edc414d58c8ea1df73cf24fd47bf4b61cff71ab8691b1bceb8700c08714f98c2

1b78f378246a539beb5412842ab5c310cac8566237afbc3ecb3535f85ca74b5b

7ee566cc71a21cd288867c97188e1f0a2e229cfc6db426ea4f51154cc5a4cfc5

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for supabase-js (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging supabase-js across your stack and pipelines.
If you installed it — respond
Remove supabase-js 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 activity or persistence.
Did it already run?
If supabase-js 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 supabase-js 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. supabase-js on npm has been identified as a malicious package (versions 1.0.0, 1.0.2, 1.0.4, 213.21.24 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-07380GHSA-4rwr-4jcc-7p2fRLUA-2026-01599

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks supabase-js-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database