Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

symphony-corenpm

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

Malicious code in symphony-core (npm)

MAL-2026-2608
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall symphony-core

What this malware does

The package symphony-core 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.

Malicious versions

1 flagged
99.9.0

Indicators of compromise (SHA-256)

5c6f5ab5486f9ad46cd864ccf677494724eb5cddafcda7be2300f61dc5b2257a
043c1edf6e1236518709ec4cecd320367fba8de6f3b1ccc52038ada2c08abcb8
df4b3d8e4ef2e132b4ca06b900ad0eecb2505a9f2cc5fe123b8746a9014fb4f4

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for symphony-core (version 99.9.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging symphony-core across your stack and pipelines.

  2. If you installed it — respond

    Remove symphony-core 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.

  3. Did it already run?

    If symphony-core 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.

  4. How O3 protects you

    O3 blocks symphony-core 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. symphony-core on npm has been identified as a malicious package (version 99.9.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6vc2-8rcw-cxg8RLMA-2026-05329

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks symphony-core-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.

Explore

symphony-core (npm) malicious package — MAL-2026-2608 | O3 Security