Which versions of vscode-designer-14 are malicious?

The following npm versions of vscode-designer-14 are flagged malicious: 14.0.1. Treat any of these as compromised.

How do I remediate vscode-designer-14 if I installed it?

vscode-designer-14 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 vscode-designer-14 — how do I know if it already compromised me?

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

Yes — vscode-designer-14 is associated with the IN-MAL-2026-014831 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 vscode-designer-14 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 vscode-designer-14 (version 14.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vscode-designer-14 across your stack and pipelines.

Malicious package

vscode-designer-14npm

vscode-designer-14 is a confirmed malicious npm package (MAL-2026-12497) that steals credentials and exfiltrates sensitive data (malicious version 14.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vscode-designer-14 (npm)

MAL-2026-12497

Immediate action

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

npm uninstall vscode-designer-14

What this malware does

package.json declares a preinstall hook that runs index.js on npm install. index.js collects the installer's hostname, username, home directory, DNS server configuration, package metadata, and the contents of /etc/passwd and /etc/hosts, then POSTs the collected data over HTTPS to the hardcoded host slh4v8u1tz6gjo447tgf9rl3xu3mrcf1.oastify.com (a Burp Collaborator OAST subdomain). The package has no legitimate functionality that would justify reading local system files or beaconing host identifiers to an out-of-band interaction service; the shape matches a dependency-confusion / typosquat exfiltration beacon.

Malicious versions

1 flagged

14.0.1

Indicators of compromise (SHA-256)

dcf384e12e957c8d6b3d0014504f652cd2b6f3885f49820a2907865566bb6137

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 vscode-designer-14 (version 14.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vscode-designer-14 across your stack and pipelines.
If you installed it — respond
vscode-designer-14 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 vscode-designer-14 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 vscode-designer-14 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. vscode-designer-14 on npm has been identified as a malicious package (version 14.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014831

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks vscode-designer-14-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