Which versions of hops-preset-jest are malicious?

The following npm versions of hops-preset-jest are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate hops-preset-jest if I installed it?

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

If hops-preset-jest 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 hops-preset-jest part of a known attack campaign?

Yes — hops-preset-jest is associated with the GHSA-hgp2-cp4x-f69q 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 hops-preset-jest 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 hops-preset-jest (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hops-preset-jest across your stack and pipelines.

Malicious package

hops-preset-jestnpm

Malicious code in hops-preset-jest (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-908

Immediate action

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

npm uninstall hops-preset-jest

What this malware does

The package hops-preset-jest 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 'hops-preset-jest' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

6d87af0bf1ec496328e673a779d94a3dd4a6f9d8997b912d2cc4bddf7c392a66

8165500e6c415192d0b46d0e106f29fb3ae49fce7538b2da40a9e398998c087d

d1e4e88ca9b17e3778d9b7f4aa3d9cb2a94cc7ac234505750c84264eb43440d2

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

Campaign

GHSA-hgp2-cp4x-f69q

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks hops-preset-jest-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