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

@vreden-team/baileysnpm

Malicious code in @vreden-team/baileys (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190599
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @vreden-team/baileys

What this malware does

The package @vreden-team/baileys 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

4 flagged
7.7.87.7.97.8.07.8.1

Indicators of compromise (SHA-256)

e93a2ca0987843a93e09a99e78124ced3358731c00799ec1fc11906b80c55606
9fed39a318dda2a4b76dc12030fb47d54a1a1b36c7a8186f2eca1ae6bd908d23
64221cf21f59a621777bd861b08b0ad55c6ff84eb1a13a239beeb0f98190b462
0c11e7ad147fc0049d7763806fe9ae76bb43f960d1fcd34df3b6d9014db70629

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

  2. If you installed it — respond

    Remove @vreden-team/baileys 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 @vreden-team/baileys 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 @vreden-team/baileys 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. @vreden-team/baileys on npm has been identified as a malicious package (versions 7.7.8, 7.7.9, 7.8.0, 7.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rpmx-cvh3-2xqfRLMA-2025-05671RLUA-2025-06050

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @vreden-team/baileys-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.

@vreden-team/baileys (npm) malicious package — MAL-2025-190599 | O3 Security