Which versions of vectormark are malicious?

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

How do I remediate vectormark if I installed it?

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.

I already installed vectormark — how do I know if it already compromised me?

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

Yes — vectormark is associated with the GHSA-g48p-2cr5-5hm2, IN-MAL-2026-011148, IN-MAL-2026-011216 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 vectormark 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 vectormark (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vectormark across your stack and pipelines.

Malicious package

vectormarknpm

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)

MAL-2026-11017

Immediate action

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

npm uninstall vectormark

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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

966fb5c08bb39dca42e48787fab3b7c14e38afc4ae209f5cd6231acc10d05c72

3fa85f8a110d2401a7762a729526de6d338ac4a6a9aa0e896eb7b7acb9560cbe

6d0646473c841676e2f55d66494a805943e00b2e2d7515e1bbba5453e6a9024e

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vectormark (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vectormark across your stack and pipelines.
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 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 vectormark 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. vectormark on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-g48p-2cr5-5hm2IN-MAL-2026-011148IN-MAL-2026-011216

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database