Which versions of sessionfiy are malicious?

The following npm versions of sessionfiy are flagged malicious: 2.2.8. Treat any of these as compromised.

How do I remediate sessionfiy if I installed it?

Remove sessionfiy 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 sessionfiy — how do I know if it already compromised me?

If sessionfiy 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 sessionfiy part of a known attack campaign?

Yes — sessionfiy is associated with the RLMA-2025-05505, RLUA-2025-05944 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 sessionfiy 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 sessionfiy (version 2.2.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sessionfiy across your stack and pipelines.

Malicious package

sessionfiynpm

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

Malicious code in sessionfiy (npm)

MAL-2025-48865

Immediate action

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

npm uninstall sessionfiy

Malicious versions

1 flagged

2.2.8

Indicators of compromise (SHA-256)

2038a3b55639197809b55ae05c525d8b715325a862e6aa0d2b9d5ff774377611

48c4ef8e551402544a1c322430f2e88b403a7b6432943aacd55779bd338522b4

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 sessionfiy (version 2.2.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sessionfiy across your stack and pipelines.
If you installed it — respond
Remove sessionfiy 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 sessionfiy 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 sessionfiy 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. sessionfiy on npm has been identified as a malicious package (version 2.2.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05505RLUA-2025-05944

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks sessionfiy-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

Explore

All malware advisories How O3 detects malware Vulnerability database