Which versions of securefiles-common are malicious?

The following npm versions of securefiles-common are flagged malicious: 1.0.1, 1.0.3. Treat any of these as compromised.

How do I remediate securefiles-common if I installed it?

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

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

Yes — securefiles-common is associated with the RLMA-2026-01814 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 securefiles-common across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for securefiles-common (2 malicious versions).

Malicious package

securefiles-commonnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

securefiles-common is a confirmed malicious npm package (MAL-2026-2387) that executes malicious code on install (malicious versions 1.0.1, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in securefiles-common (npm)

MAL-2026-2387

Immediate action

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

npm uninstall securefiles-common

What this malware does

The package securefiles-common was found to contain malicious code.

Malicious versions

2 flagged

1.0.11.0.3

Indicators of compromise (SHA-256)

ae644d6550fc4a4d998b3abe5c550db6e8a3439665bf33503aa33465cbe971cc

9e6eb158a4a31560fd7d020c4644db9f8795bf0049b5e15a5ab5cccea05e68ee

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for securefiles-common (2 malicious versions).
If you installed it — respond
Remove securefiles-common 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 securefiles-common 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. securefiles-common on npm has been identified as a malicious package (versions 1.0.1, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01814

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks securefiles-common-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