Beware the Chimera: Stealthy PyPI Package Targets AWS and macOS Data

Summary

• A malicious PyPI package called ‘chimera-sandbox-extensions’ was found stealing data from developers’ machines, including AWS credentials and macOS details.
• The package posed as a helper module for the Chimera sandbox, a tool used by developers.
• Researchers initially described the operation as sophisticated and well organized.
• Security experts are urging developers to check third-party packages carefully.

How the package was found

Researchers at JFrog found the package, called ‘chimera-sandbox-extensions’, on the Python Package Index (PyPI) in June 2025. Media reports dubbed it ‘Chimera-strike’. It was built to steal secrets.

Once installed, the package used a domain generation algorithm to find its Command & Control (C&C) server, then downloaded a second-stage Python payload that did the actual data theft.

Disguised as a Developer’s Tool

The package was convincing. It presented itself as an add-on for Chimera sandbox users, promising extra functionality, and once installed it quietly harvested AWS account information and tokens, CI/CD secrets, Git data and macOS JAMF configuration details before sending them all to external servers.

Attackers keep improving their techniques, so developers need to check any third-party package before adding it to a project. The package was downloaded about 140 times before removal. Even small numbers matter, because one compromised developer machine can expose a company’s cloud accounts.

What security experts recommend

Security experts say the case shows how carefully attackers now design these packages. Developers should check where a package comes from, who maintains it and whether its name closely mimics a known tool.

Open-source repositories have made tools available to everyone. That openness is also what attackers exploit, so verifying the integrity of what you install is now part of the job.

Who is Behind Chimera-strike?

When the package was first reported, researchers suggested a skilled, organized actor was behind it, given its multi-stage design and its focus on corporate developer environments. JFrog later said the package had been part of an internal security-audit simulation, not an attack by an unknown threat actor.

Malicious packages on PyPI are nothing new. Whatever its origin, this one showed how much damage a well-built package could do, and how quickly it could reach developers’ machines.

A Call for Caution and Proactive Measures

The case is a reminder of the risks that come with third-party code. Security specialists urge developers to use strong security controls and to be skeptical of newly published tools.

Recommended steps include keeping dependencies updated, checking package integrity with checksums and using threat detection tools. Subscribing to threat intelligence feeds also helps teams learn about new malicious packages quickly.

Lessons for developers

Chimera-strike shows how quietly a malicious package can work once it is installed. Stay alert.

The software ecosystem keeps growing, and so does the number of packages developers rely on. Careful habits, and a willingness to question trust in third-party tools, go a long way toward reducing risk.

Fred Templeton, CISA, CASP, SEC+

Fred Templeton is a practicing Information Systems Auditor in the Washington DC area. Fred works as a government contractor and uses his skills in cyber security to make our country's information systems safer from cyber threats. Fred holds a master's degree in cybersecurity and is currently working on his PHD in Information Systems.