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

microsoft-employee-experiencenpm

Malicious code in microsoft-employee-experience (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3018
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall microsoft-employee-experience

What this malware does

The package microsoft-employee-experience was found to contain malicious code.

The OpenSSF Package Analysis project identified 'microsoft-employee-experience' @ 99.2.2 (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
99.2.199.2.2

Indicators of compromise (SHA-256)

57f04f03ea7885020c55b905296876100e081e865b6abc6d6a7b3c03786a8d98
9c34bc4b2b8497b2f155f93295b0fe4b78eb94e7830684929547465d0b66b7a7
141a7384b8f01b0eff88e3a189bdec1d19e05dd5ee23caf3b2c7d1a92f1c290f

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

  2. If you installed it — respond

    Remove microsoft-employee-experience 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 microsoft-employee-experience 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 microsoft-employee-experience 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. microsoft-employee-experience on npm has been identified as a malicious package (versions 99.2.1, 99.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

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

Detect & block this

O3 blocks microsoft-employee-experience-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.

microsoft-employee-experience (npm) malicious package — MAL-2026-3018 | O3 Security