Which versions of francium-utils are malicious?

The following npm versions of francium-utils are flagged malicious: 1.0.0, 99.99.9. Treat any of these as compromised.

How do I remediate francium-utils if I installed it?

Remove francium-utils 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.

I already installed francium-utils — how do I know if it already compromised me?

If francium-utils 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.

Is francium-utils part of a known attack campaign?

Yes — francium-utils is associated with the GHSA-45m3-pf6h-c243, RLMA-2026-01328 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find francium-utils across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for francium-utils (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-utils across your stack and pipelines.

Malicious package

francium-utilsnpm

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

MAL-2026-242

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall francium-utils

What this malware does

The package francium-utils 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)

36e968a97c914ae6c1bf4fb980564d69546cc92105d1be341f56c933ec2caa12

7bbfe7cfa0e201004579dc73a60307dbd93e6507801d3dd767b689cb748535c1

47413858684529ed7e42326e9b63a2fecb04140c4568ff4416defc3936ced548

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for francium-utils (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-utils across your stack and pipelines.
If you installed it — respond
Remove francium-utils 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.
Did it already run?
If francium-utils 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.
How O3 protects you
O3 blocks francium-utils 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-utils 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-45m3-pf6h-c243RLMA-2026-01328

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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

Malware detection Runtime egress monitoring