Which versions of hubl-parser are malicious?

The following npm versions of hubl-parser are flagged malicious: 7.0.0. Treat any of these as compromised.

How do I remediate hubl-parser if I installed it?

Remove hubl-parser 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 hubl-parser — how do I know if it already compromised me?

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

Yes — hubl-parser is associated with the GHSA-8ppv-4gfx-6jq4 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 hubl-parser 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 hubl-parser (version 7.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hubl-parser across your stack and pipelines.

Malicious package

hubl-parsernpm

hubl-parser is a confirmed malicious npm package (MAL-2024-3) that executes malicious code on install (malicious version 7.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hubl-parser (npm)

MAL-2024-3

Immediate action

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

npm uninstall hubl-parser

What this malware does

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 'hubl-parser' @ 7.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

7.0.0

Indicators of compromise (SHA-256)

ad64ca4112c57ab0a0c7fcba10f396c6086e3511d7d792f7964a84dc7af7d958

c48b757cf4e86cc97abb28765fdf3f0a2205e99bbcf856ec3904b7e02038fea0

26e1f33bf240306094ea8c888bc2c8538211171b22e9adbb6e85715f28208e31

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

Campaign

GHSA-8ppv-4gfx-6jq4

References

github.com

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks hubl-parser-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

Explore

All malware advisories How O3 detects malware Vulnerability database