npm package report

Is body-parse-xml safe?

Confirmed malicious. Do not install it, and remove it where it has been installed.

Do not install this package

CRITICAL

malware. Confirmed 2025-08-14, OSV malicious-package feed (Google / OpenSSF).

// what we observed

The package body-parse-xml was found to contain malicious code.

mitre ttp: T1195.001

// versions and what to do

Malicious: all versions
Clean: none confirmed

Remove it from every machine and lockfile it reached. Treat any credentials, tokens and SSH keys present on those machines as exposed and rotate them. Check CI runners and container images that installed it.

npm uninstall body-parse-xml

OSV record

// reach

0 direct dependencies

none carry a known advisory

0 packages depend on it

an advisory here reaches each of them

Create a free accountfor every dependency path, dependent and what to upgrade

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

cvss

0.0

critical

severity band, no base score published

epss

not scored

chance of exploitation in 30 days

xyz score

0.0

medium

CyberXYZ composite out of 10

fig. 01 — GHSA-jcmh-9fvm-j39w, the advisory selected below

// 1 advisories

GHSA-jcmh-9fvm-j39w

CRITICAL

This package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.

// recommendation

Remove the package from your environment. There are no indications of further compromise.

// cvss v3.1 vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Checked 2026-10-04 at 01:09 UTC. The most recent advisory here was published 2020-09-03. Updated continuously from NVD, GHSA, OSV and CNA feeds.