Which versions of @needl-ai/common are malicious?

The following npm versions of @needl-ai/common are flagged malicious: 1.0.0, 99.99.2. Treat any of these as compromised.

How do I remediate @needl-ai/common if I installed it?

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

If @needl-ai/common 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 @needl-ai/common part of a known attack campaign?

Yes — @needl-ai/common is associated with the RLMA-2026-01861 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 @needl-ai/common 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 @needl-ai/common (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @needl-ai/common across your stack and pipelines.

Malicious package

@needl-ai/commonnpm

Malicious code in @needl-ai/common (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2716

Immediate action

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

npm uninstall @needl-ai/common

What this malware does

The package @needl-ai/common was found to contain malicious code.

The OpenSSF Package Analysis project identified '@needl-ai/common' @ 99.99.2 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

1.0.099.99.2

Indicators of compromise (SHA-256)

07f350bc78b2c6cdf7043391bb1605f22ad848daf744e21f70e4a5b09e90fd13

7eced6745ccb1cab99a3bf2df80ebdb76fa0d0275f88c1956dce1194b94a088e

e1b98ae2755d0fd7d61bc3dfd378dc1bad2eadf7ef0033ba66bbf1383a711e5c

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 @needl-ai/common (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @needl-ai/common across your stack and pipelines.
If you installed it — respond
Remove @needl-ai/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 @needl-ai/common 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 @needl-ai/common 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. @needl-ai/common on npm has been identified as a malicious package (versions 1.0.0, 99.99.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01861

References

safedep.io

Credits

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

Detect & block this

O3 blocks @needl-ai/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