Which versions of expo-audio-session are malicious?

The following npm versions of expo-audio-session are flagged malicious: 0.2.1. Treat any of these as compromised.

How do I remediate expo-audio-session if I installed it?

expo-audio-session is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed expo-audio-session — how do I know if it already compromised me?

If expo-audio-session 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.

Is expo-audio-session part of a known attack campaign?

Yes — expo-audio-session is associated with the GHSA-jj4m-v9c9-3v2w, RLMA-2026-01302 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find expo-audio-session across my projects, lockfiles, and CI pipelines?

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

Malicious package

expo-audio-sessionnpm

Malicious code in expo-audio-session (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190842

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall expo-audio-session

What this malware does

The package expo-audio-session 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

0.2.1

Indicators of compromise (SHA-256)

62960ebcb1688cc1542366b31fca17612d23e2837c1069a7dee6d6927a6b1e14

9ab638e9e692037cc0b74ba589ba0f3986462fcf5310a6ba4418a01fb08c6866

069312b6af2fe92485f8e39bd62fce6fb2747f170568dd5f14132c0439764bb6

501e2316bad52cf4d5b957080968e4b1fa4ee430c257d7d13bd4633ba0050ed4

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for expo-audio-session (version 0.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging expo-audio-session across your stack and pipelines.
If you installed it — respond
expo-audio-session is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If expo-audio-session 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.
How O3 protects you
O3 blocks expo-audio-session 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. expo-audio-session on npm has been identified as a malicious package (version 0.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jj4m-v9c9-3v2wRLMA-2026-01302

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks expo-audio-session-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring