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

web3-chain-syncnpm

Malicious code in web3-chain-sync (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-748
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall web3-chain-sync

What this malware does

The package web3-chain-sync 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

2 flagged
0.0.1-security2.4.3

Indicators of compromise (SHA-256)

a73489541e1d91e9e98d8ee52b10cc423ddd5b990bee23731cfa78e9bce3be00
e8092971594fb2e6c9a5748ec492ca88c9a8cc396917b314f09e5c3c85e0d130
6b9d75b3a3e300de6ef3c2107722d6b47b01db059504bf6538f16a74bff287bd

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 web3-chain-sync (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging web3-chain-sync across your stack and pipelines.

  2. If you installed it — respond

    Remove web3-chain-sync 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 web3-chain-sync 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 web3-chain-sync 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. web3-chain-sync on npm has been identified as a malicious package (versions 0.0.1-security, 2.4.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-p3xm-qpjg-2gg8RLMA-2026-01647

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks web3-chain-sync-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.

web3-chain-sync (npm) malicious package — MAL-2026-748 | O3 Security