Which versions of ahmed_salem_o are malicious?

Every published version of ahmed_salem_o on npm is considered malicious. Remove the package entirely.

How do I remediate ahmed_salem_o if I installed it?

Remove ahmed_salem_o 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.

I already installed ahmed_salem_o — how do I know if it already compromised me?

If ahmed_salem_o 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 ahmed_salem_o part of a known attack campaign?

Yes — ahmed_salem_o is associated with the GHSA-75rh-f487-q44w 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 ahmed_salem_o 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 ahmed_salem_o (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ahmed_salem_o across your stack and pipelines.

Malicious package

ahmed_salem_onpm

Malicious code in ahmed_salem_o (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192663

Immediate action

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

npm uninstall ahmed_salem_o

What this malware does

The package ahmed_salem_o 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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

dcde03f9a78b367c9044b92cfac2900e588491df6c7894a65c4b2658e26c7e65

5ccf3722bcf6828ca9cc9ed0f332cb3778d8a8be73146f96edb1d381a4649f54

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ahmed_salem_o (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ahmed_salem_o across your stack and pipelines.
If you installed it — respond
Remove ahmed_salem_o 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.
Did it already run?
If ahmed_salem_o 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 ahmed_salem_o 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. ahmed_salem_o on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-75rh-f487-q44w

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ahmed_salem_o-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.

Malware detection Runtime egress monitoring