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

com.unity.xr.visionosnpm

Malicious code in com.unity.xr.visionos (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190622
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall com.unity.xr.visionos

What this malware does

The package com.unity.xr.visionos 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 'com.unity.xr.visionos' @ 2.3.2 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
2.3.2

Indicators of compromise (SHA-256)

25ff36462472554b7ff72ad74024fe4497d60f84e78d6f4c4b9d1a84fcb51d07
cfc5fb97986cf3c32288632dc0df9916994609543b354548885edf9d229dd489
7d8cc90b00cae9393c461eab3728098c163f16864f715e76c39e091ebfb755cf

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 com.unity.xr.visionos (version 2.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging com.unity.xr.visionos across your stack and pipelines.

  2. If you installed it — respond

    Remove com.unity.xr.visionos 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 com.unity.xr.visionos 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 com.unity.xr.visionos 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. com.unity.xr.visionos on npm has been identified as a malicious package (version 2.3.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-453j-55mv-5p43

References

Credits

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

Detect & block this

O3 blocks com.unity.xr.visionos-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.

com.unity.xr.visionos (npm) malicious package — MAL-2025-190622 | O3 Security