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

matlab-proxynpm

matlab-proxy is a confirmed malicious npm package (MAL-2025-849) that executes malicious code on install (malicious versions 1.0.0, 1.0.5, 2.0.5…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in matlab-proxy (npm)

MAL-2025-849
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall matlab-proxy

What this malware does

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 'matlab-proxy' @ 2.0.10 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

8 flagged
1.0.01.0.52.0.52.0.62.0.72.0.82.0.102.0.11

Indicators of compromise (SHA-256)

28958595ef874098387f3e405efe50b238a8cd8db1f72bb3a68d028d4395d97c
25ff5fb986087a5a342710fa14f097fd812832d8a6324b70e872ec40ccb7cf9f
d0c97b76513cf0f41efef9619b5a85c818093738a81b0627a1cf80d4b0a84069
69d1c9f8fc2ac7b79ac71f982d63975187f10208bf2e827f0797a38e8e629a16
95c7ecb2db92bd175e93e71dcdc5ac01334f040655a92cb4e04bbb808e057d14

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 matlab-proxy (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging matlab-proxy across your stack and pipelines.

  2. If you installed it — respond

    Remove matlab-proxy 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 matlab-proxy 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 matlab-proxy 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. matlab-proxy on npm has been identified as a malicious package (versions 1.0.0, 1.0.5, 2.0.5, 2.0.6, 2.0.7, 2.0.8, 2.0.10, 2.0.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-00263GHSA-jfhc-79w3-rm9wRLUA-2025-05885

References

Credits

  • OpenSSF: Package Analysis · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks matlab-proxy-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.

Explore

matlab-proxy (npm) malicious package — MAL-2025-849 | O3 Security