What does the vg-interaction-model malware do?

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.

Which versions of vg-interaction-model are malicious?

The following npm versions of vg-interaction-model are flagged malicious: 40.0.1, 40.0.4. Treat any of these as compromised.

How do I remediate vg-interaction-model if I installed it?

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.

I already installed vg-interaction-model — how do I know if it already compromised me?

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

How do I find vg-interaction-model across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for vg-interaction-model (2 malicious versions).

Malicious package

vg-interaction-modelnpm

Advisory published Jun 2, 2026Updated Jun 3, 2026

vg-interaction-model is a confirmed malicious npm package (MAL-2026-5168) that executes malicious code on install (malicious versions 40.0.1, 40.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vg-interaction-model (npm)

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

Find it
Search your lockfiles and build artifacts for vg-interaction-model (2 malicious versions).
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.
Did it already run?
If vg-interaction-model 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. 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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database