Which versions of 1231dai are malicious?

The following npm versions of 1231dai are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate 1231dai if I installed it?

Remove 1231dai 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 1231dai — how do I know if it already compromised me?

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

Yes — 1231dai is associated with the GHSA-7v67-7g8x-pph4, RLMA-2026-01078 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 1231dai 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 1231dai (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging 1231dai across your stack and pipelines.

Malicious package

1231dainpm

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

MAL-2026-328

Immediate action

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

npm uninstall 1231dai

What this malware does

The package 1231dai 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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

059687ab0f69f9d832e38192dcf9e4f9f48bdf8469db1d0f049eb65cb9fbc20b

8d09761b1be982e0d4d6c72363d32a065c01f1799ef2a7df482d0d29b27e5e38

146dff72f530eb5e712a4cee3e752faaedef07516f631fe8e28ba8d9e4dddcc5

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

Campaign

GHSA-7v67-7g8x-pph4RLMA-2026-01078

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks 1231dai-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