Which versions of focaleys are malicious?

The following npm versions of focaleys are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate focaleys if I installed it?

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

If focaleys was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is focaleys part of a known attack campaign?

Yes — focaleys is associated with the IN-MAL-2026-020814 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 focaleys across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for focaleys (version 1.1.0).

Malicious package

focaleysnpm

Advisory published Sep 30, 2026Updated Sep 30, 2026

focaleys is a confirmed malicious npm package (MAL-2026-17329) that executes malicious code on install (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in focaleys (npm)

MAL-2026-17329

Immediate action

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

npm uninstall focaleys

What this malware does

package.json declares the dependency 'libsignal' as 'github:rexxzyid/libsignal-node' with no tag, version, or commit SHA. On npm install, this resolves to whatever the default branch HEAD contains at that moment, with no integrity check, and any lifecycle scripts in the fetched repository execute on the installer's machine. Whoever controls the rexxzyid GitHub account controls code that runs at install time for every installer of focaleys, and the fetched code can change silently between installs without any change to focaleys itself.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

481093b5037c8aafc763d4543e5a6a39c2ebc7055673eb1d4f480f885593bcd2

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for focaleys (version 1.1.0).
If you installed it — respond
Remove focaleys 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 focaleys was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. focaleys on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020814

References

npmjs.com

Credits

Amazon Inspector · finder
OX Security · finder

Detect & block this

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