Which versions of compliancepolicyserv are malicious?

The following npm versions of compliancepolicyserv are flagged malicious: 9.9.11. Treat any of these as compromised.

How do I remediate compliancepolicyserv if I installed it?

compliancepolicyserv establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed compliancepolicyserv — how do I know if it already compromised me?

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

Yes — compliancepolicyserv is associated with the IN-MAL-2026-010272 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 compliancepolicyserv across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for compliancepolicyserv (version 9.9.11).

Malicious package

compliancepolicyservnpm

Advisory published Jul 13, 2026Updated Jul 13, 2026

compliancepolicyserv is a confirmed malicious npm package (MAL-2026-10458) that opens a backdoor for remote access (malicious version 9.9.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in compliancepolicyserv (npm)

MAL-2026-10458

Immediate action

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

npm uninstall compliancepolicyserv

What this malware does

[email protected] registers index.js as both scripts.install and main. On npm install and on require, index.js loads lib/core.js, which reads os.userInfo().username, os.hostname(), and process.cwd(), concatenates them with a 'paypal' prefix, a timestamp, and the domain oob.sl4x0.xyz, and issues a dns.resolve4 query against the resulting subdomain, beaconing installer identifiers over DNS to an author-controlled domain. The destination host and the names of the os/dns/process APIs and their methods (userInfo, hostname, cwd, resolve4) are reconstructed at runtime from char-code arrays in lib/b02e30.js and lib/6ad264.js, hiding the exfil endpoint and sensitive API references from static inspection. The package name resembles a compliance-policy service but the shipped code performs no such function; the sole install/import-time effect is the DNS beacon.

Malicious versions

1 flagged

9.9.11

Indicators of compromise (SHA-256)

a9f18c11413e208ef48e083af8a065b36134c2b37b5fd1474a5701a986a659d8

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for compliancepolicyserv (version 9.9.11).
If you installed it — respond
compliancepolicyserv establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If compliancepolicyserv 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. compliancepolicyserv on npm has been identified as a malicious package (version 9.9.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010272

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks compliancepolicyserv-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database