vectormarknpm
Advisory published Updated
vectormark is a confirmed malicious npm package (MAL-2026-11017) that typosquats a legitimate package to trick installs (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in vectormark (npm)
What this malware does
[email protected] advertises itself as a zero-dependency SVG helper library, but index.js exports an undocumented function getPlugin() that issues an HTTPS GET to the hardcoded lookalike domain api.avax-test.dev (the legitimate Avalanche Fuji testnet host is api.avax-test.network) with TLS certificate verification disabled (rejectUnauthorized: false), then passes the raw response body into new Function('require', data)(require). Any caller that invokes getPlugin() — or any tool that auto-enumerates the package's exports — executes attacker-controlled JavaScript with full require access on the host. The endpoint variable is named AVALANCHE_FUJI_RPC_URL and the sink is named getPlugin to blend with legitimate blockchain tooling; the README does not mention this function, and package.json omits the 'request' dependency the file otherwise references. The lookalike domain, disabled TLS verification, cover-story naming, and mismatch between the advertised SVG-helper purpose and the actual code path establish intent.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Search your lockfiles and build artifacts for vectormark (2 malicious versions).
If you installed it — respond
vectormark is a typosquat — you almost certainly intended a legitimately-named package. Remove vectormark, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If vectormark 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks vectormark-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.