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

@vietmoney/react-big-calendarnpm

Malicious code in @vietmoney/react-big-calendar (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192994
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @vietmoney/react-big-calendar

What this malware does

The package @vietmoney/react-big-calendar 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

3 flagged
0.26.00.26.10.26.2

Indicators of compromise (SHA-256)

f1b295b2e53ad5dedab8ab361358a3f4161bcd4329598dee16a3848ed353ce76
b38aebebed4a38e2464d8abb76fbda4a16d4cf03b372124ec3d069c63f6e79f2
92585ec3c63f1e9a8e3d2645274b746c99718c223dd5ca5c8bee7cf774192045

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 @vietmoney/react-big-calendar (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @vietmoney/react-big-calendar across your stack and pipelines.

  2. If you installed it — respond

    Remove @vietmoney/react-big-calendar 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 @vietmoney/react-big-calendar 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 @vietmoney/react-big-calendar 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. @vietmoney/react-big-calendar on npm has been identified as a malicious package (versions 0.26.0, 0.26.1, 0.26.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2w42-mjvc-7mgqRLMA-2026-01075

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @vietmoney/react-big-calendar-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.

@vietmoney/react-big-calendar (npm) malicious package — MAL-2025-192994 | O3 Security