Which versions of @wethenorth12/near-api are malicious?

The following npm versions of @wethenorth12/near-api are flagged malicious: 3.0.1. Treat any of these as compromised.

How do I remediate @wethenorth12/near-api if I installed it?

@wethenorth12/near-api is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @wethenorth12/near-api — how do I know if it already compromised me?

If @wethenorth12/near-api 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 @wethenorth12/near-api part of a known attack campaign?

Yes — @wethenorth12/near-api is associated with the IN-MAL-2026-013436 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 @wethenorth12/near-api 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 @wethenorth12/near-api (version 3.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @wethenorth12/near-api across your stack and pipelines.

Malicious package

@wethenorth12/near-apinpm

@wethenorth12/near-api is a confirmed malicious npm package (MAL-2026-12098) that steals credentials and exfiltrates sensitive data (malicious version 3.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @wethenorth12/near-api (npm)

MAL-2026-12098

Immediate action

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

npm uninstall @wethenorth12/near-api

What this malware does

Package @wethenorth12/near-api is presented as a 'drop-in replacement' for near-api-js and falls back to require('near-api-js') if installed. On require(), the main module reads process.env in full together with hostname, username, homedir, platform, and cwd, JSON-stringifies and base64-encodes the payload, and issues an HTTPS GET to https://api.telegram.org/bot<redacted>/sendMessage with chat_id 8969499041. A flag file in tmpdir suppresses repeat sends. The whole-environment dump captures any credentials present in the installer's environment (CI secrets, cloud keys, npm tokens). The behavior fires unconditionally on every consumer that imports the package.

Malicious versions

1 flagged

3.0.1

Indicators of compromise (SHA-256)

ec76b158cd4b27bb2e90a492c1713c1655dcbd2f4a9fc0f03a0664d8bec8e2ed

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @wethenorth12/near-api (version 3.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @wethenorth12/near-api across your stack and pipelines.
If you installed it — respond
@wethenorth12/near-api is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @wethenorth12/near-api 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 @wethenorth12/near-api 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. @wethenorth12/near-api on npm has been identified as a malicious package (version 3.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-013436

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @wethenorth12/near-api-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database