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

matlab-azure-devops-extensionnpm

matlab-azure-devops-extension is a confirmed malicious npm package (MAL-2026-12400) that opens a backdoor for remote access (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in matlab-azure-devops-extension (npm)

MAL-2026-12400
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall matlab-azure-devops-extension

What this malware does

The package's preinstall script (node index.js) auto-executes on npm install and collects host identifiers (os.hostname(), os.userInfo().username, home directory, DNS servers) along with the contents of /etc/passwd and /etc/hosts, then POSTs them via HTTPS to a hardcoded Burp Collaborator subdomain at 2ru8qr34u3so6bnti176tzt30u6muci1.oastify.com. The package name mimics an Azure DevOps MATLAB extension but ships no legitimate functionality (empty author, empty description); the package exists only to run the exfil beacon. Consistent with a dependency-confusion / recon probe.

Malicious versions

1 flagged
1.0.1

Indicators of compromise (SHA-256)

ecc42778bb54bfdea5784d5dcb68cf43c89def3dbaeddba1d1a6bd2850cb174b

Detection & response playbook

Backdoor / remote access

  1. Find it

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

  2. If you installed it — respond

    matlab-azure-devops-extension establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If matlab-azure-devops-extension 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-azure-devops-extension 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-azure-devops-extension on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014856

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks matlab-azure-devops-extension-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
matlab-azure-devops-extension (npm) malicious package — MAL-2026-12400 | O3 Security