CriticalPublic exploit

Malicious code in node-ipc

IdentifiersCVE-2022-23812CWE-506

CVE-2022-23812 tracks a software supply-chain compromise/protestware incident in the npm package node-ipc. In affected versions 10.1.1 and 10.1.2, malicious code was intentionally added to the package source. The injected logic performs an outbound HTTPS request to an IP geolocation service, parses the returned country_name value, and checks whether the host appears to be located in Russia or Belarus. If the check matches, the code recursively traverses directories and overwrites files with a heart emoji, causing destructive data corruption. The provided code shows the malicious logic using Node.js fs, path, and https modules, delayed execution via setTimeout, and recursive filesystem enumeration before calling writeFile to replace file contents. The content also notes that from 11.0.0 onward, node-ipc no longer embedded the destructive logic directly, but instead imported the peacenotwar package, which introduced separate potentially undesired behavior. This CVE is associated with the 2022 destructive node-ipc incident, not the distinct 2026 credential-theft campaign discussed in the supporting context.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful triggering of the malicious logic can destroy user data by overwriting files with a heart emoji on systems geolocated to Russia or Belarus. Because node-ipc is a transitive dependency in the JavaScript ecosystem, the impact can propagate to downstream applications and developer environments that load the affected package, resulting in integrity loss of local files and potential disruption of development or runtime systems.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, pin node-ipc to a known-good version outside 10.1.1 and 10.1.2, regenerate lockfiles, and prevent installation of the malicious versions through registry policy, artifact allowlisting, or software composition controls. Review systems that executed the affected package for unexpected file corruption, especially on hosts geolocated to Russia or Belarus. Restrict unreviewed dependency updates and monitor for anomalous package behavior such as unexpected outbound network calls and filesystem writes during module load.

Remediation

Patch, then assume compromise.

Upgrade node-ipc to 10.1.3 or later and avoid the known malicious releases 10.1.1 and 10.1.2. Additionally, review dependency trees for transitive inclusion of affected node-ipc versions, remove deprecated or poisoned package versions from lockfiles and caches, and verify that downstream packages are pinned to known-good releases. Where relevant, also assess exposure to later node-ipc releases that introduced peacenotwar-based behavior separately from this CVE.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

Node-Ipc ProjectNode-Ipcapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

2 SOURCESView more in app

medium slowmistNews

May 16, 2026

Threat Intelligence | Analysis of the node-ipc Supply Chain Compromise and Poisoning Attack | by SlowMist | May, 2026 | Medium

A historical node-ipc supply chain poisoning incident from 2022 involving destructive behavior in malicious package versions 10.1.1 to 10.1.2. The article explicitly distinguishes it from the new 2026 credential-theft campaign.

snyk blogNews

Mar 16, 2022

Alert: peacenotwar module sabotages npm developers in the node-ipc package to protest the invasion of Ukraine | Snyk

A supply-chain sabotage vulnerability in the npm package node-ipc involving intentionally malicious/destructive behavior in certain versions, including file corruption/wiping and later protestware behavior via added dependencies.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity