Which versions of remark-parse10 are malicious?

The following npm versions of remark-parse10 are flagged malicious: 10.0.0, 10.0.2. Treat any of these as compromised.

How do I remediate remark-parse10 if I installed it?

Remove remark-parse10 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed remark-parse10 — how do I know if it already compromised me?

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

Yes — remark-parse10 is associated with the GHSA-w4xv-3vpw-m3x5 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 remark-parse10 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 remark-parse10 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging remark-parse10 across your stack and pipelines.

Malicious package

remark-parse10npm

Malicious code in remark-parse10 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192246

Immediate action

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

npm uninstall remark-parse10

What this malware does

The package remark-parse10 was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'remark-parse10' @ 10.0.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

10.0.010.0.2

Indicators of compromise (SHA-256)

d8cd5885ca66abe264124578aa99aaeb2907923a26681d5b64e8d6b72cb72696

84306852bbfaa80196c0fdf7e4227b3f5b4dad54a05e1ba37b60a711bc1be39f

b0d37276c9efb7e85e07384bd19c0625e6672c70443710e145c260516f0ba2f4

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for remark-parse10 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging remark-parse10 across your stack and pipelines.
If you installed it — respond
Remove remark-parse10 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If remark-parse10 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 remark-parse10 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. remark-parse10 on npm has been identified as a malicious package (versions 10.0.0, 10.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-w4xv-3vpw-m3x5

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks remark-parse10-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring