Which versions of npm-module-service are malicious?

The following npm versions of npm-module-service are flagged malicious: 3.7.2. Treat any of these as compromised.

How do I remediate npm-module-service if I installed it?

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

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

Yes — npm-module-service is associated with the IN-MAL-2026-014863, RLMA-2026-10766 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 npm-module-service across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for npm-module-service (version 3.7.2).

Malicious package

npm-module-servicenpm

Advisory published Aug 5, 2026Updated Sep 24, 2026

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

Malicious code in npm-module-service (npm)

MAL-2026-12404

Immediate action

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

npm uninstall npm-module-service

What this malware does

The default export getPlugin in index.js performs an HTTPS request to the hardcoded bare-IP endpoint https://46.183.25.232:45000/icons/107 and passes the returned data.credits field to a Function constructor invoked with require, module, process, Buffer, and Promise bound in scope. Any consumer that imports and calls the module executes attacker-supplied JavaScript with full Node.js privileges on the installer's host. The URL is assembled from separated protocol/domain/path variables, and identifiers such as iconDomain, font-awesome, cdnjs, and bearrtoken, together with a decoy setDefaultModule function, present the module as a CDN icon helper while the actual network target is an unauthenticated bare-IP host unrelated to any CDN.

Malicious versions

1 flagged

3.7.2

Indicators of compromise (SHA-256)

8000a7baeda176481fd23b624485b3e419d6bed7f954900229de069c8ec4e026

d4e4093ceb644548a685efa3d647dae0d3a17db50d40ffd6da9a7b95dda51b69

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-014863RLMA-2026-10766

References

npmjs.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks npm-module-service-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