Which versions of user_migration are malicious?

The following npm versions of user_migration are flagged malicious: 9.99.9. Treat any of these as compromised.

How do I remediate user_migration if I installed it?

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

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

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

Search your lockfiles and build artifacts for user_migration (version 9.99.9).

Malicious package

user_migrationnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in user_migration (npm)

MAL-2026-1872

Immediate action

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

npm uninstall user_migration

What this malware does

The package user_migration was found to contain malicious code.

Malicious versions

1 flagged

9.99.9

Indicators of compromise (SHA-256)

7f93e2496734194de8ff6fc8257c074331b1aee97c6eb7d33459d8815a1364ef

6a952d55363362a942ec86eee421ffd30f1de7fbc2e9575ea1a37eaae9a73603

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01636

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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