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

libffi-devnpm

libffi-dev is a confirmed malicious npm package (MAL-2025-4843) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in libffi-dev (npm)

MAL-2025-4843
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall libffi-dev

What this malware does

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.

This advisory concerns a malicious npm package named libffi-dev. It is not related to the upstream C library libffi nor distro development packages named libffi-dev shipped by Debian, Ubuntu, Alpine, etc.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

8a906bee35ae351e1925f8e50b6060ecae77896f7f3ceb459f1218bfa3df15fc
24526fbf539d4c1c75fd80d2858984316a86e5b5a5a3d51db5185639e6dbe463
214a71dbf223c356b8305beaea8aff72606ac373a1459ca4388482ff6bc07139
570b28ff882e484be3a59b834348694d7d3f5ec0f6e5aa712640fb0336ec6a88

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

  2. If you installed it — respond

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

Campaign

GHSA-2p54-33x3-2mcfRLMA-2025-03297RLUA-2025-03903

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks libffi-dev-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

libffi-dev (npm) malicious package — MAL-2025-4843 | O3 Security