Which versions of hackpreinstall are malicious?

The following npm versions of hackpreinstall are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate hackpreinstall if I installed it?

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

If hackpreinstall was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is hackpreinstall part of a known attack campaign?

Yes — hackpreinstall is associated with the GHSA-34f9-x3r7-8wjj, RLMA-2026-01339, RLUA-2026-01770 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 hackpreinstall across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hackpreinstall (version 1.0.0).

Malicious package

hackpreinstallnpm

Advisory published Mar 3, 2026Updated Apr 1, 2026

hackpreinstall is a confirmed malicious npm package (MAL-2026-1149) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hackpreinstall (npm)

MAL-2026-1149

Immediate action

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

npm uninstall hackpreinstall

What this malware does

The package hackpreinstall 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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

75af598258a7a91741c032e5d4ae8deafd1d54d392cbc950c3e0b3da69936c7e

a33e3f8d27139e08c22f475145ed3748570d6aadbd5f194bb0cce5be5a93fbf5

2f9d2d6066e9e9221ab71b1234cfed7151316c117bfaa2a738bf675a2cac17a3

56ca6b524102ce8e35f5c0a2327def31e68cc4d7b01cb830c8665c4e3d81d306

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for hackpreinstall (version 1.0.0).
If you installed it — respond
Remove hackpreinstall 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 hackpreinstall was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. hackpreinstall 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-34f9-x3r7-8wjjRLMA-2026-01339RLUA-2026-01770

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks hackpreinstall-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