Which versions of syncora are malicious?

The following npm versions of syncora are flagged malicious: 0.2.0. Treat any of these as compromised.

How do I remediate syncora if I installed it?

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

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

Yes — syncora is associated with the GHSA-2xgm-25c8-fggh, IN-MAL-2026-008791 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 syncora 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 syncora (version 0.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging syncora across your stack and pipelines.

Malicious package

syncoranpm

syncora is a confirmed malicious npm package (MAL-2026-6884) that executes malicious code on install (malicious version 0.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in syncora (npm)

MAL-2026-6884

Immediate action

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

npm uninstall syncora

What this malware does

The package was found to contain malicious code or consuming dependency that contains 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.

Malicious versions

1 flagged

0.2.0

Indicators of compromise (SHA-256)

e1489d873dca6f208aac743dcf3aad7f55efd704c6980bf9fba68019054e0092

fad6a402b2081c7bd35f082e81588979985d9e4b458e0a34794e50f4acc14fd7

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

Campaign

GHSA-2xgm-25c8-fgghIN-MAL-2026-008791

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks syncora-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