Which versions of studiocode_tools are malicious?

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

How do I remediate studiocode_tools if I installed it?

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

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

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

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

Malicious package

studiocode_toolsnpm

Advisory published Oct 4, 2026Updated Oct 4, 2026

studiocode_tools is a confirmed malicious npm package (MAL-2026-17523) 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_tools (npm)

MAL-2026-17523

Immediate action

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

npm uninstall studiocode_tools

What this malware does

package.json declares a postinstall hook that runs wscript.exe 4444.vbs, auto-executing on npm install on Windows. The shipped 4444.vbs contains hand-rolled AES and ChaCha20 implementations with XOR-obfuscated S-boxes, SHA-256 round constants XORed with 0x5A5A5A5A, and hundreds of base64 ciphertext fragments (ArtifactBundleHX) that are reassembled and decrypted at runtime into a PowerShell loader. The script writes a payload file to %TEMP%\pfNNNNN.dat and invokes powershell.exe to perform process hollowing of the decrypted payload. The VBS carries cover-story branding as 'Verdant Signals Corp' / 'Device Telemetry Aggregator', and the README falsely states 'There are no installation scripts.' The multi-layer custom cryptography, false branding, and explicit README denial of install scripts are unambiguous indicators of hostile intent rather than legitimate functionality.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

261d413c0847b530c9a452c209c25e0a7d9123f9b0f20b26d0afcc41a929c74a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for studiocode_tools (version 1.0.1).
If you installed it — respond
Remove studiocode_tools 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_tools 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_tools 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-020957

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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