Which versions of vite-vue-path-map are malicious?

The following npm versions of vite-vue-path-map are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate vite-vue-path-map if I installed it?

vite-vue-path-map establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed vite-vue-path-map — how do I know if it already compromised me?

If vite-vue-path-map 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 vite-vue-path-map part of a known attack campaign?

Yes — vite-vue-path-map is associated with the IN-MAL-2026-016771, IN-MAL-2026-016772, IN-MAL-2026-016770 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 vite-vue-path-map 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 vite-vue-path-map (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vite-vue-path-map across your stack and pipelines.

Malicious package

vite-vue-path-mapnpm

vite-vue-path-map is a confirmed malicious npm package (MAL-2026-13465) that opens a backdoor for remote access (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vite-vue-path-map (npm)

MAL-2026-13465

Immediate action

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

npm uninstall vite-vue-path-map

What this malware does

The package is advertised as a Vite plugin that generates a local pathInfo.json map, but its generateBundle hook appends obfuscated JavaScript to the largest/entry JS chunk of the developer's build when a hidden MD5 license check (global['gva-project-name'] vs global['gva-secret']) fails. The appended code is stored as base64 constants (G, v, O) decoded via atob() at runtime. On every page load of the resulting production site it creates an invisible 0x0 off-screen <img> whose src decodes to https://plugin.gin-vue-admin.com/api/shopImage/view?name=logo.svg, sending a per-visitor beacon to an author-controlled domain. If that request fails or the server returns a non-image response, the onerror handler invokes document.open() and document.write() with a base64-decoded Chinese-language 'project unauthorized, contact WeChat shouzi_1994' HTML page, replacing the developer's application in every visitor's browser. The injection, beacon, and defacement behavior are not documented in the README and are activated at server-side discretion of the author's domain, giving whoever controls plugin.gin-vue-admin.com a remote switch to deface any site that shipped a build produced with this plugin.

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

33d9fb9d9144ca6d582b2cd92711169c1200b7dec8f5b63064d4f00cf0939ff6

40585ca03a579600693c4690e34a7cdee9e0d021d0699e96b91ad3162cf04e79

a6841df6c82f556057129d7bf3f23a6cccff9da407678d980875c5529e40caa9

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vite-vue-path-map (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vite-vue-path-map across your stack and pipelines.
If you installed it — respond
vite-vue-path-map establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If vite-vue-path-map 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 vite-vue-path-map 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. vite-vue-path-map on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016771IN-MAL-2026-016772IN-MAL-2026-016770

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks vite-vue-path-map-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database