Which versions of separadordeinfo are malicious?

The following npm versions of separadordeinfo are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate separadordeinfo if I installed it?

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

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

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

Search your lockfiles and build artifacts for separadordeinfo (version 1.0.0).

Malicious package

separadordeinfonpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

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

Malicious code in separadordeinfo (npm)

MAL-2026-2800

Immediate action

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

npm uninstall separadordeinfo

What this malware does

The package separadordeinfo was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

8e15a0fa8035769a270e736b06fb91cb1a4c01a346f19aab388722dfe21442ab

21e2d6619a0d8333edc7c42d4fd1c6b03822b68469735f3ae6bf4afafefce398

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02039

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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