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

francium-web-visitorsnpm

Malicious code in francium-web-visitors (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-243
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall francium-web-visitors

What this malware does

The package francium-web-visitors 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
1.0.099.99.9

Indicators of compromise (SHA-256)

3a347695781bf1cc2015572ac6eb0d395158f5cf0b2272cd95144454a3325ad9
72629df67c0b81a1d120987aca534bd8096a0cbb2a9898a327a2dc2d1b8a0a49
76d0a2bc58445cee90f31aadee493c7590eeb7aaf42c1eb84fe897e048565337

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

  2. If you installed it — respond

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

Campaign

GHSA-5c69-2ppp-w4fvRLMA-2026-01329

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks francium-web-visitors-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.

francium-web-visitors (npm) malicious package — MAL-2026-243 | O3 Security