@webapp-shared/login-vmok versions 1.0.0 to 99.0.1 on npm sent the computer name and folder paths to a hardcoded IP address on install.
The OpenSSF database lists the package as MAL-2026-18356. GitHub published malware advisory GHSA-hj92-8q8w-frh4 on 9 November 2026.
What happened
The account thekw11 published six bad versions of @webapp-shared/login-vmok on 27 October 2026.
- The OpenSSF record calls it a dependency-confusion package. The
@webapp-sharedscope matches a private internal package scope. - High version numbers such as
99.0.1make builds that resolve the internal name from the public registry pick this package. - A postinstall script runs
node beacon.cjs. - The script sends a POST to
http://13.140.137.222:8787/_ah/dcwith the package name, hostname, install directory, working directory and Node.js version. index.jssends the same beacon again when a program loads the package.
On 9 November 2026, npm set the latest tag to the holding package 0.0.1-security.
Affected versions
- The OpenSSF record names
1.0.0,1.0.1,1.1.0,2.0.1,3.0.0and99.0.1. - The OpenSSF record says
0.0.0-stageand0.1.0carry no install script and are not affected. - The GitHub advisory marks every version as affected (
>= 0) and lists no fixed version.
Indicators of compromise
- Network:
http://13.140.137.222:8787/_ah/dc beacon.cjssha2568a717c81e8754a677d6e22be57d9be0a508daf456154e14234ca4ecd2dc3908aindex.jssha256a86a4da763bbb34c16f361abe7aab66d5df591b66867ac8160041f932159b08d- 99.0.1 tarball sha1
738608ed58e02e9e4eda2259e70a879dfa314a7b
How to check
Run this in each project folder. Any version from 1.0.0 to 99.0.1 means the project installed a bad version.
npm ls @webapp-shared/login-vmok
Then search installed packages for the server address. The command only reads files.
grep -rln "13.140.137.222" node_modules
What to do now
- If a project lists the package, remove it and delete it from your lockfile.
- If your company uses the
@webapp-sharedscope internally, pin that scope to your private registry. - Block
13.140.137.222at your firewall or proxy and search your logs for it. - Treat any computer that installed the package as fully compromised, as the GitHub advisory states. Rotate every secret and key from a different computer.
What Vigilance would show
Vigilance checks each update before it installs. This is what a customer sees, rebuilt from the facts on this page.
On the computer, at install
Vigilance blocked `@webapp-shared/login-vmok` 1.0.1. This version is too new or changed in a way Vigilance must check first. The last safe version is 0.1.0. Install that version.
In the owner report
Bad update
@webapp-shared/login-vmok 1.0.1
This update now runs a command on its own when it is installed and downloads from the internet. The version before it did not.
- Ask the AI tool to swap @webapp-shared/login-vmok to 0.1.0. That is the last safe version.
Frequently asked questions
What is @webapp-shared/login-vmok?
It is an npm package that uses the name of a private internal package scope. Its bad versions send host details to 13.140.137.222 on install.
Which versions of @webapp-shared/login-vmok are malicious?
The OpenSSF record names 1.0.0, 1.0.1, 1.1.0, 2.0.1, 3.0.0 and 99.0.1. The GitHub advisory marks every version as affected.