Which versions of vue-compiler-sfc-plugin are malicious?

The following npm versions of vue-compiler-sfc-plugin are flagged malicious: 3.5.25, 3.5.26. Treat any of these as compromised.

How do I remediate vue-compiler-sfc-plugin if I installed it?

vue-compiler-sfc-plugin 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 vue-compiler-sfc-plugin — how do I know if it already compromised me?

If vue-compiler-sfc-plugin 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 vue-compiler-sfc-plugin part of a known attack campaign?

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

Malicious package

vue-compiler-sfc-pluginnpm

Malicious code in vue-compiler-sfc-plugin (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4707

Immediate action

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

npm uninstall vue-compiler-sfc-plugin

What this malware does

Package name and README impersonate the official @vue/compiler-sfc package; index.js merely re-exports it. The npm postinstall hook runs postinstall-run.cjs which invokes tooling-bootstrap.cjs. tooling-bootstrap.cjs concatenates a fragmented base64 array (BOOTSTRAP_B64), decodes it, writes the resulting JS to ~/.gradle/daemon/tooling-api-runtime.mjs (a Gradle-daemon cover name), and detached-spawns it with the user's node binary (spawn(nodeBin, args, { detached: true, stdio: 'ignore', windowsHide: true }); child.unref()). Activation is gated by victim-project sentinels (ALLOWED_PROJECT_SENTINELS includes 'src/businessCom/BLinker.vue' and 'src/api/gameCategorie.js'), so the RAT only deploys inside the intended victim's repo — evading sandboxed install scanners. The decoded payload is a long-running C2 agent that POSTs hostname, OS user, and OS info to https://npmjs.it.com/api/register, persists an agent id at /.gradle-cache/.aid, polls https://npmjs.it.com/api/task/<agent>, and dispatches operator-issued ops: exec (spawn /bin/sh or cmd.exe with attacker-supplied command), ls, download (read arbitrary path and POST bytes to /api/file/<agent>/<task>), upload (write attacker-supplied base64 to arbitrary path), delete (fs.rmSync), move, ps. C2 defaults to https://npmjs.it.com/ (a typosquat of npmjs.com) and TLS verification can be disabled via C2_TLS_INSECURE. This is a fully-featured backdoor enabling credential theft (/.aws, ~/.ssh,.env,.npmrc), arbitrary code execution, and persistent remote control of any machine where install hits the targeted project.

Malicious versions

2 flagged

3.5.253.5.26

Indicators of compromise (SHA-256)

c320320435358c109567ef3776ced079a2196b831b583b66c87323ddf402bae9

ccae84b1e69608b53868c4776df642dd816aa47b9110e8958aa03fcb6899f5e8

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

Campaign

IN-MAL-2026-004696IN-MAL-2026-004915

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks vue-compiler-sfc-plugin-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