Which versions of app-hsu-layer are malicious?

The following npm versions of app-hsu-layer are flagged malicious: 2.1.6, 2.1.7. Treat any of these as compromised.

How do I remediate app-hsu-layer if I installed it?

app-hsu-layer is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed app-hsu-layer — how do I know if it already compromised me?

If app-hsu-layer 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 app-hsu-layer part of a known attack campaign?

Yes — app-hsu-layer is associated with the IN-MAL-2026-015829, IN-MAL-2026-015830 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 app-hsu-layer 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 app-hsu-layer (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging app-hsu-layer across your stack and pipelines.

Malicious package

app-hsu-layernpm

app-hsu-layer is a confirmed malicious npm package (MAL-2026-13357) that steals credentials and exfiltrates sensitive data (malicious versions 2.1.6, 2.1.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in app-hsu-layer (npm)

MAL-2026-13357

Immediate action

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

npm uninstall app-hsu-layer

What this malware does

On npm install, the package's postinstall script runs test.js, which imports index.js and immediately invokes two harvesting/backdoor routines. The first routine recursively scans the current working directory for id.json, config.toml, Config.toml, env, and.env files and POSTs each match, tagged with the OS username, to http://95.216.118.146:3001/api/v1 — exfiltrating project secrets including Solana keypairs and API/database credentials. The second routine fetches attacker-controlled glob patterns from http://95.216.118.146:3001/api/scan-patterns and walks the user's home directory on Unix (or enumerates all logical drives via wmic/PowerShell on Windows), uploading matching files as multipart form-data to the same endpoint. In parallel, the postinstall fetches an SSH public key from http://95.216.118.146:3001/api/ssh-key, appends it to ~/.ssh/authorized_keys, runs sudo chown on ~/.ssh, and executes sudo ufw enable plus sudo ufw allow 22/tcp to guarantee inbound SSH reachability — granting the operator of 95.216.118.146 persistent remote shell access to the installing host. Package metadata is hollow (empty description/author, only test.js and index.js shipped) and function names (from_str_1, from_str_2) obscure intent.

Malicious versions

2 flagged

2.1.62.1.7

Indicators of compromise (SHA-256)

ad1ccd2bfbe4abd87e980067608328d6c0a6cb3d1145d8d8ff8d72a22667f00d

ccec10b777948fb3fcd849ce3741e0cd78bf46c23f037b8ab23ff6835acb6400

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for app-hsu-layer (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging app-hsu-layer across your stack and pipelines.
If you installed it — respond
app-hsu-layer is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If app-hsu-layer 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 app-hsu-layer 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. app-hsu-layer on npm has been identified as a malicious package (versions 2.1.6, 2.1.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015829IN-MAL-2026-015830

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks app-hsu-layer-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database