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?

npm-module-service is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed npm-module-service — how do I know if it already compromised me?

If npm-module-service was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is npm-module-service part of a known attack campaign?

Yes — npm-module-service is associated with the IN-MAL-2026-014863 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for npm-module-service (version 3.7.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging npm-module-service across your stack and pipelines.

Malicious package

npm-module-servicenpm

npm-module-service is a confirmed malicious npm package (MAL-2026-12404) that steals credentials and exfiltrates sensitive data (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

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for npm-module-service (version 3.7.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging npm-module-service across your stack and pipelines.
If you installed it — respond
npm-module-service is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If npm-module-service was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks npm-module-service before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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-014863

References

npmjs.com

Credits

Amazon Inspector · 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 credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database