Which versions of fastercode are malicious?

The following PyPI versions of fastercode are flagged malicious: 0.1.0, 0.1.1, 1.0.0. Treat any of these as compromised.

How do I remediate fastercode if I installed it?

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

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

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

Malicious package

fastercodePyPI

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

MAL-2026-6206

Immediate action

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

pip uninstall fastercode

What this malware does

The package advertises itself as a Python performance helper ("Make your Python code run faster") and exposes a single public function run(). On Windows, calling run() fetches BackgroundSyncService.exe from https://raw.githubusercontent.com/manhhungdev0603/kl.py/refs/heads/main/BackgroundSyncService.exe, writes it to %PROGRAMDATA%\BackgroundSyncService\, and launches it via subprocess.Popen([local_filepath], shell=True) (fastercode/core.py:7-22). The source URL is a mutable branch reference on a personal GitHub account; the repo is named kl.py (suggestive of "keylogger.py"); the binary is unsigned, unpinned, and unrelated to the package's advertised purpose. All exceptions during download/execute are swallowed silently. Package metadata lists author="Anonymous" with no email or homepage, consistent with a throwaway publish account. Any developer who imports fastercode and calls its only public API on Windows runs an attacker-controlled executable persisted under PROGRAMDATA.

The package contains code to download and run a malicious executable. The executable contains a remote access trojan controlled via Telegram bot, with capabilities like a keylogger, screen recording, command execution. It also attempts to gain persistence via startup registry keys.

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

Campaign: 2026-06-fastercode

Reasons (based on the campaign):

Downloads and executes a remote executable.
peristence-autorun
uses-telegram-bot
keylogger
rat
spyware-like

Malicious versions

3 flagged

0.1.00.1.11.0.0

Indicators of compromise (SHA-256)

1c2793304d30de27278e36f79685e9ca60f9f839d7a27d2ea39d8d22e36a8584

0c1c6ad7cb09c8cd9e42769e498edb2d78c688470b110385943bee59a30ccb7b

14de4534d4cf2290f5f54bc5929fa799b73dff2e6a03aa879ade141dfc6ea054

318511040684d1d998f340681b444251df9bec616202a4c158d31344a22d9670

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

Campaign

2026-06-fastercodeIN-MAL-2026-007337IN-MAL-2026-007403IN-MAL-2026-007402

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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