Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@webapp-shared/login-vmoknpm

Advisory published Updated

@webapp-shared/login-vmok is a confirmed malicious npm package (MAL-2026-18356) that opens a backdoor for remote access (malicious versions 1.0.0, 1.0.1, 1.1.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @webapp-shared/login-vmok (npm)

MAL-2026-18356
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @webapp-shared/login-vmok

What this malware does

@webapp-shared/login-vmok is a dependency-confusion package: it uses the @webapp-shared scope, which matches a private internal package scope, and was published on 2026-10-27 in versions 1.0.0, 1.0.1, 1.1.0, 2.0.1, 3.0.0 and 99.0.1 so that builds resolving the internal name from the public registry install it instead. Its postinstall script runs node beacon.cjs, which sends an HTTP POST over cleartext HTTP to the hardcoded IP endpoint http://13.140.137.222:8787/_ah/dc with the package name, the machine's hostname, the install directory, the current working directory and the Node.js version; the entry point index.js sends the same request again whenever the package is loaded and otherwise has no functionality. The beacon code is the same as in other dependency-confusion packages sending to http://185.158.107.175:8787/_ah/dc (e.g. MAL-2026-18276), with only the endpoint and package name changed. The inert 0.0.0-stage and 0.1.0 placeholder versions carry no install script and are not affected. Any machine that installed an affected version has disclosed its hostname and filesystem layout to a third party; remove the package, pin or scope internal package names to the internal registry, and block 13.140.137.222 on build hosts.

Malicious versions

6 flagged
1.0.01.0.11.1.02.0.13.0.099.0.1

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for @webapp-shared/login-vmok (6 malicious versions).

  2. If you installed it — respond

    @webapp-shared/login-vmok establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If @webapp-shared/login-vmok 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

No. @webapp-shared/login-vmok on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.1.0, 2.0.1, 3.0.0, 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Robin Frehner, Protet · finder

Detect & block this

O3 blocks @webapp-shared/login-vmok-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore