Which versions of country-specialization are malicious?

The following npm versions of country-specialization are flagged malicious: 99.13.9. Treat any of these as compromised.

How do I remediate country-specialization if I installed it?

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

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

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

Search your lockfiles and build artifacts for country-specialization (version 99.13.9).

Malicious package

country-specializationnpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

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

Malicious code in country-specialization (npm)

MAL-2026-2752

Immediate action

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

npm uninstall country-specialization

What this malware does

The package country-specialization was found to contain malicious code.

Malicious versions

1 flagged

99.13.9

Indicators of compromise (SHA-256)

cfea14769c799622f60c382078265fc0f7daa18e8dce9cad3dad439fb4aeb802

2fc45c7299fe53b25a5d609d9a1207bf2b5f3b2a0ec54e30af13aeb3dba2e5f8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01931

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks country-specialization-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