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

wm-plugin-visions-recordernpm

Malicious code in wm-plugin-visions-recorder (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2566
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall wm-plugin-visions-recorder

What this malware does

The package wm-plugin-visions-recorder was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'wm-plugin-visions-recorder' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
99.9.1

Indicators of compromise (SHA-256)

9236b61b5f4e4b5d3a85e365fbf8932c633f54e915af3a38f2c43f2ca8822d62
92bafb354a1afa6fb40ac3af09630adac2683934e04aaf867b8689b9832e02d1
b9fc7d1b94e873a6acaa539c03b3deb578141de07e79343acb659b17d4815077

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 wm-plugin-visions-recorder (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wm-plugin-visions-recorder across your stack and pipelines.

  2. If you installed it — respond

    Remove wm-plugin-visions-recorder 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 wm-plugin-visions-recorder 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 wm-plugin-visions-recorder 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. wm-plugin-visions-recorder on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-x6cr-7xwj-965h

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks wm-plugin-visions-recorder-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.

wm-plugin-visions-recorder (npm) malicious package — MAL-2026-2566 | O3 Security