Which versions of hs-framework are malicious?

The following npm versions of hs-framework are flagged malicious: 999.9.1, 999.9.2. Treat any of these as compromised.

How do I remediate hs-framework if I installed it?

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

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

Yes — hs-framework is associated with the IN-MAL-2026-022473, IN-MAL-2026-022472 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 hs-framework across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hs-framework (2 malicious versions).

Malicious package

hs-frameworknpm

Advisory published Nov 1, 2026Updated Nov 1, 2026

hs-framework is a confirmed malicious npm package (MAL-2026-18434) that executes malicious code on install (malicious versions 999.9.1, 999.9.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hs-framework (npm)

MAL-2026-18434

Immediate action

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

npm uninstall hs-framework

What this malware does

package.json declares its sole dependency ltidisafe as a direct HTTPS tarball URL (https://storage.googleapis.com/lscunpentest/pack_ux_foundry.tgz) instead of a registry version range. On npm install, npm fetches whatever bytes are currently at that URL and installs them into the dependency tree, running any lifecycle scripts the fetched tarball contains, with no version pin and no integrity hash. Whoever controls the bucket controls code that executes on the installer's machine, and the bytes can change at any time without any change to this package. The shipped source is a one-line stub, so the manifest line is the entire published surface of the package. The bucket path segment lscunpentest is also consistent with penetration-testing / unauthorized-testing framing.

Malicious versions

2 flagged

999.9.1999.9.2

Indicators of compromise (SHA-256)

2950f0dff0145db43d5dd123c45c2786c7d42f58e7dec69e0178ca2aa325c478

e5b7694b77d2d36e84ffb82cbdf486244b673b29d8905ae7226022e58ea3bfb7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for hs-framework (2 malicious versions).
If you installed it — respond
Remove hs-framework 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 hs-framework 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. hs-framework on npm has been identified as a malicious package (versions 999.9.1, 999.9.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022473IN-MAL-2026-022472

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks hs-framework-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