MAL-2026-4704 Malicious code in veteran-proxy (npm)
Malicious package
Published
MAL-2026-4704 is a malicious package: veteran-proxy (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-4704/ (Markdown: https://insights.sbomify.com/MAL-2026-4704/index.md)
- Package
- veteran-proxy
- Registry
- npm
What is MAL-2026-4704?
MAL-2026-4704 is a malicious package in veteran-proxy, published on 21 May 2026.
Official description
On
npm install, the postinstall hook (node install.js) downloads a platform-specific binary archive from a hardcoded https://your-website.com/downloads/veteran/... URL, extracts it, chmods it 0755, and immediately executes it (execSync("${BIN_PATH}" version)). The README advertises that binaries come from GitHub Releases at github.com/yongjie0203/veteran/releases, but the install script hardcodes your-website.com with a Chinese-language comment instructing the maintainer to replace it with their real download host — the package was published to npm with the placeholder in place. There is no hash or signature verification of the fetched bytes. Whoever registers or already controls your-website.com can ship arbitrary executables to every installer of this package, with full code execution on the installer's machine. Even absent registered malicious intent today, the install path is undefined: the destination domain is not under the publisher's control, the URL is unpinned, and the fetched binary's purpose (advertised as a SOCKS5 proxy) cannot be verified.What should I do about MAL-2026-4704?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.