Which versions of jagproject are malicious?

The following npm versions of jagproject are flagged malicious: 28.1.0, 28.2.0, 28.3.0. Treat any of these as compromised.

How do I remediate jagproject if I installed it?

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

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

Yes — jagproject is associated with the IN-MAL-2026-016052, IN-MAL-2026-016053, IN-MAL-2026-016051 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 jagproject 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 jagproject (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jagproject across your stack and pipelines.

Malicious package

jagprojectnpm

jagproject is a confirmed malicious npm package (MAL-2026-13402) that executes malicious code on install (malicious versions 28.1.0, 28.2.0, 28.3.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jagproject (npm)

MAL-2026-13402

Immediate action

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

npm uninstall jagproject

What this malware does

The package (a Baileys-family WhatsApp library fork) contains char-code-obfuscated destination strings in lib/Socket/messages-send.js at lines 425 and 436. The byte arrays passed to String.fromCharCode decode to the URL https://fiora.nixel.my.id/, a hardcoded third-party host reconstructed at runtime rather than appearing as a plain string literal. The URL is embedded on the message-send code path, meaning normal use of the library's messaging API routes caller-owned session data through an author-controlled endpoint that is deliberately concealed via char-code obfuscation. Obfuscated destinations in a messaging library's send path have no legitimate purpose and match the covert-relay pattern seen in compromised Baileys forks.

Malicious versions

3 flagged

28.1.028.2.028.3.0

Indicators of compromise (SHA-256)

0d8c56a51a256d7e55c64c71b51b0559ca53c6624e2b225264b13a5061105947

94042d7483f1c99379cc4befbb3b56f08c75caf9f5f9fd04fa3cfe51ef5edd50

5b9e8e7f59a1e5717aee5efd7eb7414cc68c1d87e63fdb0b487e5dfede0b6ee5

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

Campaign

IN-MAL-2026-016052IN-MAL-2026-016053IN-MAL-2026-016051

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks jagproject-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