Which versions of citrea-bridge are malicious?

The following npm versions of citrea-bridge are flagged malicious: 2.0.0. Treat any of these as compromised.

How do I remediate citrea-bridge if I installed it?

Remove citrea-bridge 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 citrea-bridge — how do I know if it already compromised me?

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

Yes — citrea-bridge is associated with the GHSA-jh4j-2cx5-78p2 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 citrea-bridge 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 citrea-bridge (version 2.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging citrea-bridge across your stack and pipelines.

Malicious package

citrea-bridgenpm

Malicious code in citrea-bridge (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3820

Immediate action

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

npm uninstall citrea-bridge

What this malware does

The package citrea-bridge was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified 'citrea-bridge' @ 2.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

2.0.0

Indicators of compromise (SHA-256)

08b6ea48da9888306f5c3fdb716f4e68792ee8d828a2cbff78cbc5ed1bc348a6

abffe603b7967ca2d5e19b9daed6989d966c78d638b7367a926ef2d9fa9e6997

23fdd6beb009e7afba647c12314e567a8c1bc2be715524724645820fc6239852

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

Campaign

GHSA-jh4j-2cx5-78p2

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks citrea-bridge-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