Which versions of studiocode_eligibility are malicious?

The following npm versions of studiocode_eligibility are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate studiocode_eligibility if I installed it?

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

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

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

Search your lockfiles and build artifacts for studiocode_eligibility (version 1.0.1).

Malicious package

studiocode_eligibilitynpm

Advisory published Oct 4, 2026Updated Oct 4, 2026

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

Malicious code in studiocode_eligibility (npm)

MAL-2026-17522

Immediate action

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

npm uninstall studiocode_eligibility

What this malware does

package.json declares a postinstall hook wscript.exe 4444.vbs that automatically executes a 765KB VBScript shipped in the tarball on Windows installers. The VBS contains multi-layer obfuscation (XOR-decoded AES S-boxes, SHA-256 constants, a ChaCha20 stream layer, and a large Base64 'ArtifactBundleHX' blob) that decrypts a PowerShell loader, writes it to %TEMP%\pf#####.dat, and invokes it via powershell.exe using process-hollowing-style techniques. The library source (src/index.js) is a small Zod-based email-domain eligibility checker that is unrelated to the VBS payload and serves as cover. The README explicitly claims 'Checks run locally, without network requests' and 'There are no installation scripts', directly contradicting the declared postinstall hook and shipped dropper. Running npm install studiocode_eligibility on Windows grants the package author arbitrary code execution on the installer's machine.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

a49b1af8bbf0463bb38d3049e59c28b0dcc8d2e3e5ef54611b4e77bddfdd36dc

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-020956

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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