Which versions of @afound/common are malicious?

The following npm versions of @afound/common are flagged malicious: 10.10.11, 10.10.12. Treat any of these as compromised.

How do I remediate @afound/common if I installed it?

Remove @afound/common 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 @afound/common — how do I know if it already compromised me?

If @afound/common was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @afound/common part of a known attack campaign?

Yes — @afound/common is associated with the RLMA-2024-10376, RLUA-2026-05794 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 @afound/common across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @afound/common (2 malicious versions).

Malicious package

@afound/commonnpm

Advisory published Dec 8, 2024Updated Sep 1, 2026

@afound/common is a confirmed malicious npm package (MAL-2024-11252) that executes malicious code on install (malicious versions 10.10.11, 10.10.12). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @afound/common (npm)

MAL-2024-11252

Immediate action

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

npm uninstall @afound/common

Malicious versions

2 flagged

10.10.1110.10.12

Indicators of compromise (SHA-256)

16aeb1fcc89c46b14a4cb7f5b945b0a57409bcb1168a91f93c060282d848850e

37ff775e1cbdca4a41f7bdbffe7cd18ff3d0f4315b2252a74e4597a6ba774b17

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @afound/common (2 malicious versions).
If you installed it — respond
Remove @afound/common 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 @afound/common was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @afound/common on npm has been identified as a malicious package (versions 10.10.11, 10.10.12 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-10376RLUA-2026-05794

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @afound/common-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

Explore

All malware advisories How O3 detects malware Vulnerability database