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

vg-interaction-modelnpm

Malicious code in vg-interaction-model (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5168
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall vg-interaction-model

What this malware does

The OpenSSF Package Analysis project identified 'vg-interaction-model' @ 40.0.1 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged
40.0.140.0.4

Indicators of compromise (SHA-256)

aba91a5b2aeb99e94b28109825a7ac069669d39c12c118fd37d9ef70afe63261
407173b2aee14360bfad38888d87727b81adef8528e3f63dd41520a6fd3ccabf

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vg-interaction-model (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vg-interaction-model across your stack and pipelines.

  2. If you installed it — respond

    Remove vg-interaction-model from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If vg-interaction-model 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.

  4. How O3 protects you

    O3 blocks vg-interaction-model 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. vg-interaction-model on npm has been identified as a malicious package (versions 40.0.1, 40.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks vg-interaction-model-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.

vg-interaction-model (npm) malicious package — MAL-2026-5168 | O3 Security