Which versions of @wethenorth12/test-fresh are malicious?

The following npm versions of @wethenorth12/test-fresh are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @wethenorth12/test-fresh if I installed it?

@wethenorth12/test-fresh 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/test-fresh — how do I know if it already compromised me?

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

Yes — @wethenorth12/test-fresh is associated with the IN-MAL-2026-013460 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/test-fresh 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/test-fresh (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 @wethenorth12/test-fresh across your stack and pipelines.

Malicious package

@wethenorth12/test-freshnpm

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

Malicious code in @wethenorth12/test-fresh (npm)

MAL-2026-12104

Immediate action

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

npm uninstall @wethenorth12/test-fresh

What this malware does

On require() of the package, index.js collects the machine hostname, OS username, package name, and a timestamp and sends them via HTTPS GET to a hardcoded Telegram Bot API endpoint (bot id 7231970337, chat_id 8969499041). A flag file (.tst) is written to the OS tmpdir to suppress repeat sends. The Telegram bot token is embedded in the source and serves as the exfiltration transport. Consumers that install and load the package leak host/user identifiers to an attacker-controlled Telegram chat with no opt-in.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

978a97770aada576052d6e62b4a5815fb8a186b1b30275860c0951f00f5b3f7c

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/test-fresh (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 @wethenorth12/test-fresh across your stack and pipelines.
If you installed it — respond
@wethenorth12/test-fresh 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/test-fresh 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/test-fresh 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/test-fresh 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

IN-MAL-2026-013460

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @wethenorth12/test-fresh-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