Which versions of hast-util-to-mdast9 are malicious?

The following npm versions of hast-util-to-mdast9 are flagged malicious: 9.0.0. Treat any of these as compromised.

How do I remediate hast-util-to-mdast9 if I installed it?

Remove hast-util-to-mdast9 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 hast-util-to-mdast9 — how do I know if it already compromised me?

If hast-util-to-mdast9 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 hast-util-to-mdast9 part of a known attack campaign?

Yes — hast-util-to-mdast9 is associated with the GHSA-28w3-67mg-fxwj 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 hast-util-to-mdast9 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 hast-util-to-mdast9 (version 9.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hast-util-to-mdast9 across your stack and pipelines.

Malicious package

hast-util-to-mdast9npm

Malicious code in hast-util-to-mdast9 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192244

Immediate action

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

npm uninstall hast-util-to-mdast9

What this malware does

The package hast-util-to-mdast9 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 'hast-util-to-mdast9' @ 9.0.0 (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

1 flagged

9.0.0

Indicators of compromise (SHA-256)

fabf8dc58c17b065c6576e16228fa6dbe32f4944b01419821880c59edb28d012

f30c503e303a14ae873617a49a5055604ccdd16daaa5386b1e0f8a0d5208ea58

ef08c9391950720be5b9c3a3d6c0dae067e29884f6990b0734b0906fdbc4e7af

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 hast-util-to-mdast9 (version 9.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hast-util-to-mdast9 across your stack and pipelines.
If you installed it — respond
Remove hast-util-to-mdast9 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 hast-util-to-mdast9 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 hast-util-to-mdast9 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. hast-util-to-mdast9 on npm has been identified as a malicious package (version 9.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-28w3-67mg-fxwj

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks hast-util-to-mdast9-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