Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2022-23812: Destructive malicious code in node-ipc

Published Mar 16, 2022 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS4.2%91st percentile
CISA KEVNoNot listed
In the wildReported3 exploitation records in Mallory
Vendor
Node-Ipc Project
IdentifiersCVE-2022-23812CWE-506

CVE-2022-23812 concerns intentionally introduced malicious code in the npm package node-ipc versions 10.1.1 and 10.1.2. The maintainer-added payload schedules an outbound IP-geolocation lookup and, when the returned country identifies Russia or Belarus, recursively traverses directories and overwrites accessible file contents with a heart emoji. A randomized execution gate means the destructive routine does not proceed on every execution. Version 10.1.3 removed the destructive payload, but some subsequent releases introduced separate potentially unwanted behavior through the peacenotwar dependency. The credential-theft campaign involving node-ipc releases in May 2026 is a distinct incident.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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

Successful execution destroys the original contents of files writable by the process running the malicious dependency. Recursive traversal can extend beyond the application's working directory, potentially corrupting application files and other accessible data and disrupting dependent applications or workflows. The extent of damage depends on filesystem access permissions and the files encountered. This CVE's destructive payload does not establish credential theft or data exfiltration.

Mitigation

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

Avoid node-ipc where feasible or constrain dependency resolution to reviewed, known-good versions, including transitive dependencies. Use lockfiles and controlled dependency updates to prevent unexpected package changes. Restrict dependency execution environments' filesystem write access to limit the destructive payload's reach. Disabling npm lifecycle scripts alone does not prevent malicious dependency code from executing when loaded.

Remediation

Patch, then assume compromise.

Remove node-ipc versions 10.1.1 and 10.1.2 from direct and transitive dependencies and pin a reviewed, known-good replacement. Version 10.1.3 removed the destructive payload; however, upgrading indiscriminately to later releases is inappropriate because versions 9.2.2, 11.0.0, and 11.1.0 introduced peacenotwar-related behavior. For affected Vue.js CLI deployments, fixes addressing the node-ipc 9.2.2 dependency issue were released in versions 4.5.16 and 5.0.3. Dependency replacement does not recover overwritten file contents.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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
FAQ

Frequently asked questions

Is CVE-2022-23812 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2022-23812?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2022-23812.
Is there a patch for CVE-2022-23812?
Remove node-ipc versions 10.1.1 and 10.1.2 from direct and transitive dependencies and pin a reviewed, known-good replacement. Version 10.1.3 removed the destructive payload; however, upgrading indiscriminately to later releases is inappropriate because versions 9.2.2, 11.0.0, and 11.1.0 introduced peacenotwar-related behavior.
What products are affected by CVE-2022-23812?
Node-Ipc Project Node-Ipc.
How severe is CVE-2022-23812?
CVE-2022-23812 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 4.2% (91st percentile) as of Oct 16, 2026.
Activity feed

Recent activity

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

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence1Every report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.