Which versions of noteasonfnsource are malicious?

The following PyPI versions of noteasonfnsource are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate noteasonfnsource if I installed it?

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

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

Yes — noteasonfnsource is associated with the 2026-02-old-noteasonfnsource 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 noteasonfnsource 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 noteasonfnsource (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging noteasonfnsource across your stack and pipelines.

Malicious package

noteasonfnsourcePyPI

Malicious code in noteasonfnsource (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-1098

Immediate action

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

pip uninstall noteasonfnsource

What this malware does

Code provides a Discord bot, which - once a generic command is called - performs malicious action against the Discord server: deletes all channels, renames the server, and then starts a loop that creates spamming channels and notifies everyone.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-02-old-noteasonfnsource

Reasons (based on the campaign):

abusing-3rd-api
other

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

fa2242ec1849ffa55a55c85b7781623cdc7147b8568b3beaa5d2b3b956c04e17

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

Campaign

2026-02-old-noteasonfnsource

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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