Which versions of alinet-w are malicious?

Every published version of alinet-w on npm is considered malicious. Remove the package entirely.

How do I remediate alinet-w if I installed it?

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

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

Yes — alinet-w is associated with the GHSA-394g-wvjv-j6mg 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 alinet-w across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for alinet-w (all published versions).

Malicious package

alinet-wnpm

Advisory published Mar 10, 2026Updated Mar 23, 2026

alinet-w is a confirmed malicious npm package (MAL-2026-1319) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in alinet-w (npm)

MAL-2026-1319

Immediate action

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

npm uninstall alinet-w

What this malware does

Package is malware due to ransomware-like behavior: file encryption, key exfiltration, terminal locking, ransom note, and persistence attempts.

The package alinet-w 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

9588a7d4915394fe3597930ad8e373ffaf697fac1ce842311001c9f2e35be623

5c18fd7e3ffa16f370fa25fcc489c381958d8200bf01cd8bf3627c91301eb397

Detection & response playbook

Credential / info stealer

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

Campaign

GHSA-394g-wvjv-j6mg

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks alinet-w-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